GNOME Bugzilla – Bug 513931
gnome-screensaver deactivates itself as soon as it kicks in
Last modified: 2008-11-19 16:13:40 UTC
Please describe the problem: Under Fedora 8, the ppc flavor, gnome-screensaver deactivates itself as soon as it kicks in, which means its never started and hence, gnome-power-manager never turns off the screen or puts the laptop on suspend. Steps to reproduce: 1. Wait until the screensaver kicks in 2. 3. Actual results: After the screen has faded to black, it immediately returns to the desktop. Expected results: I would expect a screensaver. Does this happen every time? yes. Other information:
Created attachment 104269 [details] output of gnome-screensaver --no-daemon --debug
[window_obscured_cb] gs-manager.c:1282 (18:56:42): Handling window obscured: obscured [gs_job_stop] gs-job.c:479 (18:56:42): stopping job [gs_job_stop] gs-job.c:482 (18:56:42): Could not stop job: pid not defined [window_obscured_cb] gs-manager.c:1282 (18:56:42): Handling window obscured: unobscured So, for some reason your screensaver window is being obscured and then unobscurred. When unobscured we try to stop the screensaver. What window manager are you using? Version?
This happens as well in up-to-date Ubuntu 8.10 Intrepid post-beta. Using compiz. Will attach gnome-screensaver debug log. Ubuntu's gnome-screensaver version: 2.24.0-0ubuntu2. Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/273787
Created attachment 120377 [details] gnome-screensaver --no-daemon --debug
According to http://bugs.launchpad.net/bugs/278112 it's a bug in compiz as it doesn't happen with metacity.
Please see comment https://bugs.edge.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/278112/comments/45 Its a problem with the way that unredirect fullscreen windows are unhanlded inside the xserver. The patch in LP should fix it.
Thanks Michael, An older half of this issue is bug 488264 . Michael, do you know if that patch is upstream or headed that way?
Hello Ray, I submited it upstream as https://bugs.freedesktop.org/show_bug.cgi?id=18133 (sorry that I did not mention that in the previous comment).