I updated the bug title. In this report, let's track the missing screen
locking on lid close when using gdm autologin. Please file (or lookfor)
separate reports for other cases, like the indicator or the power button
dialog, otherwise it becomes too hard to track.
Thanks!
** Summary changed:
-
Please open a terminal, and do
killall gnome-power-manager
gnome-power-manager --verbose 21 | tee /tmp/gpm.log
Then close the lid, reopen again, confirm that it suspended/resumed, but
does not lock the screen. Press Control-C, and attach /tmp/gpm.log here.
Then press Alt+F2 and run
Here you go. Also, I'm not using autologin...
** Attachment added: gpm.log
http://launchpadlibrarian.net/33170266/gpm.log
--
Does not lock screen on lid close when using gdm autologin
https://bugs.launchpad.net/bugs/428115
You received this bug notification because you are a member of Ubuntu
Martin, isn't locking disabled by design when using autologin?
http://bazaar.launchpad.net/~indicator-applet-developers/indicator-
session/trunk/revision/45
--
Does not lock screen on lid close when using gdm autologin
https://bugs.launchpad.net/bugs/428115
You received this bug notification
Tormod - locking via the inidicator is a separate issue.
Anyway, this bit of the log shows why g-p-m is not locking the screen on
lid-close:
TI:16:49:01 TH:0x84d5168FI:gpm-control.c
FN:gpm_control_get_lock_policy,227
- Using ScreenSaver settings (0)
This is because it's
I suspect that your user config shows /apps/gnome-power-
manager/lock/use_screensaver_settings = TRUE and /apps/gnome-
screensaver/lock_enabled = FALSE
--
Does not lock screen on lid close when using gdm autologin
https://bugs.launchpad.net/bugs/428115
You received this bug notification because
Chris, it is a separate issue, but should not the same logic apply?
--
Does not lock screen on lid close when using gdm autologin
https://bugs.launchpad.net/bugs/428115
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
Our current default setting for /apps/gnome-power-
manager/lock/use_screensaver_settings is true, which means that the
screen will not lock on suspend (when you close the lid) if you have
disabled locking in the screensaver preferences. The log above shows
that this is the most likely cause for
b...@aao-lin:~$ gconftool -R /apps/gnome-screensaver
lock_enabled = false
idle_activation_enabled = true
cycle_delay = 10
status_message_enabled = true
mode = blank-only
theme = screensavers-ubuntu_theme
user_switch_enabled = true
idle_delay = 10
logout_delay = 120
power_management_delay
Bart - thanks. So your issue is that you disabled Lock screen when
screensaver is active in the user preferences.
This is confusing, and I think we should change use_screensaver_settings
to false by default.
--
Does not lock screen on lid close when using gdm autologin
Tormod - perhaps the same logic should apply, but the indicator applet
doesn't user gnome-power-manager for suspend (it talks directly to DK-
power) so it is responsible for locking the screen itself. I'm not sure
what the policy is for locking the screen on suspend from the session
applet, as I'm
This fixed the issue, however I never changed this option. It must have
been a default on the alpha version I installed. This should definitely
be the default option, if it isn't already with newer versions. Thanks
for the help.
--
Does not lock screen on lid close when using gdm autologin
You're right, /apps/gnome-screensaver/lock_enabled is actually false
by default (it is true in the schema, but false in
/use/share/gconf/defaults/10_gnome-screensaver.
--
Does not lock screen on lid close when using gdm autologin
https://bugs.launchpad.net/bugs/428115
You received this bug
13 matches
Mail list logo
