SUMMARY On a full plasma -git session (Frameworks and Plasma Workspace/Desktop and everything else from git master), kscreenlocker(-git) will *always* say authentication failure. Trying to get any proper information by using the test greeter application is quite useless as it'll just say "Authentication Failure". Logging anywhere else works. TTY works, so I can just switch to a tty and type loginctl unlock-session 1, but this is not ideal. I can also "switch user" to my own user and it'll unlock the session just fine. I checked all the culprits: capslock is off, so is anything else that could make this not work. I actually even clicked "show password" and looked at it, the password is correct. STEPS TO REPRODUCE 1. Try to unlock your computer on -git plasma OBSERVED RESULT Unlock doesn't work at all. EXPECTED RESULT Being able to unlock my session with the correct password. SOFTWARE/OS VERSIONS Linux: 5.10.9 KDE Plasma Version: 5.21.80 KDE Frameworks Version: 5.79 Qt Version: 5.15.2 ADDITIONAL INFORMATION Whole session is git master. KScreenLocker test greeter logs will just display "Authentication Failure" no matter what. This has been reproduced by all users of the plasma-git session from chaotic-aur. The PKGBUILD used for kscreenlocker is https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=kscreenlocker-git, but trying just the normal kscreenlocker (not from git) doesn't work either.
Created attachment 135073 [details] /usr/lib/libexec/kscreenlocker_greet --testing logs
Going back to KDE Frameworks 5.78 and kscreenlocker 5.20.80 fixes the issue. Since 5.79 is really early work, it's probably a fluke more than anything, but just putting this one the table for clarification.
Confirming this behavior, running -git branch as well. Happens on both X and Wayland sessions. Operating System: Arch Linux KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.11.8-zen1-1-zen
So many auth-related bugs from Arch users. :(
>Going back to KDE Frameworks 5.78 and kscreenlocker 5.20.80 fixes the issue. Since 5.79 is really early work, it's probably a fluke more than anything, but just putting this one the table for clarification. Given this was feb and we've had releases since then, it was clearly some setup issue.
*** Bug 443473 has been marked as a duplicate of this bug. ***