Bug#500887: xserver-xorg: Unpredictable X server crash when Gnome screen saver (lock screen) run
On Thu, Oct 2, 2008 at 21:12:17 +1000, Jason White wrote: On several occasions now, upon running the Gnome screen saver or the lock screen menu option, the X server has crashed. My only recourse has been to log in over ssh from another system and reboot the machine. As this system has an nVidia video card installed, and I have chosen not to install the non-free nVidia driver, the X server should be using the nv driver. The automatically generated xorg.conf file is included below. The following segfault is reported in the kernel log. Oct 2 20:06:11 jdc kernel: [59619.632360] Xorg[18999]: segfault at 61 ip 7f60a837f18f sp 7fffc77fd610 error 4 in libgcc_s.so.1[7f60a836f000+16000] Hi, can you send an Xorg log from the crash (should be in /var/log/Xorg.0.log.old after reboot), or even better try to log in remotely before the crash, attach gdb to the X server process, and catch a full backtrace when it segfaults (make sure xserver-xorg-core-dbg is installed for that). Thanks, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500887: xserver-xorg: Unpredictable X server crash when Gnome screen saver (lock screen) run
On Thu, Oct 02, 2008 at 01:45:45PM +0200, Julien Cristau wrote: can you send an Xorg log from the crash (should be in /var/log/Xorg.0.log.old after reboot), or even better try to log in remotely before the crash, attach gdb to the X server process, and catch a full backtrace when it segfaults (make sure xserver-xorg-core-dbg is installed for that). I can do the former now (see the attached log file). I'll install the debugging package and attempt gdb tomorrow, assuming that I can reproduce the problem. Regards, Jason. Xorg.0.log.old Description: application/trash
Bug#500887: xserver-xorg: Unpredictable X server crash when Gnome screen saver (lock screen) run
I'm having trouble reproducing the problem, but I'll keep trying. When I run the Gnome lock screen tool with gdb monitoring the X server, I get the following signal and backtrace. However, if I resume the X server at this point, it continues normally, so this may not help you to diagnose the original crash, especially if the following is normal behaviour. Program received signal SIGPIPE, Broken pipe. [Switching to Thread 0x7f0f23ab96e0 (LWP 16946)] 0x7f0f220d7963 in writev () from /lib/libc.so.6 (gdb) bt #0 0x7f0f220d7963 in writev () from /lib/libc.so.6 #1 0x005797cc in _XSERVTransSocketWritev ( ciptr=value optimized out, buf=0x7fff2bad9ec0, size=1) at /usr/include/X11/Xtrans/Xtranssock.c:2297 #2 0x00573b87 in FlushClient (who=0x1b16540, oc=0x1b64db0, extraBuf=0x0, extraCount=0) at ../../os/io.c:1060 #3 0x005725f4 in CloseDownConnection (client=0x2e) at ../../os/connection.c:1048 #4 0x00449c7a in CloseDownClient (client=0x1b16540) at ../../dix/dispatch.c:3600 #5 0x0044f68c in Dispatch () at ../../dix/dispatch.c:513 #6 0x00436bd5 in main (argc=3, argv=0x7fff2bada568, envp=value optimized out) at ../../dix/main.c:452 (gdb) quit The program is running. Quit anyway (and detach it)? (y or n) y Detaching from program: /usr/bin/Xorg, process 16946 jdc:~# -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500887: xserver-xorg: Unpredictable X server crash when Gnome screen saver (lock screen) run
This time I managed to reproduce the real culprit. The exact sequence of steps isn't clear: working in Gnome and Iceweasel for a while, then selecting Lock screen from the Gnome system menu did the trick. The backtrace from gdb follows. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f501ebdc6e0 (LWP 17615)] 0x0061 in ?? () (gdb) bt #0 0x0061 in ?? () #1 0x7f501c157a20 in DoSwapInterval (cl=value optimized out, pc=0x2d5c674 \217\020\004, do_swap=0) at ../../../GL/glx/swap_interval.c:80 #2 0x7f501c135732 in __glXDisp_VendorPrivate (cl=0x19c50a0, pc=0x2d5c674 \217\020\004) at ../../../GL/glx/glxcmds.c:2328 #3 0x7f501c1398a5 in __glXDispatch (client=0x19b6210) at ../../../GL/glx/glxext.c:561 #4 0x0044f7d2 in Dispatch () at ../../dix/dispatch.c:502 #5 0x00436bd5 in main (argc=3, argv=0x7fff26bfb928, envp=value optimized out) at ../../dix/main.c:452 (gdb) quit -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
