https://bugs.kde.org/show_bug.cgi?id=507023
Edmund <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|DOWNSTREAM |--- Status|RESOLVED |REOPENED CC| |[email protected] Ever confirmed|0 |1 --- Comment #13 from Edmund <[email protected]> --- I can reproduce this on Archlinux. Without the `kde` file, `KScreenLocker` cannot authenticate and throws errors like this repeatedly: `kscreenlocker_greet[9241]: pam_warn(kde:auth): function=pam_sm_authenticate … service=[kde]` This might have been interpreted by the OP as "Enter being hit repeatedly", as the screen has a visible refresh, and shows something to the line of "Authentication failed". Questions: 1. Is PAM the only authentication way? Most OS's (Archlinux, Debian, FreeBSD) appear to provide a PAM service file called `kde`. Fedora, on the other hand, does not; which leads me to the next question: 2. Is there a way that `KScreenLocker` will work with, say, just `systemd-logind`, if configured correctly - and then PAM is involved via `logind`, rather than directly via a PAM service file called `kde`? Thank you for your time and sharing of knowledge, to further investigate this! -- You are receiving this mail because: You are watching all bug changes.
