Ubuntu
xserver-xorg-video-savage package

X server crashes when screensaver activates

Bug #769799 reported by Brian Parma on 2011-04-24

This bug report is a duplicate of: Bug #635362: Xorg assert failure: X: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	xserver-xorg-video-savage (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: xserver-xorg-video-savage

If in System->Screensaver, the option 'Activate screensaver when computer is idle', when it activates the X server crashes and restarts at the login screen. This happens no matter what screensaver is selected, which is usually just set to 'blank screen'.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-video-savage 1:2.3.1-2ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11
Uname: Linux 2.6.35-28-generic i686
Architecture: i386
Date: Sun Apr 24 01:51:38 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
Lsusb:
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 04d9:1203 Holtek Semiconductor, Inc. Keyboard
Bus 001 Device 003: ID 1733:0101 Cellink Technology Co., Ltd RF Wireless Optical Mouse OP-701
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port 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-28-generic root=UUID=c395f5eb-8e3f-4f15-83a0-2524ef1ae156 ro i8042.nopnp i8042.dumbkbd=1 quiet splash
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: xserver-xorg-video-savage
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: maverick
architecture: i686
kernel: 2.6.35-28-generic

Tags:

Revision history for this message

Brian Parma (bj0) wrote on 2011-04-24:

BootDmesg.txt Edit (38.2 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (520 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (4.3 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (28.0 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (28.5 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (28.5 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (9.3 KiB, text/plain; charset="utf-8")
PciDisplay.txt Edit (748 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (472 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.1 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (246 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (67.0 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (155.0 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (40.8 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (41.4 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (1.3 KiB, text/plain; charset="utf-8")
peripherals.txt Edit (1.5 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (233 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (6.1 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (54.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Brian Parma (bj0) wrote on 2011-04-24:

backtrace of the crash. Edit (4.2 KiB, text/plain)

Here's a backtrace of the crash.

Revision history for this message

Tormod Volden (tormodvolden) wrote on 2011-04-25:

Thanks for your report. As Dave Airlie pointed out, this seems to be a known problem that has been fixed in newer versions. Please test the maverick-proposed version, and confirm it works in bug 635362.