** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2009-4997
--
Does not lock screen on lid close
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 mailing list
For me the screen is NOT locked on suspend.
(It doesn't matter if pressing Fn+Esc or using indicator-applet-session!)
Comment #51 does not work for me!
My system is up to date!
** Changed in: gnome-power-manager (Ubuntu)
Status: Fix Released = New
** Changed in: indicator-session
Daniel, the bug title is does not lock screen on lid close (which is
what g-p-m does). Also comment 51 will actually _break_ it:
gconftool -s --type string /apps/gnome-power-
manager/buttons/lid_battery blank
This configured g-p-m to _not_ suspend any more on any lid actions. I
suggest to
@Martin, This configured g-p-m to _not_ suspend any more on any lid
actions -- Exactly. Perhaps should discuss this on IRC rather than
back-and-forth here, but as you note, the bug title is does not lock
screen on lid close, not the system does not suspend on lid close.
My entries in comment 51
Noel J. Bergman [2009-11-13 19:00 -]:
@Martin, This configured g-p-m to _not_ suspend any more on any lid
actions -- Exactly. Perhaps should discuss this on IRC rather than
back-and-forth here, but as you note, the bug title is does not lock
screen on lid close, not the system does not
** Description changed:
Binary package hint: gnome-power-manager
Since a recent update to Karmic, my laptop doesn't lock when exiting
suspend or when the lid is lifted. Both worked fine in Jaunty and in
Karmic up to a few days ago (I've been updating more than weekly). The
laptop
I found, on a clean karmic install, that I had to do this:
# blank screen and lock on lid close
gconftool -s --type bool /apps/gnome-power-manager/lock/blank_screen true
gconftool -s --type string /apps/gnome-power-manager/buttons/lid_battery blank
gconftool -s --type string
Just wanted to confirm that it works again. I haven't changed anything
so I guess it was an update.
--
Does not lock screen on lid close
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.
--
The problem was fixed in the indicator applet but it seems to have
reappeared again. Locking is enabled in gconf and I am using the
indicator applet.
--
Does not lock screen on lid close
https://bugs.launchpad.net/bugs/428115
You received this bug notification because you are a member of Ubuntu
The only unusual thing I had to do when testing is that I had to
manually suspend using sudo /etc/acpi/sleep.sh sleep
Right, it won't (and can't even) lock the screen with sleep.sh. Please
try it with closing/reopening the lid.
because the suspend option has disappeared in the latest karmic.
This was fixed in yesterday's gnome-session upload.
Yes - I discovered this after rebooting (it wasn't automatically
applied).
However, the problem persists. If I suspend from the System / Shut Down
menu and resume, I don't get asked for a password using my normal login.
I created a new user,
I've discovered what it is - if you suspend from user switcher applet,
it locks the screen on suspend; if you remove the applet from gnome-
panel and suspend from the System / Shut Down menu, it doesn't lock the
screen. Should I log a separate bug for this or is it still relevant to
g-p-m and this
Rocko [2009-10-08 8:51 -]:
I've discovered what it is - if you suspend from user switcher applet,
it locks the screen on suspend; if you remove the applet from gnome-
panel and suspend from the System / Shut Down menu, it doesn't lock the
screen. Should I log a separate bug for this or is
So I close this again. The initially reported bug was fixed in comment
3, and it was determined that the people who still experience this have
a local configuration which disables locking.
I verified the default settings in karmic:
* /apps/gnome-screensaver/lock_enabled is false by default
I have the same settings as the default karmic, ie as outlined in
comment #43, but I still don't get prompted for a password when I
resume. I'm running gnome-power-manager 2.28.0-0ubuntu3.
The only unusual thing I had to do when testing is that I had to
manually suspend using sudo
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
28 matches
Mail list logo
