This bug was fixed in the package gnome-screensaver - 3.6.0-0ubuntu2
---------------
gnome-screensaver (3.6.0-0ubuntu2) quantal-proposed; urgency=low
* debian/patches/28_blocking_return.patch:
- Correctly reply so the client doesn't block waiting (lp: #1067515)
-- Sebastien Bacher <[email protected]> Thu, 18 Oct 2012 19:35:19 +0200
--
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/1067515
Title:
Locking from user menu fails second time (gnome-screensaver
SimulateUserActivity() doesn't return)
Status in GNOME Screensaver:
Fix Released
Status in The Session Menu:
Invalid
Status in “gnome-screensaver” package in Ubuntu:
Fix Released
Status in “indicator-session” package in Ubuntu:
Invalid
Status in “gnome-screensaver” source package in Quantal:
Fix Released
Status in “indicator-session” source package in Quantal:
Invalid
Bug description:
Impact:
Locking and other actions are delayed when used for a second time
Test Case:
1. Login
2. Lock screen from system menu, then unlock
3. Lock screen again from system menu
This time the lock dialog takes around 30secs to be displayed. At this
point The same applies for Log-out, suspend options etc, if these are
clicked instead of Lock in step #3.
Regression Potential:
The SimulateUserActivity method from gnome-screensaver could not function as
it should resulting on the lock screen ui not being displayed after locking
screen of the session indicator (it would still be there but would require an
user action to show)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screensaver/+bug/1067515/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
