https://bugs.kde.org/show_bug.cgi?id=455712
henn...@hennsch.de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|DUPLICATE |---
CC| |henn...@hennsch.de
--- Comment #31 from henn...@hennsch.de ---
Switched a gentoo box to 5.25.5 on the weekend and see that weird button every
single time. I can already say that it seems clearly related to pam_u2f and
other are also reporting special pam modules. If i have a yubikey plugged i
need to touch it several times and hit that new "Unlock" button. If there is no
yubikey plugged i can log in with my password like before.
Note that i am using the pam_u2f not as a 2nd factor but as an alternative to a
password so "sufficient" and not "required" ... probably much like the face
recognition someone talked about, or was it fingerprint ... or both?
This was marked as a duplicate of https://bugs.kde.org/show_bug.cgi?id=456210
but it really is not. The "Unlock" button seem to be an effect of any special
pam, maybe one without a password.
> file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9:
> Unable to assign [undefined] to bool
Now when i have one screen i have to hit the button one time. A button i would
not expect at all ...
Adding a second screen meens adding a second push of the new button, and a
second touch of my yubikey. I did not try 3 screens but am willing to guess
what might happen ...
So i open this one back up. That "new" "unlock" button came somewhere between
5.24.6 and 5.25.5, likely in relation to "special pam". And it seems you have
to push it several times when having more than one screen.
--
You are receiving this mail because:
You are watching all bug changes.
