Whenever I put my laptop to sleep, KScreenLocker counts everything that wakes it as a login attempt without a password. If I open the lid, that’s a failed login attempt. If I get a low battery notification, that’s a failed login attempt. If Discord rolls over in its sleep, that’s a failed login attempt. If all of the above occur, that’s three failed attempts and I’m locked out for ten minutes.
This is not ideal. In case the desired behaviour isn’t obvious, I’d like my computer to only count actual attempts to log in as login attempts.
Does anyone have insights? Particular bits of information that would help to diagnose this issue? I would rather not disable faillock, so I’m hoping somebody knows what causes this.
In case it helps, journalctl is full of entries like these:
Aug 03 19:14:00 backuptron kscreenlocker_greet[625408]: pam_unix(kde:auth): unexpected response from failed conversation function
Aug 03 19:14:00 backuptron kscreenlocker_greet[625408]: pam_unix(kde:auth): conversation failed
Aug 03 19:14:00 backuptron kscreenlocker_greet[625408]: pam_unix(kde:auth): auth could not identify password for [admin]
And kinfo gives:
Operating System: Arch Linux
KDE Plasma Version: 6.7.3
KDE Frameworks Version: 6.28.0
Qt Version: 6.11.1
Kernel Version: 7.1.5-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 9 7940HS w/ Radeon 780M Graphics
Memory: 96 GiB of RAM (86.2 GiB usable)
Graphics Processor 1: AMD Radeon 780M Graphics
Graphics Processor 2: AMD Radeon RX 7700S