Description of problem:
After I return from suspend, screen doesn't get locked, but it should always do, imho. And I can't find any settings for that issue, so I think it could be a bug.
Version-Release number of selected component (if applicable):
rpm -q pm-utils
rpm -q gnome-screensaver
Steps to Reproduce:
1. go to suspend
2. press key to wake up
The screen isn't locked after suspend.
The screen is locked after suspend.
I see no problem in /var/log/messages.
Created attachment 493416 [details]
output of pm-utils-bugreport-info.sh
Which method did you use for suspending (e.g. HW key, gnome menu or directly pm-suspend from console)?
I've tested all tree ways and only suspending from gnome menu works correctly (screen gets locked). If I press functional key (Fn + F4 by me) or run pm-suspend, then screen stays unlocked.
I've seen another strange behavior: when I click on suspend in gnome menu and have opened Looking Glass (Alt+F2 and run "lg") at the same time, then screen isn't locked as well.
Then, if I do the same without opened Looking Glass, screen is correctly locked.
So, the screen locking after suspend depends on other apps (at least Looking Glass) somehow.
For pm-suspend it is not implemented. pm-suspend is low level utility that knows nothing about your desktop and doesn't communicate with it. Theoretically it could be supported by adding hook which would read g/dconf and then call gnome-screensaver-command but it would tricky to implement and tight to gnome.
For the other cases it should be handled by gnome-power-manager, thus reassigning.
*** Bug 694483 has been marked as a duplicate of this bug. ***
I have just tried Fn + F4, shutting the lid and selecting suspend from the top-right user menu. Only the menu method locked the screen, the other two did not.
Here's what I think is the cause of the problem (and the solution!):
In dconf-editor, the 2 following keys in org/gnome/power-manager are set to true (checked) by default:
However, the descriptive of lock-suspend says: "Whether the screen is locked when the computer wakes up from a suspend. Only used if lock-use-screensaver is false."
Setting lock-use-screensaver to false (unchecked) solves the problem, i.e. I now have locked screen upon resume.
The solutions from mlaverdiere works for me too.
And for me. Perhaps that option should be false by default.
another easy solution - command:
gsettings set org.gnome.power-manager lock-use-screensaver false
thanks for the fix. This is a security hole in my opinion - almost no-one will suspend by using the GUI - they'll close the lid like I do
I can confirm the solution from xaverx above works and agree that locking should be default behavior when closing the lid on a laptop.
Another confirmation of this issue and that the solution from mlaverdiere fixes it.
*** Bug 708543 has been marked as a duplicate of this bug. ***
This is fixed upstream, https://bugzilla.gnome.org/show_bug.cgi?id=650464 : we should probably ensure the fix lands in F15 quickly?
"Pushed to gnome-3-0 and master, many thanks Gary."
This fix was pushed to Gnome in June. Can we get it into Fedora?
gnome-power-manager-3.0.2-2.fc15 has been submitted as an update for Fedora 15.
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gnome-power-manager-3.0.2-2.fc15'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Thanks for the push.
I haven't seen the problem re-occur for suspend/resume yet, but I still definitely get the problem that gnome-screensaver doesn't seem to verify that the screen is actually locked before doing the next thing, be that user switching or whatever. So I think there is still an issue.
there's lots of people on this report but only one logged-in feedback on the update: can some others please test and provide feedback?
NRN (06:15:09) - can you file a new bug for that, perhaps? It's probably better to track it separately from this.
(In reply to comment #21)
> NRN (06:15:09) - can you file a new bug for that, perhaps? It's probably better
> to track it separately from this.
Tricky - it's a general problem I think, nothing seems to check for success. I've reported it as bug 697199, but nobody seems to even care about it (despite how it blows open security on a desktop).
gnome-power-manager-3.0.2-2.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
What's the status of this in Fedora 16? My screen is never locked after suspending, regardless of how I suspend. The previous fix doesn't see to work, there is no lock-use-screensaver key in org.gnome.power-manager any more...
for me in f16, when I resume from suspend, the system looks like it's unlocked for a few seconds, but I can't actually interact with anything. then it 'fades out' and shows the unlock screen.
so it's not behaving correctly, but it's not exactly insecure. and this is a different bug, really, as all the code changed in f16, i think, with the Great Let's Put Everything In gnome-settings-daemon Migration. so we should probably file it separately.
Fedora Bugzappers volunteer triage team