Xorg assert failure: X: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.

Bug #635362 reported by Daniel Senderowicz
142
This bug affects 18 people
Affects Status Importance Assigned to Milestone
X.Org X server
Fix Released
Medium
xserver-xorg-video-savage (Ubuntu)
Fix Released
Medium
Unassigned
Maverick
Fix Released
Medium
Unassigned

Bug Description

it just logs me out, could be after 1 minute or 10 minutes

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-core 2:1.9.0-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic i686
Architecture: i386
AssertionMessage: X: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
Date: Fri Sep 10 15:06:07 2010
ExecutablePath: /usr/bin/Xorg
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
Lsusb:
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   3.3V 32-bit PC Card
 Socket 1:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-20-generic root=UUID=7d74c065-a5cd-4c8a-862f-5dcd8f65d8fb ro quiet splash
ProcCmdline: /usr/bin/X :1 -br -verbose -auth /var/run/gdm/auth-for-gdm-EjSSD3/database -nolisten tcp
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/libc.so.6
 abort () from /lib/libc.so.6
 __assert_fail () from /lib/libc.so.6
 ?? () from /usr/lib/xorg/modules/drivers/savage_drv.so
Title: Xorg assert failure: X: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
UserGroups:

dmi.bios.date: 10/18/2006
dmi.bios.vendor: IBM
dmi.bios.version: 1AET64WW (1.20 )
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvr1AET64WW(1.20):bd10/18/2006:svnIBM:pn:pvrNotAvailable:rvnIBM:rn:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.version: Not Available
dmi.sys.vendor: IBM
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-20-generic

