https://bugs.kde.org/show_bug.cgi?id=514326
Christian Hacker <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REPORTED Resolution|DUPLICATE |--- --- Comment #3 from Christian Hacker <[email protected]> --- (In reply to michaelk83 from comment #2) > You also reported the same in bug 507778. At this point, until bug 490788 is > fixed, you can assume that *all* secretd crashes you see are 490788. There's > no need to submit any more reports of those. Thanks. > That said, since you're getting multiple instances of this crash, if you can > determine repeatable steps to reproduce, you may post those in bug 490788. The difference between the two faultreports from the past three days is that the newer 2nd one gave information about kded6 and was made on an updated current Tumbleweed software platform. Which is definitely different to Leap 15.6 from 2024-07-24 (aka bug 490788). In my experience, it is unhelpful to attempt to repair a present software platform with a historic fault reference in a different operating system. If I really may be able to reproduce the fault reliably as a novice in my present software platform, I will definitely not attribute such to Leap 15.6. > See also bug 490788 comment 24 for a possible workaround, aka: >> In Debian testing, after installing libpam-kwallet5, the problem disappeared. >> With libpam-kwallet5, ksecretd runs like /usr/bin/ksecretd --pam-login 14 12 As described, this faultreport is for the current Tumbleweed, like: kf6-kded v6.21.0-1.1, kf6-kwallet v6.21.0-1.1, kf6-kded. It would also be helpful, if the interworking with Drkonqi could be fixed, because that would maybe ease finding out where all it may go wrong. Best regards -- You are receiving this mail because: You are watching all bug changes.
