https://bugs.kde.org/show_bug.cgi?id=458130
Nate Graham <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM Summary|Fingerprint authentication |Fingerprint authentication |sometimes fails to activate |only activates after trying |immediately; sometimes |to authenticate with the |activates after a few |wrong password |seconds, and sometimes only | |activates once you try to | |enter an incorrect/empty | |password once | --- Comment #19 from Nate Graham <[email protected]> --- (In reply to Philippe ROUBACH from comment #16) > If I understand well the chapter "Using a fingerprint reader" here > https://wiki.archlinux.org/title/SDDM#Using_a_fingerprint_reader > then it is normal to expect to get first the password field, then by typing > "enter" with an empty password field to get the fprint dialog. > > If I sum up : > > to get only fprint dialog you add in sddm file > > auth sufficient pam_fprintd.so > > to get password field then fprint dialog you add in sddm file > > auth [success=1 new_authtok_reqd=1 default=ignore] > pam_unix.so > try_first_pass likeauth nullok > auth sufficient pam_fprintd.so > > What do we add to get fprint dialog then password field dialog as a backup ? It sounds like this is caused by a configuration problem. Here's KDE's documentation for how to configure PAM to make this work as expected: https://community.kde.org/Distributions/Packaging_Recommendations#PAM_configuration Can you communicate this to the maintainers of your distro? -- You are receiving this mail because: You are watching all bug changes.
