https://bugs.kde.org/show_bug.cgi?id=515299
Bug ID: 515299
Summary: [kscreenlocker] "Authentication attempt too soon. This
shouldn't happen!"
Classification: Plasma
Product: plasmashell
Version First 6.5.5
Reported In:
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Screen locking
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: 1.0
Created attachment 189054
--> https://bugs.kde.org/attachment.cgi?id=189054&action=edit
Journalctl output since 2026-01-29 21:56:00 containing the title error
SUMMARY
Around two weeks ago, I first noticed an issue with the kscreenlocker that
would leave me unable to log back into my user session after my screen locked
due to inactivity. I am not 100% certain how to reproduce the bug, but when I
manage to reproduce it, I end up in the situation where I can still type in
characters into the lock screen password field, but I can't submit the password
(pressing enter/clicking the submit button no longer works).
STEPS TO REPRODUCE
1. Lock the screen (either manually or by user inactivity)
2. Type in an incorrect password and hit enter
3. Wait until the incorrect password animation is done and a new password can
be entered
4. Type in the correct password and hit enter
OBSERVED RESULT
I am not logged back in. The password field remains filled, no animation plays,
nothing happens - as if I hadn't pressed enter.
EXPECTED RESULT
The password should be checked and confirmed, and I should be back in my
session.
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.18.7-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 20 × 12th Gen Intel® Core™ i7-12700K
Memory: 69 GB of RAM (67.1 GB usable)
Graphics Processor: AMD Radeon RX 7900 XTX
ADDITIONAL INFORMATION
When this problem occurs, there is an error line in my journalctl that reads:
Jan 29 20:02:42 Cre8or-PC kscreenlocker_greet[44136]: [PAM worker kde]
Authentication attempt too soon. This shouldn't happen!
I *think* this might be related to a recent change where there was an initial
delay before the incorrect password animation (text field wiggles a few times)
starts playing, which is no longer present. Currently the animation plays
immediately, so I'm hypothesising that the reduced overall delay between
password prompts causes the password field to reset too early, which causes the
title error to appear in my journalctl.
--
You are receiving this mail because:
You are watching all bug changes.
