Red Hat Bugzilla – Bug 216045
gnome-screensaver only works a few hours
Last modified: 2013-03-05 22:48:00 EST
Description of problem: gnome-screensaver only works a few hours. Version-Release number of selected component (if applicable): gnome-screensaver-2.16.1-2.fc6 How reproducible: gnome-screensaver only works a few hours. after log out and re-login it works again for a few hours. Steps to Reproduce: 1. wait for the screensaver 2. (maybe) go to sleep 3. after a few hours the screensaver don't work anymore (only black screen) 4. log out 5. log in 6. the screensaver works again Actual results: Expected results: Additional info:
Created attachment 141424 [details] xorg.conf
I see this phenomenon too, just as described (sometimes within an hour). The screen locks and goes black, but the saver itself doesn't kick in. The screen doesn't switch off either. Restarting killall gnome-screensaver && gnome-screensaver restores the correct behaviour for a while.
i have found this error today: libGL warning: 3D driver claims to not support visual 0x4b mesa-libGL-6.5.1-8.fc6 mesa-libGLU-6.5.1-8.fc6 xorg-x11-drv-ati-6.6.3-1.fc6
Confirm bug as well. Occurs regardless of hardware (Nvidia and Intel tested) and regardless of the screensaver used (non OpenGL ones have this too).
Created attachment 142189 [details] gnome-screensaver log from a successfull activation
Created attachment 142191 [details] gnome-screensaver log from a failed activation
I investigated this some more and found that the reason a screensaver theme does not start is because the "throttled" flag is set in gs_manager.c. This is evident from comparing the two logs that I attached. Whereas the successful activation log shows that "job" (i.e., the actual process of the screensaver animation) is started, the second log shows that the screensaver is "throttled" and the job does not start. Now, it appears that the "throttled" flag is set by gnome-power-manager after the sleep timeout has elapsed (this is set in the Power Managment menu). After a computer was left idle for that period of time, gnome-power-manager sends gnome-screensaver a D-BUS message telling it to stop the animation (since the display is going to be put to sleep, so why waste CPU cycles). But it seems that the power manager does not inform gnome-screensaver when the display become active again (or perhaps, gnome-screensaver is not listening). I hope the above info will be useful for developers. A similar bug was reported here: http://www.mail-archive.com/desktop-bugs@lists.ubuntu.com/msg53003.html
Ah this is a known gnome-power-manager bug, let me look for the upstream report...
http://bugzilla.gnome.org/show_bug.cgi?id=355279
Hi guys, Would you mind testing gnome-power-manager-2.16.0-4.fc6 which should appear in updates-testing today or tommorow, or gnome-power-manager-2.17.2.1-2.fc7 which should be in tomorrow's rawhide compose?
Tested with gnome-power-manager-2.16.0-4.fc6 and the problem is no longer there.
fixed in gnome-power-manager-2.17.2.1-2.fc7. have to wait for gnome-power-manager-2.16.0-4.fc6 to be sure, i'v made an $ pkill gpm && gpm -m /dev/input/mice -t exps2...
great thanks guys for confirming both versions.