SUMMARY Support systemd-homed users when a FIDO U2F device is used with a PIN. Devices without a PIN work as expected in both sddm and kscreenlocker. When the user presses enter on a blank password dialog, the FIDO device prompts for presence and unlocks the computer. Once a PIN is registered, this process breaks. Sddm works if pin is entered as password dialog before enter. However, kscreenlocker no longer is capable of accepting the FIDO device to unlock the computer. STEPS TO REPRODUCE 1. Plug in FIDO device such as Solo or Yubikey, setup FIDO2 device with PIN. 2. Create systemd-homed user `homectl create foo --fido2-device=auto` 3. Follow prompts to enter PIN and register FIDO device with homed. Reboot. 4. Login with sddm by entering PIN in password dialog and activating device. 5. Lock screen. Attempt to unlock by pressing enter with blank password dialogue. OBSERVED RESULT Login failed. Password prompt unlocks. The FIDO device is not polled. EXPECTED RESULT kscreenlocker polls FIDO device and prompts for PIN entry (or allows PIN entry instead of password like SDDM). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux 5.15.15-zen1-1-zen KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Related tickets: 430828, 396703
Can you check to see if this is still not working as expected on the lock screen in Plasma 5.26 or 5.26? Many PAM-related changes happened.
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!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!