GNOME Bugzilla – Bug 782619
Sometimes screen lock gets stuck when unlocking
Last modified: 2018-05-24 11:35:37 UTC
When unlocking GNOME Shell after the screen is locked, sometimes you can type your password, but the rotating-pause-animation never stops and the screen is never unlocked. You can cancel this with the Cancel button (or Escape key) and usually you can get passed the screen lock on the second attempt.
I have experienced this for a while. The Ubuntu bug is from Ubuntu 14.04 LTS (GNOME 3.10) and I still experienced it with gdm 3.24.1.
I have also experienced this bug for some time, on various different versions of GNOME. I am currently using GNOME 3.22.2 on Fedora 25. I never succeed by just pressing Cancel and trying again. What does work, is hitting Ctrl+Alt+F1, which gets me back to the main login screen. From there, I can select my user account, type the password, and get back in (my session stays intact). For what it's worth, I use an external monitor. I don't know if this is related though. I've certainly seen the problem when not plugged into the external monitor, but I'm unsure if the bug only manifests after I have plugged in at some point since I last rebooted.
Created attachment 357337 [details] journalctl output from hang Hopefully a useful log. Gnome 3.24.3 on Arch Linux. Had to put the system to sleep and wake it back up in order to get in. Happens pretty consistently every morning if I leave the system running before bed.
Looks related. https://github.com/systemd/systemd/issues/6375
I've been experiencing this problem for several months. The lock screen appears, but the keyboard doesn't respond. Sometimes I can type a few characters in the password field before it stops responding. I can move my mouse and click the button on the top right of the screen to re-lock and try again. Eventually it works. gnome shell: 3.26.2 gdm: 3.26.2.1
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/311.