gdm-simple-slave crashed with SIGSEGV in _XFlush()

[Peter Belew]

Binary package hint: gdm

This happened while rebooting after today's latest update to the Lucid alpha. I was rebooting with my Ethernet connection disconnected, but with a wifi card in the pci slot.

During the last 3 boots (after today's update) with the Ethernet cable disconnected, booting hung after running Grub2, after disk check messages, and before the login screen should appear.

This computer is an Averatec 3280 laptop.

Ubuntu version and kernel version
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION="Ubuntu lucid (development branch)"
Linux eros 2.6.32-10-generic #14-Ubuntu SMP Thu Jan 7 17:38:40 UTC 2010 i686 GNU/Linux
model name : Mobile AMD Sempron(tm) Processor 2800+

ProblemType: Crash
Architecture: i386
Date: Thu Jan 14 10:31:34 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/gdm/gdm-simple-slave
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091209)
Package: gdm 2.29.5-0ubuntu1 [modified: var/lib/gdm/.gconf.defaults/%gconf-tree.xml]
ProcAttrCurrent: unconfined (enforce)
ProcCmdline: /usr/lib/gdm/gdm-simple-slave --display-id /org/gnome/DisplayManager/Display1
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
SegvAnalysis:
 Segfault happened at: 0xd3b6ef: cmpl $0x0,0x28(%eax)
 PC (0x00d3b6ef) ok
 source "$0x0" ok
 destination "0x28(%eax)" (0x00000028) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gdm
StacktraceTop:
 ?? () from /usr/lib/libX11.so.6
 _XFlush () from /usr/lib/libX11.so.6
 XGetWindowProperty () from /usr/lib/libX11.so.6
 xkl_config_rec_get_from_root_window_property ()
 xkl_config_rec_get_full_from_server ()
Tags: lucid
Title: gdm-simple-slave crashed with SIGSEGV in _XFlush()
Uname: Linux 2.6.32-10-generic i686
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #505972, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.