On Tue, Mar 06, 2012 at 07:07:01AM +0100, Michael Biebl wrote: > severity 645427 important > thanks > > On 06.03.2012 06:51, Josh Triplett wrote: > > On Tue, Mar 06, 2012 at 04:37:38AM +0100, Michael Biebl wrote: > >> On 06.03.2012 03:53, Josh Triplett wrote: > >>> On Tue, Mar 06, 2012 at 03:25:21AM +0100, Michael Biebl wrote: > >>>> On 06.03.2012 03:15, Debian Bug Tracking System wrote: > >>>>> Processing commands for [email protected]: > >>>>> > >>>>>> reopen 645427 > >>>>> Bug #645427 {Done: Michael Biebl <[email protected]>} > >>>>> [gnome-power-manager] Stopped locking the screen when closing the > >>>>> laptop lid > >>>>> Bug #626544 {Done: Michael Biebl <[email protected]>} > >>>>> [gnome-power-manager] gnome-screensaver: does not lock the screen in > >>>>> GNOME 3 when the computer goes to sleep > >>>>> Bug #647358 {Done: Michael Biebl <[email protected]>} > >>>>> [gnome-power-manager] g-p-m doesn't lock the screen on lid-close > >>>>> because it uses an obsolete GConf key > > .. > > > > Yes, easily. I created a new user account, logged in as that user, ran > > gnome-tweak-tool to change the settings described in my previous comment > > (change lid close from suspend to blank), closed the lid, reopened it, > > and observed the lack of an unlock screen. > > Well, that's what I meant with local configuration. The default is > suspend-on-lid-close, and in this case the screen locks correctly. > > This information is completely missing from your initial bug report. It > was not clear to me, that you had a custom configuration. (and I think > in this case #626544 shouldn't have been merged) > > So, what you want is lock-on-blank, basically.
I want gnome-screensaver to properly lock the screen as I've already configured it to do, yes. :) I mentioned this in the bug log: http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=40;bug=645427 And I mentioned it again in my mail that reopened the bug (the one that didn't come through properly and I had to forward the contents of). I merged the bugs at Alexander Kurt's suggestion, because while I ran GNOME 2 and GNOME 2's version of gnome-power-manager, the workaround mentioned in bug 647358 (manually setting the gconf key gnome-power-manager looks at rather than the dconf key that gnome-screensaver migrated to) solved the problem for me, which matches the explanation of bug 647358. This new problem seems different: it appears that gnome-power-manager in GNOME 3 no longer respects *either* the gconf or dconf keys of gnome-screensaver that tell it to lock the screen, or alternatively something other than gnome-power-manager handles blanking the screen and it doesn't respect org.gnome.desktop.screensaver.lock-enabled. - Josh Triplett -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
