Xorg crashing at (seeminly) ramdon

[Ryan Daly]

I was able to obtain a backtrace. Will attach...

ProblemType: Bug
Architecture: i386
Date: Tue Dec 22 09:03:27 2009
DistroRelease: Ubuntu 9.10
MachineType: Dell Inc. Precision WorkStation T7400
NonfreeKernelModules: nvidia
Package: xserver-xorg-core 2:1.6.4-2ubuntu4 [modified: usr/lib/xorg/modules/extensions/libglx.so]
ProcCmdLine: root=/dev/mapper/vg00-lv01 ro quiet splash reboot=bios
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic-pae
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
SourcePackage: xorg-server
Uname: Linux 2.6.31-16-generic-pae i686
Xrandr: Error: command ['xrandr', '--verbose'] failed with exit code 1: Can't open display
dmi.bios.date: 09/09/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0RW199
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA05:bd09/09/2009:svnDellInc.:pnPrecisionWorkStationT7400:pvr:rvnDellInc.:rn0RW199:rvr:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision WorkStation T7400
dmi.sys.vendor: Dell Inc.
fglrx: Not loaded
glxinfo: Error: command ['glxinfo'] failed with exit code 255: Error: unable to open display
setxkbmap: Error: command ['setxkbmap', '-print'] failed with exit code 255: Cannot open display "default display"
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-16-generic-pae
xdpyinfo: Error: command ['xdpyinfo'] failed with exit code 1: xdpyinfo: unable to open display "".
xkbcomp:
 Error: command ['xkbcomp', ':0', '-w0', '-'] failed with exit code 1: Error: Cannot open display ":0"
                   Exiting

[Ryan Daly (daly-ctcnet)]

Backtrace obtained from running in gdb.

[Ryan Daly (daly-ctcnet)]

Another backtrace... Very similar to the one obtained on the 22nd.

[Ryan Daly (daly-ctcnet)]

Yet another trace after a crash.

This time the OS is x86_64 as I reloaded from scratch to rule out a problem during the 'do-release-upgrade' process.

[Ryan Daly (daly-ctcnet)]

This is starting to make me think about switching to Windows 7. Yet another X server SIGTERM.

[Ryan Daly (daly-ctcnet)]

These stack traces (of which I have another) all appear to be similar. I would think this would make it easy to diagnose and to determine what may be causing X to terminate. Can someone please look at this?

[Ryan Daly (daly-ctcnet)]

I've been working with some folks via the Xorg mailing list. Through that I have recompiled the latest evdev_drv.so module. I still had Xorg exit on me, but this time I received a different backtrace. I've attached the output.

[Ryan Daly (daly-ctcnet)]

Through the Xorg mailing list... I have found and removed $HOME/.xmodmaprc. I have been crash free since removing this file...

[bugbot (bugbot)]

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

[Ryan Daly (daly-ctcnet)]

Sorry for the late reply...I was having some issues getting logged back into the site.

I have not seen this issue in quite a while...so I concur with closing this bug. Thanks.