SUMMARY I set up Plasma 6 with kdesrc-build following [1] and [2] alongside Plasma 5.27.9 from the Arch repos, and after entering the new Plasma 6 session via SDDM I found that the lock screen doesn't let me unlock my session, so I have to unlock the session via the `loginctl unlock-session` command instead. In particular, the mouse cursor just flashes all the time in the lock screen, and while hovering over where the password entry field would be does make the cursor switch to the I shaped thing typing my password and pressing Enter still doesn't let me through. When the issue is occurring I see these two lines appear repeatedly in the system logs, despite my system having neither fingerprint nor smartcard authentication: > kscreenlocker_greet[5762]: pam_warn(kde-fingerprint:auth): function=[pam_sm_authenticate] flags=0 service=[kde-fingerprint] terminal=[<unknown>] user=[m7] ruser=[<unknown>] rhost=[<unknown>] > kscreenlocker_greet[5762]: pam_warn(kde-smartcard:auth): function=[pam_sm_authenticate] flags=0 service=[kde-smartcard] terminal=[<unknown>] user=[m7] ruser=[<unknown>] rhost=[<unknown>] I'm not sure if this is expected due to Plasma 6 not being installed to the system directly, like the issue with KAuth noted in [3], but if so having it mentioned there would be great (unless it's noted somewhere else already and I just missed it?). [1]: https://community.kde.org/Get_Involved/development/Set_up_a_development_environment [2]: https://community.kde.org/Get_Involved/development/Build_software_with_kdesrc-build [3]: https://community.kde.org/Plasma/Plasma_6#Known_issues STEPS TO REPRODUCE 1. Build Plasma 6 via kdesrc-build 2. Run the dev session via SDDM 3. Lock the screen OBSERVED RESULT It is impossible to unlock the screen via the GUI. EXPECTED RESULT The password field should appear to allow unlocking the screen. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.6.0 Kernel Version: 6.5.9-arch2-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION kscreenlocker is at commit 6777145016231427cccb4721de1e469a1512715c when I built it.
Can confirm. Also happens for me with Arch and QT6.6 on Master. Running: QT_LOGGING_RULES='kscreenlocker_greet=true' /home/duha/kde/usr/lib/libexec/kscreenlocker_greet --testing --theme /home/duha/kde/usr/share/plasma/look-and-feel/org.kde.breeze.desktop/ Repeats the the same message over and over again until I kill the screenlocker: kscreenlocker_greet: PamAuthenticators: Availability changed for non-interactive authenticator kde-fingerprint true kscreenlocker_greet: PamAuthenticators: Availability changed for non-interactive authenticator kde-smartcard true kscreenlocker_greet: PamAuthenticators: Non-interactive authenticator kde-smartcard failed kscreenlocker_greet: PamAuthenticators: state changing from PamAuthenticators::Authenticating to PamAuthenticators::Failed kscreenlocker_greet: PamAuthenticators: Availability changed for non-interactive authenticator kde-smartcard false kscreenlocker_greet: PamAuthenticators: Non-interactive authenticator kde-fingerprint failed kscreenlocker_greet: PamAuthenticators: Availability changed for non-interactive authenticator kde-fingerprint false kscreenlocker_greet: PamAuthenticators: starting authenticators kscreenlocker_greet: PamAuthenticators: state changing from PamAuthenticators::Failed to PamAuthenticators::Authenticating kscreenlocker_greet: [PAM worker kde-fingerprint] Authenticate: Starting authentication kscreenlocker_greet: [PAM worker kde-smartcard] Authenticate: Starting authentication kscreenlocker_greet: [PAM worker kde-smartcard] Authenticate: Authentication done, result code: 7 (Authentication failure) kscreenlocker_greet: [PAM worker kde-fingerprint] Authenticate: Authentication done, result code: 7 (Authentication failure)
Does the problem go away if you change your system's PAM configs per the instructions linked to at https://community.kde.org/Plasma/Plasma_6#PAM_configuration?
Oh, I tried the "steal from GNOME" method there after installing GDM and it worked! Seems like the documentation might need to be updated to make it a requirement instead of just for simultaneous password+fingerprint authentication then.
Didn't work for me, neither did the other method. But i think this is likely an issue with my setup up, maybe I have screwed up the pam files. So if you want you can close this bug and I will reopen once I am certain it is not an issue on my end (unlikely).
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
It's been working for me ever since I copied over the PAM config from GNOME, so I guess this isn't really a problem assuming distros sort it out properly when they package Plasma 6.