https://bugs.kde.org/show_bug.cgi?id=520817
--- Comment #5 from TraceyC <[email protected]> --- Thanks for the update. This is what Sumit is suggesting in the Fedora report > The krb5_child.log shows that it was started at 20:47:33 to collect to > available authentication methods but never got an authentication attempt > back. The PID (7945) was not cleared in the backend so that the next attempt > failed because there was no process anymore which could handle it. > unfortunately I cannot think of a workaround from the SSSD side because the > related timeout is hardcoded to 5 minutes. Maybe there is a way to tell the > KDE lock screen to not call `pam_authenticate()` immediately after locking > the screen but only after some user interaction? -- You are receiving this mail because: You are watching all bug changes.
