Password (the correct one) doesn't work randomly (after fresh Install, after an update, and even when witthin a logged-in session in terminal) and frequently

Issues & Assistance
21

Hello people. I can reproduce this issue consistently, every time I try, it fails.

So what files do you need me to send for you to diagnose the issue?

This is NOT caused by:

  • incorrect password
  • different keyboard layout
  • a kernel panic
  • faillock, as it has been disabled

This is caused by:

  • logging into a Cosmic session
  • closing the laptop lid and opening it again

Session is locked, entering the password correctly is not enough, it is never recognized again. The lockout happens after you enter the correct password three times.

So the issue is not the lockout itself, it is that it can’t recognize the correct password when it should.

22

I’ve had this occur in tbe past. it wasn’t overtly faillock - or at least didn’t involve anything that should have triggered faillock.. No caps or num lock was involved. It resolved with a reboot. Because it resolved I dropped it. I think at the time I was able to log in via TTY as mentioned by @Mewsse

23

Happend to me too yesterday and today. Both times, a reboot did solve the problem.

24

So for those who it is not faillock* ..

It is specifically the Cosmic screen locker (whatever that is) - rather than password not being accepted by the system (whether sudo or systemd or pam etc). Just that screen locker? Possibly “Cosmic” as a whole in some way?


* - It seems we might have a mixture of reports going on here. A not insignificant number probably still are just faillock as outlined above. Linking for their benefit; Password (the correct one) doesn't work randomly (after fresh Install, after an update, and even when witthin a logged-in session in terminal) and frequently - #14 by cscs

25

I’ve had cases where sddm won’t accept input (can type in the password, but neither enter nor clicking actually submit it for validation) following wake from sleep. Have not tried cosmic.

26

I did have what sounds like this happen to me in some odd case where I had hit ESC after mashing the password .. and it sorta borked the whole lockscreen. I could type but not really do anything and had to restart. Thought it was an odd quirk though and I have not been able to reproduce.

But was it SDDM for you?
SDDM should only be after boot - if on Plasma for example post sleep/lock you would be met with kscreenlocker.
If it really is SDDM somehow that is fine but I am just trying to be sure.

27

I have a vague impression that kscreenlocker did it, so i tried clicking back to login as s new session, then tried restarting sddm and logging in again from there and the problem persisted in sddm. I wasn’t really taking notes and didn’t really dig deeper than “ultimately needed to reboot”.

28

@untamedunbranded Just recently had this happen after an update, did you eventually resolve this?

29

Maybe this?