Bug#647358: g-p-m doesn't lock the screen on lid-close because it uses an obsolete GConf key

Alexander Kurtz kurtz.alex at googlemail.com
Wed Nov 2 07:38:16 UTC 2011


Package: gnome-power-manager
Version: 3.0.2-2
Severity: critical
Justification: Introduces a new security hole
Tags: fixed-upstream patch security

Hi,

the user can decide whether to lock his laptop on lid-close under

	System Settings -> Screen -> Lock -> On/Off

which sets "org.gnome.desktop.screensaver.lock-enabled" (GSettings),
buth g-p-m still uses "/apps/gnome-screensaver/lock_enabled" (GConf):
This query always fails and the screen is not locked on lid-close. A
good workaround is to manually re-create the old configuration key:

	gconftool-2 --type boolean --set /apps/gnome-screensaver/lock_enabled true

This bug has been reported[0] and fixed upstream[1]. Please add this
patch in order to make laptops with GNOME 3 more secure. 

Best regards

Alexander Kurtz

[0] https://bugzilla.gnome.org/show_bug.cgi?id=650464
[1] http://git.gnome.org/browse/gnome-power-manager/commit/?id=312066e7514586eb830950dae7c089f4a9f13135
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20111102/9c332b15/attachment.pgp>


More information about the pkg-gnome-maintainers mailing list