Description of problem: The system is upgraded to F12Beta and after clicking on System -> Lock Screen the entire X session is killed. The .xsession-errors shows: (new TypeError("chromeWin.Firebug is undefined", "file:///home/fleitner/.mozilla/firefox/nc0ead4b.default/extensions/%7Be4a8a97b-f2ed-450b-b12d-ee082ba24781%7D/components/greasemonkey.js", 392)) (null) get context on /home/fleitner/.xsession-errors.old.swx failed: 'No such file or directory' (null) get context on /home/fleitner/.xsession-before.swpx failed: 'No such file or directory' handle_message(member:'NameOwnerChanged') gnome-session[5568]: WARNING: Detected that screensaver has left the bus handle_message(member:'NameOwnerChanged') handle_message(member:'NameOwnerChanged') and the strace on gnome-screensaver daemon shows: 7172 write(2, "gnome-screensaver: Fatal IO error 0 (Success) on X server :0.0.\n"..., 64) = 64 7172 writev(13, [{"GIOP\1\2\1\5\0\0\0\0"..., 12}], 1) = -1 EPIPE (Broken pipe) 7172 --- SIGPIPE (Broken pipe) @ 0 (0) --- 7172 close(13) = 0 7172 writev(11, [{"GIOP\1\2\1\5\0\0\0\0"..., 12}], 1) = -1 EPIPE (Broken pipe) 7172 --- SIGPIPE (Broken pipe) @ 0 (0) --- I'll attach some logs. Version-Release number of selected component (if applicable): gnome-screensaver-2.28.0-1.fc12.i686 How reproducible: Always Steps to Reproduce: Click on System -> Lock Screen or run $ gnome-screensaver-command -l Actual results: The entire X session is killed. Expected results: The usual locked screen.
Created attachment 365526 [details] strace of gnome-screensaver-command -l
Created attachment 365527 [details] strace of gnome-screensaver daemon
Created attachment 365528 [details] xsession-error before the crash
Created attachment 365530 [details] xsession-error after the crash
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I seem to be having a similar problem except that: 1. I run F12 on other machines without this problem. The other machines use NVidia video drivers. 2. I am running F13 on two different netbooks (one Dell mini 1012, one HP mini 2102) and both behave similarly to that which has been described in this bug report. 3. My Xorg.0.log.old file shows that the intel video driver/server has crashed. (see data following this) The video driver/server crashing would account for the Xsession not being able to resume from sleeping or from screensaver since that session would no longer be available due to the driver crashing. Relevant snippet from the Xorg.0.log.old follows: -------- Backtrace: [ 12483.491] 0: /usr/bin/Xorg (xorg_backtrace+0x3c) [0x80e51dc] [ 12483.491] 1: /usr/bin/Xorg (0x8047000+0x5e176) [0x80a5176] [ 12483.491] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0x18640c] [ 12483.492] 3: /usr/bin/Xorg (miDoCopy+0x2e) [0x8198c2e] [ 12483.492] 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x210000+0x39bd9) [0x249bd9] [ 12483.492] 5: /usr/bin/Xorg (0x8047000+0xd6b14) [0x811db14] [ 12483.492] 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x210000+0x35797) [0x245797] [ 12483.492] 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x210000+0x3649b) [0x24649b] [ 12483.492] 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x210000+0x30793) [0x240793] [ 12483.492] 9: /usr/lib/libdrm.so.2 (drmHandleEvent+0xf1) [0x370921] [ 12483.492] 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x210000+0x306cf) [0x2406cf] [ 12483.492] 11: /usr/bin/Xorg (WakeupHandler+0x52) [0x80734b2] [ 12483.493] 12: /usr/bin/Xorg (WaitForSomething+0x1a2) [0x809f4a2] [ 12483.493] 13: /usr/bin/Xorg (0x8047000+0x26c70) [0x806dc70] [ 12483.493] 14: /usr/bin/Xorg (0x8047000+0x1b675) [0x8062675] [ 12483.493] 15: /lib/libc.so.6 (__libc_start_main+0xe6) [0x676cc6] [ 12483.493] 16: /usr/bin/Xorg (0x8047000+0x1b261) [0x8062261] [ 12483.493] Segmentation fault at address 0x200c0 [ 12483.493] Fatal server error: [ 12483.493] Caught signal 11 (Segmentation fault). Server aborting [ 12483.493] [ 12483.494] Please consult the Fedora Project support at http://bodhi.fedoraproject.org/ for help. [ 12483.494] Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 12483.494] [ 12483.501] (II) Power Button: Close [ 12483.501] (II) UnloadModule: "evdev" [ 12483.505] (II) Video Bus: Close [ 12483.505] (II) UnloadModule: "evdev" [ 12483.508] (II) Power Button: Close [ 12483.508] (II) UnloadModule: "evdev" [ 12483.511] (II) HP Webcam-50: Close [ 12483.512] (II) UnloadModule: "evdev" [ 12483.516] (II) AT Translated Set 2 keyboard: Close [ 12483.516] (II) UnloadModule: "evdev" [ 12483.529] (II) UnloadModule: "synaptics" [ 12483.535] (II) Macintosh mouse button emulation: Close [ 12483.535] (II) UnloadModule: "evdev" [ 12483.538] (II) HP WMI hotkeys: Close [ 12483.538] (II) UnloadModule: "evdev" [ 12483.547] (II) Logitech USB Optical Mouse: Close [ 12483.547] (II) UnloadModule: "evdev" [ 12483.547] (II) AIGLX: Suspending AIGLX clients for VT switch -------- I hope this information us useful.
CCing Adam Jackson, for the intel angle on this. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I can confirm this too, opening the configuration for the screen-saver also kills the X session. The system is a dell inspiron 1525, any help I can give please ask.
I can't get a backtrace out of my crashed but it I have a Lenovo T500 running Fedora 13 with compiz and a intel processor with a ATI graphics card and all the 3D screensavers cause the system to crash... the default installed non 3d screensavers appear to work fine
I confirm Zach's observations. I've an F13, x64, on a Dell Vostro 1520 (Intel Mobile graphics), compiz in KDE. This machine is up-to-date of all Fedora packages (except the fedora-testing ones). Activating a GL screensaver results quite often in a crashed session when I unlock. Switching to a non-GL screensaver (blank :() stopped the crashes, and I can now have a session that survives regular lock/unlock sequences. lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) lspci -n 00:00.0 0600: 8086:2a40 (rev 07) 00:02.0 0300: 8086:2a42 (rev 07) More details available on request. Any fix will be tested.
Additional information: I now have an Alienware M11x with hybrid graphics. I do not have the nVidia driver installed and the Intel graphics driver automatically installed with Fedora 13 x86_64. The symptoms persist as the Intel video is the one that is active at the moment. This is a REALLY old bug. While there may be something wrong with the screensaver code that can be fixed, an application should not be able to crash the X session so there is unquestionably a "weakness" in the Intel driver waiting for other programs to trip over this problem as well. I wonder where I might report this problem with Intel?
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.