I filed a report about similar behavior a few days ago when upgrading from ibex to jaunty and then to karmic, where my screensaver stopped working correctly. Running gnome-screensaver in debug as you did, I see no events at the one minute mark, which the timeout is set to. Using gnome-screensaver-command -a as you did put my screensaver into proper fade out as I'd expect at the timeout, without the error.
One thing I did notice is restarting gnome-screensaver in debug, while waiting for the screensaver to kick in, all of a sudden I did get a DMPS shutdown of the screen, which hadn't occurred at the timeout interval either. I had upgraded yesterday to an updated build of gnome-power- manager (2.27.5-0ubuntu2) supposedly resolving the timeout issue, but did infact not. I did restart it, but not gnome-screensaver, so at least DMPS seems to be behaving, still not gnome-screensaver. I think the two are somehow related, but I'm not certain if gnome- screensaver and gnome-power-manager use the same event engine (hal,dbus?) to signal "idle" state, or from xorg itself that may be broken. Seems gnome-screensaver just isn't figuring itself to ever go idle, while they fixed whatever it was in GPM. Now that I just tested the DMPS timeout again, I see it's not working again either. FWIW, another system recently upgraded to Jaunty has variable issues with gnome-screensaver not always turning on at the set timeout as well, really almost random when it works or doesn't. Almost exactly the same output as this one on karmic. -- gnome-screensaver not functioning https://bugs.launchpad.net/bugs/411350 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
