https://bugs.kde.org/show_bug.cgi?id=524522
--- Comment #19 from michaelk83 <[email protected]> --- What I'm less clear about is why these reports started only recently, with 6.29. It might just be a coincidental external change, but this part of comment 4 suggests it may be something that was recently changed in the PAM instance initialization: > The crash is deterministic and reproducible, but only in the first > instance of ksecretd started by SDDM with --pam-login. After the > crash, when ksecretd is automatically restarted (without --pam-login), > the crash never reproduces again for the rest of the session, > regardless of how many times the same secret is requested. -- You are receiving this mail because: You are watching all bug changes.