Revision history for this message
Daniel Senderowicz (daniel-synchrodesign) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __kernel_vsyscall ()
 *__GI_raise (sig=6)
 *__GI_abort () at abort.c:92
 *__GI___assert_fail (assertion=0x3a3c4b "key->initialized",
 SavageUpdateKey (pScrn=<value optimized out>,

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Robert Hooker (sarvatt)
visibility: private → public
Revision history for this message
Tomasz Czapiewski (xeros) wrote :

II've had the same error message after I upgraded from Kubuntu 10.04 to 10.10 (with updates) yesterday. My PC has two Radeon cards (RV350 and RV370).
After many hours trying bring my system to live I've found that in my case the cause of problem was:
Load "v4l"
option in "Module" section of this file.
Commenting this line fixed KDM (and Xorg) start.

Could you see if you have /etc/X11/xorg.conf and post it here if you've got it?

Revision history for this message
Daniel Senderowicz (daniel-synchrodesign) wrote : Re: [Bug 635362] Re: Xorg assert failure: X: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.

Hi Tomasz,

Unfortunately I don't have those files anymore. This bug, as well as
another (probably unrelated) problem with grub not seeing the 2
partitions made me give up on Ubuntu and install Fedora 13 which works
well. However I have Ubuntu on another machine that runs OK but I cannot
longer use the Nvidia proprietary driver. It seems that Maverick 10.10
has still a few rough edges to polish (no pun intended!)

Best regards,

Daniel

On Mon, 2010-11-01 at 20:59 +0000, Tomasz Czapiewski wrote:
> II've had the same error message after I upgraded from Kubuntu 10.04 to 10.10 (with updates) yesterday. My PC has two Radeon cards (RV350 and RV370).
> After many hours trying bring my system to live I've found that in my case the cause of problem was:
> Load "v4l"
> option in "Module" section of this file.
> Commenting this line fixed KDM (and Xorg) start.
>
> Could you see if you have /etc/X11/xorg.conf and post it here if you've
> got it?
>

Revision history for this message
Tormod Volden (tormodvolden) wrote :

I can confirm this on 10.10. We need to pull in http://cgit.freedesktop.org/xorg/driver/xf86-video-savage/commit/?id=830e58d086828fa0431303df32a847ddd3022654 for 10.10. For natty we will probably pull in 2.3.2 which includes this fix. Anyway, I have attached a debdiff for natty, so it can be tested there before being SRU'ed to 10.10.

affects: xorg-server (Ubuntu) → xserver-xorg-video-savage (Ubuntu)
Changed in xserver-xorg-video-savage (Ubuntu):
status: New → Confirmed
tags: added: patch
Michael Terry (mterry)
Changed in xserver-xorg-video-savage (Ubuntu):
assignee: nobody → Michael Terry (mterry)
status: Confirmed → In Progress
Revision history for this message
Michael Terry (mterry) wrote :

This patch looks fine and builds fine. I would upload it, but I'm not core-dev.

Changed in xserver-xorg-video-savage (Ubuntu):
assignee: Michael Terry (mterry) → nobody
status: In Progress → Triaged
Revision history for this message
Mike L (mikerl) wrote :

The current savage driver has problems rendering any OpenGL application. The experimental one, which can be found as a DEB off of Debian's website, sort of fixes the problem. It can be found at <http://packages.debian.org/experimental/xserver-xorg-video-savage>. The problem that Daniel is having is relating to OpenGL attempting to initialise itself with Gnome's screensaver, and failing due to bugs in the Savage driver. This causes X to crash, and X restarts, logging the user off. This happens with other OpenGL applications as well, such as OpenGL accelerated video in VLC or Gnome MPlayer, ZSnes with OpenGL enabled, Neverball, and other multimedia applications/games. By downloading the experimental version off of Debian's website, the crashes will stop. This, however, leads to another problem: OpenGL is painfully slow even in simple applications with the newer savage driver. But at least it works. And it seems the I will get funky colours if I use hardware accelerated X11 on an application such as Snes9x, even with the new driver. I hope somebody knows what/how to fix this driver. Help is appreciated, as this bug has many duplicates, so it must be having a negative impact in many other places as well.

Revision history for this message
Bryce Harrington (bryce) wrote :

Debdiff looks good to me as well, I've gone ahead and uploaded it to natty.

Changed in xserver-xorg-video-savage (Ubuntu):
status: Triaged → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xserver-xorg-video-savage - 1:2.3.1-2ubuntu3

---------------
xserver-xorg-video-savage (1:2.3.1-2ubuntu3) natty; urgency=low

  * 101_fix_use_of_privates.diff: From upstream, fixes crashes due to
    use of uninitialized privates. LP: #635362
 -- Tormod Volden <email address hidden> Thu, 16 Dec 2010 00:14:17 +0100

Changed in xserver-xorg-video-savage (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Tormod Volden (tormodvolden) wrote :

SRU rationale: On all savage hardware this bug is critical and makes the desktop unusable due to random X crashes. The attached minimal patch is taken from the newer upstream release 2.3.2. It does not affect other hardware.

TEST CASE: Use the normal desktop for a while, or activate random screen savers. Especially use of accelerated graphics such as 3D applications and notification bubbles can cause X to crash fast.

Revision history for this message
Mike L (mikerl) wrote :

Hopefully this will be backported to Maverick as well.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

This is what the SRU (Stable Release Update) process is for. It may speed things up if someone can confirm that everything is fine in Natty now.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

I tested today's natty live CD and it works fine. I was not able to make X crash.

Changed in xserver-xorg-video-savage (Ubuntu Maverick):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Uploaded maverick debdiff to maverick-proposed. Subscribing ubuntu-sru. Thanks for the debdiff!

Changed in xserver-xorg-video-savage (Ubuntu Maverick):
status: Triaged → Confirmed
Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Accepted xserver-xorg-video-savage into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in xserver-xorg-video-savage (Ubuntu Maverick):
status: Confirmed → Fix Committed
tags: added: verification-needed
Changed in xorg-server:
status: Unknown → Fix Released
Changed in xorg-server:
importance: Unknown → Medium
Revision history for this message
Joel Mawhorter (joelpub) wrote :

I had a seemingly related problem with the Savage video driver where switching to a virtual terminal and then back to X would crash X and permanently corrupt the display of the virtual terminals. Updating to the maverick-proposed version of xserver-xorg-video-savage has fixed this problem for me.

Revision history for this message
Brian Parma (bj0) wrote :

I had a related problem (bug 769799) where X would crash whenever the screensaver was activated. Installing the upgrade from maverick-proposed fixed the problem

tags: removed: verification-needed
tags: added: verification-done
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xserver-xorg-video-savage - 1:2.3.1-2ubuntu2.1

---------------
xserver-xorg-video-savage (1:2.3.1-2ubuntu2.1) maverick-proposed; urgency=low

  * 101_fix_use_of_privates.diff: From upstream, fixes crashes due to
    use of uninitialized privates. LP: #635362
 -- Tormod Volden <email address hidden> Thu, 16 Dec 2010 00:14:17 +0100

Changed in xserver-xorg-video-savage (Ubuntu Maverick):
status: Fix Committed → Fix Released
To post a comment you must log in.