Let me stress that this is not a fairly minor problem, but is a
critical security vulnerability in some contexts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/620693
Title:
Screen not locked when
** Changed in: gnome-power-manager (Ubuntu Natty)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/620693
Title:
Screen not locked when turned off
To manage
Setting natty task to invalid as per comment 19
PLEASE NOTE: I'm fairly sure the fix for this fairly minor problem has
introduced a serious regression for me in that frequently my computer
will not recover from suspend anymore. I've lost data and had other
serious trouble because of it: bug
This bug was fixed in the package gnome-power-manager -
2.30.0-0ubuntu1.1
---
gnome-power-manager (2.30.0-0ubuntu1.1) lucid-proposed; urgency=low
* debian/patches/13-lock-on-blank.patch:
- When we blank due to a timeout, make sure to lock (in case
we've blanked before the
I've followed this bug specifically due to natty 11.04 behavior. The
screen does not lock after blank.
gconf settings:
lock blank_screen is true
lock use_screensaver_settings is false
The display blanks correctly at the time set in the G-P-M settings.
However, the screen does not lock
Martin, this new package looks good on Lucid. I went through the
testing procedure before the package, and the screen did not lock.
After installing the new package, without changing settings, the screen
did indeed lock.
Michael, thanks for taking a look at this.
--
You received this bug
tekstr1der, you are right. I'll open an 11.04 (and maybe 10.10) task
now. I had not tested those without the screensaver enabled at all. A
similar patch is likely the solution.
** Tags removed: verification-needed
** Tags added: verification-done
** Also affects: gnome-power-manager (Ubuntu
I could not find other relevant gconf changes. And besides, the LiveCD
reproduction, while reproducable, isn't helpful. The Lucid LiveCD has
the RUNNING_UNDER_GDM environment variable set, which disables screen
locking.
This variable was not set in my actual installation. I did think that
Oh my goodness. I've been going by the reproduction steps in comment
#5, where I can't reproduce the problem. But a closer reading of the
original report and the reproduction steps in comment #4 make me realize
I have misunderstood.
The problem isn't that if you wait for your system to be idle,
Found it. Just a straight up bug in gnome-power-manager, it seems.
I've got the lucid debdiff here. Will test and see which other releases
are affected. I will also shortly upload this to lucid-proposed.
** Patch added: blanklock.debdiff
This is not needed for 10.10 or 11.04, as those have redefined the
timeout/sleep_display_ac key to be a timeout *after* the screensaver
determines the system is idle. So you can't hit this bug anymore, as
the screen will never blank when the system isn't idle.
This is also not needed for 11.10,
Hello Joel, or anyone else affected,
Accepted gnome-power-manager into lucid-proposed, the package will build
now and be available in a few hours. Please test and give feedback here.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you in
** Branch linked: lp:ubuntu/lucid-proposed/gnome-power-manager
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/620693
Title:
Screen not locked when turned off
To manage notifications about this bug
Torsten, note that use_screensaver_settings is false in the gconf dump
in comment #9. Step 2b controls /apps/gnome-screensaver/lock_enabled
not /apps/gnome-power-manager/lock/use_screensaver_settings
That said, using the exact same settings from the gconf dump, I also
can't reproduce (7 tries
Same on bare metal after fresh install and following the steps in
comment 5. I feel like there may be a reproduction step that hasn't
been noticed yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Aha! I hit it twice on the LiveCD. I initially thought that not
upgrading after installing 10.04.3 was the answer to reproducing. But I
tried a fresh install and no luck.
One thing I noticed is that on a LiveCD, the Lock screen when
screensaver is active preference is off by default. But on
I did some more structured testing this morning and on 20 occasions the
screen was always locked. However, /apps/gnome-power-
manager/lock/use_screensaver_settings was set to false, not to true as
in step 2b. I'll retest with use_screensaver_settings set to true.
--
You received this bug
10 more tests also resulted in screen being locked. For the record, here
are the gconf keys:
gconftool-2 --get /apps/gnome-power-manager/lock/use_screensaver_settings
true
gconftool-2 --get /apps/gnome-screensaver/lock_enabled
true
gconftool-2 --get /desktop/gnome/session/idle_delay
5
For me it sometimes locks the screen, sometimes it doesn't. From my
testing I could so far not detect any patterns.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/620693
Title:
Screen not locked
@chrisccoulson - I was able to reproduce this. Are you using steps from
comment #5, and are you testing on 10.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/620693
Title:
Screen not locked when
I can't reproduce the bug following comment #5 on Ubuntu 10.04.3 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/620693
Title:
Screen not locked when turned off
To manage notifications about
@chrisccoulson - Here is the output of gconftool -R
/desktop/gnome/session /apps/gnome-power-manager /apps/gnome-
screensaver after I was able to reproduce the issue.
** Attachment added: gconf_keys_requested
I can't recreate this. Could somebody on an affected system please post
the output of gconftool -R /desktop/gnome/session /apps/gnome-power-
manager /apps/gnome-screensaver
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: gnome-power-manager (Ubuntu)
Importance: Low = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/620693
Title:
Screen not locked when turned off
To manage notifications about
** Changed in: gnome-power-manager (Ubuntu)
Assignee: Canonical Desktop Team (canonical-desktop-team) = Chris Coulson
(chrisccoulson)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/620693
Title:
** Changed in: gnome-power-manager (Ubuntu)
Assignee: David Bensimon (davidbensimon) = Canonical Desktop Team
(canonical-desktop-team)
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/620693
Title:
Screen not locked when turned off
To manage
To boil down this bug:
1 -If the screensaver is disabled entirely, the screen does not get
locked.
2 -If the screen is blanked before the screensaver starts the screen
does not get locked.
The first statement, I would assume is to be expected since gnome-
screensaver is the software responsible
I no longer work on the team responsible for maintaining this. I'll
leave it and see if anyone on Goobuntu Team cares to test it or speak
up. It may not be important to them anymore. However, this is really
easy to reproduce, should you want to test it yourself. I just don't
have anything
Thank you for taking the time to report this bug and helping to make
Ubuntu better. A new version of GNOME Power Manager is available on
Maverick and we are wondering if this bug is still an issue for you with
that version? Could you please test and comment back? Thanks in advance.
** Changed in:
The behavior is still the same in Maverick. The screen does not lock
when the screen is blanked, even if lock/black_screen is checked, or
lock/use_screensaver_settings is checked and screensaver lock is
enabled.
The gnome power manager manual also still has inaccurate information
regarding when
31 matches
Mail list logo
