This bug was fixed in the package gnome-settings-daemon -
3.3.91-0ubuntu3
---------------
gnome-settings-daemon (3.3.91-0ubuntu3) precise; urgency=low
* debian/control.in:
- updated gsettings-desktop-schemas requirement for the lock key
* debian/patches/61_unity_use_application_indicator.patch:
- updated indicators ids, combined with the libappindicator new version
that should give the correct wm_class to the fallback gtkstatusicon
which should fix some gnome-shell issues (lp: #878951)
- use set_icon_full() with "Keyboard" as a11y description (lp: #740726)
[ Marc Deslauriers ]
* Add a new preference to lock the screen when the system suspends.
(LP: #938076)
- 51_lock_screen_on_suspend.patch: use lock-on-suspend gsettings to
determine if screen should be locked.
- 51_always_lock_screen_on_suspend.patch: removed.
- 54_lazily_connect_to_screensaver.patch: refreshed.
- 60_unity_hide_status_icon.patch: refreshed.
-- Sebastien Bacher <seb...@ubuntu.com> Fri, 09 Mar 2012 18:25:40 +0100
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/938076
Title:
[UIFe]Auto-lock on suspend is still needed when encrypting file system
Status in “gnome-control-center” package in Ubuntu:
Triaged
Status in “gnome-settings-daemon” package in Ubuntu:
Fix Released
Status in “gsettings-desktop-schemas” package in Ubuntu:
Fix Released
Bug description:
Patch "51" in the gnome-settings-daemon source code now disables auto-
locking of the screen, when the machine goes into suspend. This policy
makes some sense for users who use auto-login and don't have any other
security measures in place.
But it is counter-productive for users who have a boot-time password
and/or encrypted file systems. A quick web search shows that other
users are reporting the same problem, without a good work-around
available.
I understand that encrypted file systems are an advanced system
configuration, so I am not going to argue with you about the default
policy. As a default, it is probably reasonable as is. But please
allow a configuration option; even if that means manually changing
dconf settings. The users that are affected by this bug are presumably
sufficiently technical to know how to edit dconf settings.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/938076/+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
