513476 2025-12-17 12:21:00 +0000 Screenlocker tries to login with empty password 2025-12-18 20:36:20 +0000 1 1 4 Plasma plasmashell Screen locking 6.5.4 Other Linux RESOLVED DUPLICATE 481808 NOR normal 1.0 0 hasezoey plasma-bugs-null nate nyanpasu64 0 oldest_to_newest 2477585 0 hasezoey 2025-12-17 12:21:00 +0000 SUMMARY When resuming from sleep or hibernate that is triggered via a lock screen button, it tries to automatically log in with a empty password field, which fails; this is not just cosmetic but can actually lead to lock-outs (which happened to me while debugging https://bugs.kde.org/show_bug.cgi?id=510992). STEPS TO REPRODUCE 1. Have "empty password login" disabled (have a password on your user account) 2. Lock the screen 3. Click either "Sleep" or "Hibernate" button 4. Resume 5. Observe the Screen-locker trying to automatically log back in with a "Unlock failed" plus animation OBSERVED RESULT Screen Locker tries to automatically log in with empty password. EXPECTED RESULT Screen Locker should not try to automatically log in. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.5.4 KDE Frameworks Version: 6.20.0 Qt Version: 6.10.1 Kernel Version: 6.18.1-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 22 × Intel® Core™ Ultra 7 155H Memory: 16 GiB of RAM (15,1 GiB usable) Graphics Processor: Intel® Arc Manufacturer: LG Electronics Product Name: 17Z90SP-G.AA78G System Version: 0.1 ADDITIONAL INFORMATION Note that the only configuration setting i could find is "Screen Locking -> Delay before password required", which is set to "Require password immediately". Note that this *only* happens when the Sleep / Hibernate is triggered by the lock-screen, not if triggered via the start-menu or "systemctl sleep" or any other way. PS: in case it is related to this, i currently have removed the executable permissions from "/usr/lib/kf6/kauth/wakeupsourcehelper", but it also happens if it has executable permissions. 2477964 1 nate 2025-12-18 20:36:20 +0000 *** This bug has been marked as a duplicate of bug 481808 ***