I'm not sure if it's related, but I just then experienced the same thing. I was
able to use the computer for about 30 seconds after being away from the
computer for 20 minutes.
The computer wasn't in sleep mode, but the screensaver had kicked in. When I
moved the mouse I was able to do things,
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2006-7240
--
Screen not locked on resume from hibernate/suspend
https://bugs.launchpad.net/bugs/42052
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
Fixed in yesterday's update.
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed = Fix Released
--
Screen not locked on resume from hibernate/suspend
https://bugs.launchpad.net/bugs/42052
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
OK by me - and by the looks of it a fix happened yesterday that seems to
work for me (just as I got round to trying to figure out how this
worked!).
Dave
--
Screen not locked on resume from hibernate/suspend
https://bugs.launchpad.net/bugs/42052
You received this bug notification because you
Bug 428115 is a fresh bug report dealing with this issue on Karmic and
I'd prefer to use that to track progress on the bug. Barring any
objections I'd like to set this back to Fix Released.
--
Screen not locked on resume from hibernate/suspend
https://bugs.launchpad.net/bugs/42052
You received
on my laptop, i had this issue with 8.10, it was resolved with 9.04 but
appeared again with 9.10 ...
--
Screen not locked on resume from hibernate/suspend
https://bugs.launchpad.net/bugs/42052
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
I have found that using xscreensaver instead of gnome-screensaver results in
the session resumes as locked.
(Currently, it is also locking me out every time I close the lid ... but that
is less of a problem since the security problem has been resolved.)
I am also using xfce4-power-manager
Moving this bug to xscreensaver since it exists when you are using a
different power manager and does not exist when using gnome-screensaver.
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Triaged
** Also affects: xscreensaver (Ubuntu)
Importance: Undecided
Status:
no ... it does NOT exist when using xscreensaver and xfce4-power-manager
it DOES exist when using gnome-screensaver and gnome-power-manager
(those are the only two combination I've tested ... if you want to move it,
it should go to gnome-screensaver)
2009/9/8 Scott Howard showard...@gmail.com
also ... before calling it invalid against gnome-power-manager, someone
should try the combination:
gnome-power-manager + xscreensaver
2009/9/8 Sean Kennedy sean.wor...@gmail.com
no ... it does NOT exist when using xscreensaver and xfce4-power-manager
it DOES exist when using gnome-screensaver
Thanks for the pointing it that out, sorry I misread it. I'm resetting
this bug to the previous state.
** Changed in: gnome-power-manager (Ubuntu)
Status: Invalid = Confirmed
** Changed in: xscreensaver (Ubuntu)
Status: New = Invalid
--
Screen not locked on resume from
Same problem on an acer aspire 6920 with karmic
--
Screen not locked on resume from hibernate/suspend
https://bugs.launchpad.net/bugs/42052
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
I wonder if the resurgence of this bug has anything to do with Bug
397892 (Screensaver does not turn on [Ubuntu/Xubuntu Karmic])
--
Screen not locked on resume from hibernate/suspend
https://bugs.launchpad.net/bugs/42052
You received this bug notification because you are a member of Ubuntu
Bugs,
On Karmic this bug has returned for me; this was working for the last
couple of years but has come back in the last 2 or 3 weeks of Karmic -
so since this bug was marked as 'incomplete someone try karmic' - sorry,
it's back - although to be fair I suspect it's a different bug since the
original
This also happens sometimes on my SAMSUNG R700 Aura on amd64.
--
Screen not locked on resume from hibernate/suspend
https://bugs.launchpad.net/bugs/42052
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
Thanks for checking, setting it back to confirmed.
(This is an existing bugs that still exist and can be fixed in Karmic.)
--
Screen not locked on resume from hibernate/suspend
https://bugs.launchpad.net/bugs/42052
You received this bug notification because you are a member of Ubuntu
Bugs,
I see this with xfce4 in 9.04.
This should be marked as a security issue.
Call me dumb, but it took me at least a month to clue in that when I suspended
my computer that I didn't need a password to resume.
During all that time my computer was insecure whenever suspended.
--
Screen not locked on
Has anyone tested this bug with Karmic yet? There has been significant
changes to GPM from Jaunty to Karmic, and if this is not fixed in Karmic
we should work on it. While it is a security issue, Ubuntu tends to be
extra careful in allowing SRUs. The best course of action would be to
get it fixed
I marked as incomplete until it is checked in Karmic, then it can go
back to confirmed.
--
Screen not locked on resume from hibernate/suspend
https://bugs.launchpad.net/bugs/42052
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
Still experiencing this issue with Kubuntu 9.04
--
Screen not locked on resume from hibernate/suspend
https://bugs.launchpad.net/bugs/42052
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
Experiencing the same here with UNR 9.04 Jaunty.
--
Screen not locked on resume from hibernate/suspend
https://bugs.launchpad.net/bugs/42052
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
Forest, do you mean the Action Buttons panel item by the power applet?
--
Screen not locked on resume from hibernate/suspend
https://bugs.launchpad.net/bugs/42052
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing
When I said power applet on the panel I meant the little power plug
icon that lives near the clock on my xfce panel. Now that you mention
it, I don't think it's a panel applet after all. That icon appears in
the notification tray when I select Always display an icon in the xfce
Power Management
This problem still exists after upgrading to Intrepid. (It worked fine
before upgrading from Feisty to Gutsy.)
When I choose to hibernate using the power applet on the panel, the
screen fades to black before hibernating, and is locked when I resume
from hibernation. I'm guessing that fade
In 8.10:
In Gnome:
You can get screen locked in Gnome, it you check Lock screen... in
Screensaver preferences.
In Xfce4:
Additionally choose Power Management in Screensaver preferences and choose a
way to suspend/hibernate.
You can not use the Ask me option in Power Management preferences like
I think that this is not a gnome-only issue, I have the same one with
Kubuntu Intrepid with KDE4.
It worked perfectly with Hardy, it got broken after upgrading to
Intrepid.
--
Screen not locked on resume from hibernate/suspend
https://bugs.launchpad.net/bugs/42052
You received this bug
The same happens with the latest xubuntu 8.10 rc. Screensaver options
are set to lock, after resume screen is unlocked.
--
Screen not locked on resume from hibernate/suspend
https://bugs.launchpad.net/bugs/42052
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Same in hardy
maybe putting a script in a pm-tools directory to lock the screens (and
open consoles Alt-Ctrl-F1, ...)
--
Screen not locked on resume from hibernate/suspend
https://bugs.launchpad.net/bugs/42052
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@ceg, in all hardy test installs i have ever seen the keys are set like:
/apps/gnome-power-manager/lock/hibernate: true
/apps/gnome-power-manager/lock/suspend: true
/apps/gnome-power-manager/lock/use_screensaver_settings: false
do you say thats not the case for you ?
--
Screen not locked on
Re-opening in hopes that someone will notice this is not entirely fixed.
Gutsy is still broken where Feisty worked.
** Changed in: gnome-power-manager (Ubuntu)
Status: Fix Released = Confirmed
--
Screen not locked on resume from hibernate/suspend
https://bugs.launchpad.net/bugs/42052
You
It's still broken for me.
If I hibernate using the power manager icon in the notification area, I
am prompted for my password when I resume. If I hibernate using the
usual Quit / Log Out menu, the password prompt is bypassed when I
resume.
Xfce desktop.
Upgraded from Feisty to Gutsy.
gnome-power-manager (2.20.0-0ubuntu2) gutsy; urgency=low
* adjust the default gconf paths for our default keys so the defined
default behavior is the same as in feisty. to address the return of
LP: #42052 and LP: #39448
-- Oliver Grawert [EMAIL PROTECTED] Wed, 26 Sep 2007 01:16:44
** Attachment added: gnome-power-manager_2.19.92.debdiff for enabling the
lock_use_screensaver_settings per default
http://launchpadlibrarian.net/9307218/gnome-power-manager_2.19.92.debdiff
--
Screen not locked on resume from hibernate/suspend
https://bugs.launchpad.net/bugs/42052
You
This still happens in Gutsy but a fix is much more easier.
It is a good idea to lock screen on suspend/hibernate only if people want it.
Everybody who enables screen saver locking wants to lock screen on
suspend/hinbernate too.
The easiest solution for this is to enable the gconf option
(This started happening for me when I upgraded to Gutsy latest on ~
August 25)
This needs to be slightly separate from screen saver settings; the
choice of locking screen when the screen saver pops in and when you come
out of hibernation are certainly different for me; it's also a change in
The fix is what Jean mentioned. When gnome-power-manager starts suspend
it sends a dbus message to gnome-screen-saver that the machine is now
inactive. That kicks on the screen saver. During the resume a dbus
message is sent that the system is now active and to disable the screen
saver. If you
36 matches
Mail list logo