I have marked this bug invalid because the bug exists (might still exist) in a package that is no longer used by default in current Ubuntu releases.
** Changed in: gnome-screensaver (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/779639 Title: gnome screensaver activation is hindered by unobscure routine Status in GNOME Screensaver: New Status in OEM Priority Project: Won't Fix Status in OEM Priority Project natty series: Won't Fix Status in OEM Priority Project oneiric series: Invalid Status in “gnome-screensaver” package in Ubuntu: Invalid Bug description: Binary package hint: gnome-screensaver The problem occurs in Natty, using the Unity desktop. I have not tried the old-style desktop to see if it also affects that. https://bugzilla.gnome.org/show_bug.cgi?id=649755 I have reported upstream a bug in Gnome Screensaver that is preventing my screensaver from activating during session timeout. The symptom is that the session times out, the screen fades to black, and then immediately returns to the desktop. The symptoms are similar to Bug #241206 and Bug #363635, but the cause is different than those bugs. Summary of upstream bug report: The problem is caused in gs-manager.c by the function window_obscured_cb. This function is called when the screensaver window is obscured (i.e., when fast user switching swaps to another VT) or unobscured (i.e., switching back to the VT). In addition to attempting to disable or re-enable the screensaver animation, when the screensaver is unobscured the callback automatically makes a request to unlock the screen. This saves the user from having to press a key or wave their mouse around to bring up the unlock dialog. My problem is that, for reasons I do not understand, my screensaver thinks, every time it activates due to session timeout, that its window is obscured briefly. window_obscured_cb is called twice in rapid succession, once for obscure, then again for unobscure. Because I do not use the screensaver lock feature, this means that, on the unobscure call, the screensaver is deactivated. Thus, my screensaver will never activate due to a session timeout. I have verified that the obscured window event is the reason for the screensaver deactivation using the debugging output. I have attached a patch in the upstram bug report that fixes the problem by removing the line that calls the screensaver unlock automatically as a result of an unobscure event. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/779639/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp