Red Hat Bugzilla – Bug 660193
cannot Lock Screen
Last modified: 2015-02-17 08:31:46 EST
Description of problem:
I cannot lock the screen when using gnome-shell.
Version-Release number of selected component (if applicable):
F14 and F15 rawhide
Steps to Reproduce:
1. Click on panel User menu -> Lock Screen
screen to lock
happens for both current F14 and F15 gnome-shell.
I'm seeing this problem in F15. When I select "Lock Screen" from the menu in the upper right, nothing happens. The screen is also unlocked when the machine resumes from suspend or screen saver. I have the lock screen option in the "Screen" menu in System Settings set to 5 minutes, and the "Lock" slider is on.
I am also suffering from this issue on Fedora 15 (64 bit). It is pretty important because of my role as Network Administrator to keep my screen locked when I am off doing something away from my computer, so no one can open up Seahorse and see my different passwords.
So I did some digging, apparently gnome-screensaver is responsible for screen locking (maybe this bug should be reassigned). I checked, and gnome-screensaver isn't running, even though it's checked off in gnome-session-properties. I tried running gnome-screensaver manually, and got:
Illegal instruction (core dumped)
I tried reinstalling gnome-screensaver via a yum reinstall, and when I ran gnome-screensaver on the cli again it didn't crash. So I logged out and back in again, and gnome-screensaver was running, with screen locking working properly.
Still not working with Fedora 17. How can this not get any attention? When the unlock screen vulnerability was found, everyone freaked out, but you don't even need the vulnerability if the screen never locks in the first place.
It turns out that "Screensaver" was not ticked in gnome-session-properties. Why, I have no idea. I certainly didn't un-check it myself, because I hadn't even known about gnome-session-properties. Screen locking works now as a result of me toggling the checkbox (and restarting the session).
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.