| Summary: | Password wont be accepted when fingerprint is configured | ||
|---|---|---|---|
| Product: | [Unmaintained] kscreenlocker | Reporter: | Matt <m.mcnutt> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | bshah, jackyzy823, kde, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.23.90 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Matt
2022-01-18 00:32:06 UTC
This message is coming straight from fprint, so it's a finger recognition issue in fprint itself. Unfortunately there's nothing we can do about it in KDE code. I sometimes get the same thing and have to do it a few times before my finger is accepted. And I've notices that when my fingers are wet, it won't work. I was unable to unlock right after coming out the shower the other day lol isnt it a kscreenlocker logic issue tho? - if a password has been supplied, it should straight out skip the fprint part and unlock normally Ohh! Sorry, I misread the issue. Nonetheless, it is still an upstream issue, albeit a different one. When fprint auth is in use, polkit prevents using your password. You can see this in non-kscreenlocker polkit auth prompts as well. It really shouldn't do this. But I think this is an issue in polkit itself. (CCing David Edmundson who can correct me if I'm wrong) I was looking further into this and came across the archwiki suggestion (https://wiki.archlinux.org/title/Fprint#Login_configuration) for /etc/pam.d/kde config file to add auth sufficient pam_unix.so try_first_pass likeauth nullok essentially if password null, ask for fprint, but it looks like plasma generates these files using authselect, so I was hesitant to mess with them as I dont really want to break my config |