https://bugs.kde.org/show_bug.cgi?id=524373
--- Comment #7 from Nicolas Fella <[email protected]> --- (In reply to michaelk83 from comment #3) > The fact that KWalletManager (which uses the legacy KWallet API) does see > the wallet as unlocked, suggests this isn't an unlocking problem, but rather > a state synchronization problem between the legacy API and Secret Service. > This is similar to the old bug 459287, but may be a different cause. yes, ever since the kwalletd/ksecretd split the (un)locked state synchronization between the KWallet and Secrets API is completely broken, which doesn't make this any easier to diagnose -- You are receiving this mail because: You are watching all bug changes.
