I cant take down lock screen with password if its been on for a long time ( more than 15 mins )

Ask Fedora
,
1

I have recently moved from Fedora 33 to 34. Everything works fine and system is stable. But, I have been dealing with a rather annoying problem. If I let the lock screen kick on automatically and come back to the computer after about an hour I cannot simply enter my password to take down the lock screen. After I enter the password and press enter, I get the spinning wheel for about 40-60 seconds and then I am greeted with a blank dark screen. If I press CTRL-ALT-F2 to go to a tty, I can login to the tty. Then I press CTRL-ALT-F1 and I am presented with the gdm greeter. On this screen I can pick my user name, login and I am back in business. This whole process takes about 2 minutes.
Here is a journalctrl output from when this problem happens:

========================================>

May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) systemd-logind: got pause for 13:69
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) systemd-logind: got pause for 13:64
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) systemd-logind: got pause for 13:73
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) systemd-logind: got pause for 13:68
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) systemd-logind: got pause for 13:74
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) systemd-logind: got pause for 13:76
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) systemd-logind: got pause for 13:65
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) systemd-logind: got pause for 13:78
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) systemd-logind: got pause for 13:66
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) systemd-logind: got pause for 13:79
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) systemd-logind: got pause for 13:72
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) systemd-logind: got pause for 13:67
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) systemd-logind: got pause for 226:0
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) systemd-logind: got pause for 13:81
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) systemd-logind: got pause for 13:71
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) systemd-logind: got pause for 13:75
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) AIGLX: Suspending AIGLX clients for VT switch
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) event12 - HOLTEK USB-HID Keyboard Consumer Control: device removed
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (**) Option "fd" "43"
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) event5  - HID 04b4:6014 Consumer Control: device removed
ay 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (**) Option "fd" "36"
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) event17 - Eee PC WMI hotkeys: device removed
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (**) Option "fd" "45"
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) event14 - HOLTEK USB-HID Keyboard: device removed
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (**) Option "fd" "44"
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (**) Option "fd" "43"
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) event11 - HOLTEK USB-HID Keyboard System Control: device removed
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (**) Option "fd" "42"
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) event10 - HOLTEK USB-HID Keyboard Mouse: device removed
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (**) Option "fd" "41"
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) event9  - HOLTEK USB-HID Keyboard: device removed
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (**) Option "fd" "40"
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) event15 - Logitech USB-PS/2 Optical Mouse: device removed
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (**) Option "fd" "39"
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) event8  - HID 04b4:6014: device removed
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (**) Option "fd" "38"
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) event7  - HID 04b4:6014 Keyboard: device removed
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (**) Option "fd" "37"
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (**) Option "fd" "36"
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) event4  - HID 04b4:6014 System Control: device removed
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (**) Option "fd" "35"
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) event3  - HID 04b4:6014 Mouse: device removed
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (**) Option "fd" "34"
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) event2  - HID 04b4:6014: device removed
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (**) Option "fd" "33"
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) event0  - Power Button: device removed
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (**) Option "fd" "32"
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (II) event1  - Power Button: device removed
May 28 11:31:55 edhl06 gsd-media-keys[55059]: Unable to get default sink
May 28 11:31:55 edhl06 kernel: rfkill: input handler enabled
May 28 11:31:55 edhl06 /usr/libexec/gdm-x-session[54685]: (**) Option "fd" "29"
============================================================

Anyone else experience this problem with lock sreen?

2

That probably should be filed as a bug. I don’t see it with my VM and have not yet converted my PC to F34 on the bare metal.

3

FYI, I recently found the same exact behaviour. Worse… every once in a while I could log in just fine.

Thus far I’ve spent a few weeks and I still haven’t been able to isolate it to the root cause. That said I was able to isolate why it worked sometimes. Ironically, the reason it worked sometimes was user error. :grinning:

I realized that when I went to type in my password the user name directly above the password field was blank. When I hit “enter” the screen would hang endlessly until changing to another tty (including ReserveVT as specified by logind.conf) at which point if I when I authenticate, I’m returned to my previous session.

On the other hand, if I made a typo (at which point my muscle memory hits ESC twice quickly to toggle “away” from the lock screen and back) the username would be present. As long as the username was present on the lock screen, I could authenticate successfully.

Very, very curious. :thinking:

1 Like