GNOME Bugzilla – Bug 757259
login screen breaks if I don't input the correct password more than three times in a row
Last modified: 2018-07-26 05:16:19 UTC
Created attachment 314336 [details] journal log This is a rather weird issue. if I lock my session and input the password incorrectly more than three times in a row when trying to unlock, the lock screen input freezes. I have to ctrl+alt+f2 and loginctl unlock-session <number> to unlock. I am using autologin. On occasions, it even kicks me out of my session. I'm attaching the journal log.
Basically when it freezes, it gets stuck on 'next' instead of 'unlock'. Incidentally, if I ctrl+alt+f2 and input the incorrect password three times, the console screen resets. Perhaps that is where the "three" failure limit is from.
*** Bug 781504 has been marked as a duplicate of this bug. ***
gdb output in bug 781504.
On my system, entering the incorrect password three times in a row makes the relevant getty process restart. After that I can immediately try logging in again. Maybe this is a hint as to what is happening. Gdm seems to be hiccuping after three failed login attempts instead.
(In reply to Hussam Al-Tayeb from comment #0) > Created attachment 314336 [details] > journal log > > This is a rather weird issue. if I lock my session and input the password > incorrectly more than three times in a row when trying to unlock, the lock > screen input freezes. I have to ctrl+alt+f2 and loginctl unlock-session > <number> to unlock. > I am using autologin. > > On occasions, it even kicks me out of my session. > > I'm attaching the journal log. I'm pretty sure I fixed this same bug for the *login screen* at some point in the past. But that would have been back in 2015 or 2016, certainly well before your previous comment in April 2017. And I probably never tested the unlock screen, which is where you're hitting the problem.
I did some git history investigation to see if I could find where the problem was before, and it turns out it was a downstream problem from a much older version of the login screen code, definitely not relevant anymore. Sorry for the noise.
(In reply to Michael Catanzaro from comment #6) > I did some git history investigation to see if I could find where the > problem was before, and it turns out it was a downstream problem from a much > older version of the login screen code, definitely not relevant anymore. > Sorry for the noise. By downstream, do you mean distribution related?
(In reply to Hussam Al-Tayeb from comment #7) > By downstream, do you mean distribution related? It's irrelevant, but: I think it was actually an upstream bug, but in a much older version of the login screen, so my fix was already obsolete at the time I wrote it and I never sent it upstream. Whatever's going wrong now is surely different.
It's happening on the login screen and not just lock screen. I feel this may be due to me recompiling gdm with --disable-user-display-server
I believe this commit fixed it: https://gitlab.gnome.org/GNOME/gnome-shell/commit/fddd122956d01e7672e7a6e3a4ffc9b696d34916