Red Hat Bugzilla – Bug 1295617
After suspend/resume unable to unlock gnome desktop
Last modified: 2016-07-19 16:00:21 EDT
Description of problem:
After doing a suspend/resume on Thinkpad Edge E440 unable to unlock screen.
Version-Release number of selected component (if applicable):
Happens everytime after a suspend/resume.
Steps to Reproduce:
1. Suspend machine (press power button)
2. Resume machine (power button again)
3. Enter password at prompt
No response - just hangs. Does not give an error, just 'spins', then timeouts and goes back to blank screen.
Desktop to unlock
My opening a different virtual console, doing a 'killall -u USER ; killall gdm' it works again (but obviously losing all running applications).
NOTE: Am using auto-login account - not sure if contributes
Nothing obvious in journalctl while trying to unlock (no gnome related errors I could find).
Disable auto-login and now works.
Also - this used to work until an update about a month ago, but not sure exactly when (as don't actually suspend/resume all that often).
My mom is running into a similar issue quite often in F23. I have her setup with auto-login and when she resumes the laptop, she sees the desktop and the mouse moves around, but nothing can be clicked or typed. Nothing in the journal. Doing a kill -HUP on gnome-shell fixes it, but there's no way I'm going to try to explain that to her...
I think it started happening when I upgraded her laptop to F23 just before Christmas.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.