https://bugs.kde.org/show_bug.cgi?id=469951
postix changed:
What|Removed |Added
CC||pos...@posteo.eu
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=469951
Nate Graham changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=469951
--- Comment #3 from Aaron Kelley <09_strays_fli...@icloud.com> ---
(As a note for anyone who may look into this. libpam-fprintd documentation
suggests that setting "-1" for an "unlimited" timeout is allowed, but that is
*also broken* in the current
https://bugs.kde.org/show_bug.cgi?id=469951
--- Comment #2 from Aaron Kelley <09_strays_fli...@icloud.com> ---
I would suggest that kscreenlocker should just go with whatever timeout PAM is
configured to use. Since PAM is used in more places than just kscreenlocker,
it isn't really KDE/Plasma's
https://bugs.kde.org/show_bug.cgi?id=469951
Nate Graham changed:
What|Removed |Added
Keywords||usability
