https://bugs.kde.org/show_bug.cgi?id=435643
Sandro Knauß <skna...@kde.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |skna...@kde.org Ever confirmed|0 |1 Status|REPORTED |CONFIRMED --- Comment #4 from Sandro Knauß <skna...@kde.org> --- Properly you are affected, that we start not call KWallet directly and use QtKeychain to interact with the password storage instead. This is not done for every resource. In a clean KDE Plasma environment KWallet is the preferred password storage. I expect you are running a Gnome or any other non Plasma desktop, and than libsecret and Gnome Keyring are preferred over KWallet. See the decision path: https://github.com/frankosterfeld/qtkeychain/blob/master/keychain_unix.cpp#L100 I would expect, that it tries to read/write to either libsecret or Gnome Keyring. You can other application that uses QtKeychain like Nextcloud Desktop client to understand where passwords are read/write. But you also see the error about LibSecretKeyring::findPassword that are relevant in your case. You may also fake a KDE environment by setting KDE_SESSION_VERSION=5 and XDG_CURRENT_DESKTOP=kde when starting Akonadi. Maybe we also mixed the read and write one via QtKeychain the other directly to KWallet. -- You are receiving this mail because: You are watching all bug changes.