X11 server randomly crashes after gdm upgrade

the crash is an xorg server one not a gdm bug...

or an intel driver issue

I'm a bit doubtful it's not gdm related: it happen about 10min after upgrading it whereas it had never happen before. And it stop happening immediately after downgrading to the previous version...

Gilles, can you get a full backtrace by following the instructions on https://wiki.ubuntu.com/X/Backtracing ?

It is potentially useful information that the bug was triggered by the gdm update. However, the bug itself is probably in xorg or the intel driver. It may be that the new version of gdm uses those component in a new way.

Also, we would like some other logs from you. The easiest way for you to provide that is to run `apport-collect 494448`. Alternativerly, /var/log/Xorg.0.log, output of `lspci -vvnn` and `dmesg` is minimal requirements.

Architecture: amd64
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: LENOVO 7458AF5
Package: xserver-xorg-video-intel 2:2.9.0-1ubuntu2
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-16-generic root=UUID=354d9dab-e295-4fe5-9200-d83a557c8b14 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu10
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
Uname: Linux 2.6.31-16-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
XsessionErrors:
 (gnome-settings-daemon:9331): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:9367): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:9393): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-panel:9366): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window
dmi.bios.date: 09/17/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 6DET60WW (3.10 )
dmi.board.name: 7458AF5
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6DET60WW(3.10):bd09/17/2009:svnLENOVO:pn7458AF5:pvrThinkPadX200:rvnLENOVO:rn7458AF5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7458AF5
dmi.product.version: ThinkPad X200
dmi.sys.vendor: LENOVO
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: x86_64kernel: 2.6.31-16-generic

Yikes - wasn't expecting apport-collect to create 20 separate posts, but hope this is useful! This is the first 'crash' I have ever experienced in 2 years of almost daily use - you guys are awesome.

I have myself activated apport just after Geir Ove Myhr resqueted more infos, and reinstalled 2.28.1-0ubuntu2.1 0.
It has been one week since and I've used intensively my laptop, without a single hiccup (some slowdowns may be, but not sure if they were related as I was running MS Word, Excel and Powerpoint on top of Wine) ;-)
So I was about to say the problem as non-reproducible.
It seems to be the case here at least.
Thanks for the great work guy, I love my Ubuntu.

Gilles

Chris, the apport-collect information provides the context we need, but the real information we need is the full backtrace. Also, we would like only the original reporter of a bug to do an apport-collect, since (as you found out) it uploads a lot of information and it gets messy to have several people's logs in one report. If you can get a full backtrace, it would be nice if you could file a separate bug report for it and do an apport-collect to that one.

Gilles, I will mark this bug as Incomplete for now so that it goes off the radar while we wait for the full backtrace. If you don't get it again feel free to close this bug. It will get onto the radar again if there is a comment to this bug after it has been marked as incomplete (so please don't reply just to acknowledge this).

I've just experimented again the very same crash.

It is especially annoying as it happened on top of a brand new installation I made about 10h ago.
Beforehand, my distribution was an upgrade from 8.04 to 8.10 to 9.04 to 9.10. I imagined that cold have triggered some nasty bugs due to some remains of improper configuration.

But this time, definitely not!

I've then enabled apport and I'm waiting for the next crash to happen...

Anything else I can do that could be of any help?

Gilles

Gilles, looking at this again, at this time I don't think we can do anything even with a full backtrace from Karmic, since Lucid will anyway be close by the time we could have fixed this bug. So what would actually help is if you could test Lucid and get a full backtrace from there if the bug is still present there.

Agreed with Geir; closing this bug as expired since the info he requested last month is still missing.