Bug#662747: Screen not locked on lid close when lid close action set to 'blank'.

March 06th, 2012 - 02:30 am ET by Josh Triplett | Report spam
Package: gnome-settings-daemon
Version: 3.2.2-2
Severity: important
Tags: security

Relevant settings:
org.gnome.settings-daemon.plugins.power lid-close-ac-action 'blank'
org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank'
org.gnome.desktop.screensaver lock-enabled true

With these settings, closing the laptop lid should blank the screen,
which should in turn lock the screen, such that reopening the
lid reveals an unlock dialog rather than the user's unsecured desktop.
However, this does not occur: closing the lid blanks the screen but does
not lock it, and reopening the lid gives access to the user's account.
By contrast, leaving the system idle until the screensaver kicks in
results in a properly locked screen.

I can reproduce this with a freshly created user account, just by
setting the first two keys above (lid-close-{ac,battery}-action);
lock-enabled already defaults to true.

Michael Biebl suggested that gnome-settings-daemon needed to emit a lock
signal as part of blanking, as it currently does when suspending.

Please let me know if you need any additional information.

Thanks,
Josh Triplett

Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-settings-daemon depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.10.0-3
ii dpkg 1.16.1.2
ii gsettings-desktop-schemas 3.2.0-2
ii libatk1.0-0 2.2.0-2
ii libc6 2.13-27
ii libcairo-gobject2 1.10.2-6.2
ii libcairo2 1.10.2-6.2
ii libcanberra-gtk3-0 0.28-3
ii libcanberra0 0.28-3
ii libcolord1 0.1.16-2
ii libcomerr2 1.42.1-2
ii libcups2 1.5.2-6
ii libdbus-1-3 1.4.18-1
ii libdbus-glib-1-2 0.98-1
ii libfontconfig1 2.8.0-3.1
ii libfreetype6 2.4.8-1
ii libgconf2-4 3.2.3-3
ii libgcrypt11 1.5.0-3
ii libgdk-pixbuf2.0-0 2.24.1-1
ii libglib2.0-0 2.30.2-6
ii libgnome-desktop-3-2 3.2.1-3
ii libgnome2-common 2.32.1-2
ii libgnomekbd7 3.2.0-1
ii libgnutls26 2.12.16-1
ii libgssapi-krb5-2 1.10+dfsg~beta1-2
ii libgtk-3-0 3.2.3-1
ii libgudev-1.0-0 175-3.1
ii libk5crypto3 1.10+dfsg~beta1-2
ii libkrb5-3 1.10+dfsg~beta1-2
ii liblcms2-2 2.2+git20110628-2
ii libnotify4 0.7.4-1
ii libpackagekit-glib2-14 0.7.3-1
ii libpango1.0-0 1.29.4-2
ii libpolkit-gobject-1-0 0.104-2
ii libpulse-mainloop-glib0 1.1-3
ii libpulse0 1.1-3
ii libsqlite3-0 3.7.10-1
ii libupower-glib1 0.9.15-2
ii libx11-6 2:1.4.4-4
ii libxfixes3 1:5.0-4
ii libxi6 2:1.4.5-1
ii libxklavier16 5.2.1-1
ii nautilus-data 3.2.1-2
ii zlib1g 1:1.2.6.dfsg-2

Versions of packages gnome-settings-daemon recommends:
ii hwdata <none>
ii pulseaudio 1.1-3

Versions of packages gnome-settings-daemon suggests:
ii gnome-screensaver 3.2.0-2+b1
ii metacity [x-window-manager] 1:2.34.1-2
ii x11-xserver-utils 7.6+3




To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
email Follow the discussionReplies 1 replyReplies Make a reply

Replies

#1 Michael Biebl
March 06th, 2012 - 02:50 am ET | Report spam
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)

tags 662747 + confirmed
forwarded 662747 https://bugzilla.gnome.org/show_bug.cgi?id=671445
thanks

On 06.03.2012 08:25, Josh Triplett wrote:

Relevant settings:
org.gnome.settings-daemon.plugins.power lid-close-ac-action 'blank'
org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank'
org.gnome.desktop.screensaver lock-enabled true



With those settings I'm able to reproduce the issue and I agree that
blanking-on-lid-close should behave the same as blanking-on-idle-event
(or suspend-on-lid-close, ftm) wrt to locking.

Marking as confirmed and forwarded it upstream.


Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?







To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact

Similar topics