https://bugs.kde.org/show_bug.cgi?id=486294
Bug ID: 486294
Summary: Better PAM recommendations to distributions (no
nologin).
Classification: Plasma
Product: kscreenlocker
Version: git-master
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: descartav...@gmail.com
Target Milestone: ---
following recommendations on
https://invent.kde.org/plasma/kscreenlocker/-/merge_requests/163 my distro
adopted these files[0] in place of what was being shipped before[1].
One downside of the recommendation is that *unlocking* the desktop is now
prevented if there's a shutdown scheduled (or other reason to have the
`nologin` file present). because of the line `auth requisite pam_nologin.so`.
It is very frustrating if you get a notification on your lock screen about the
system going down in 5min and all you can do is nervously wait to lose your
work.
Are there good reasons to have the auth nologin module there? Can we recommend
without it? Should we have sample files in this upstream distribution and avoid
the communication issues? most packages i've seen just added the recommended
text to their packaging script, and now you don't know if they are following
upstream or not. Specially now that we cannot build without PAM?
(https://bugs.kde.org/show_bug.cgi?id=455303)
--
[0]
https://gitlab.archlinux.org/archlinux/packaging/packages/kscreenlocker/-/commit/7fd674f638497ba84e788118d3bbc524691974f0#6d3349510821738885fce1ed921375cb34e361f1
--
[1]
https://wiki.archlinux.org/index.php?title=SDDM&oldid=805510#Using_a_fingerprint_reader
```
#/etc/pam.d/kde
auth sufficient pam_unix.so try_first_pass likeauth
nullok
auth sufficient pam_fprintd.so
```
--
You are receiving this mail because:
You are watching all bug changes.
