https://bugs.kde.org/show_bug.cgi?id=524786
michaelk83 <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from michaelk83 <[email protected]> --- PAM should immediately start a `ksecretd` instance with a `--pam-login` argument. Check if that instance is crashing. If so, that's almost certainly bug 524522. After that, it should get restarted on demand (the ~10 seconds to 30 minutes delay you're seeing), but that 2nd instance doesn't have access to the PAM credentials. -- You are receiving this mail because: You are watching all bug changes.
