FS#9818 - X server crash on logout with nvidia 96xx driver

Attached to Project: Arch Linux
Opened by Baeyens (berbae) - Tuesday, 11 March 2008, 22:36 GMT
Last edited by Roman Kyrylych (Romashka) - Monday, 17 March 2008, 15:29 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Alexander Baldeck (kth5)
Thomas Bächler (brain0)
Architecture i686
Severity High
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Under KDE/KDEmod (possibly others) the kdm login screen doesn't reappear when choosing the 'End Current Session' option, only a black screen. The X server crashed with this message in /var/log/kdm.log :
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x7e) [0x80baf4e]
1: [0xb7fb0420]
2: /usr/lib/xorg/modules/drivers//nvidia_drv.so(_nv001216X+0xe5) [0xb721f711]
3: [0x1]

Fatal server error:
Caught signal 11. Server aborting


Additional info:
* package version(s) :
nvidia-96xx-96.43.05-1
nvidia-96xx-utils-96.43.05-1
xorg-server 1.4.0.90-6
KDE 3.5.9

Steps to reproduce:
Under KDE trying to logout with the 'End Current Session' choice.
Black screen.
The 'Ctrl Alt Backspace' key combination produces a reboot.
Nothing else works.

See http://bbs.archlinux.org/viewtopic.php?id=43799
where the Arch nvidia packages are shown to cause that bug.
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Monday, 17 March 2008, 15:29 GMT
Reason for closing:  Not a bug
Additional comments about closing:  not in Arch, but in blob
Comment by Roman Kyrylych (Romashka) - Saturday, 15 March 2008, 11:13 GMT
if this is a bug in nvidia driver - we cannot do anything with it
Comment by Baeyens (berbae) - Sunday, 16 March 2008, 22:41 GMT
In the forum thread I said that the bug disappears with the nvidia driver installed from the Nvidia installer instead of the Arch packages.
But I observed today that same bug again in the installation produced by the Nvidia installer. So the Arch packages are not responsible for that bug, and the cause of it is left unknown.
Comment by Baeyens (berbae) - Monday, 17 March 2008, 14:42 GMT
In the thread given above, I give a workaround to this bug.
As it is not an Arch bug I think it can be closed.
Thanks.

Loading...