https://bugs.kde.org/show_bug.cgi?id=511425
--- Comment #11 from michaelk83 <[email protected]> --- (In reply to Frank Busse from comment #10) > I have accidentally found out that, after dist-upgrade to trixie, both > kWallet and /usr/bin/gnome-keyring-daemon are active. (I previously was and > still am on KDE/Plasma.) Is there any use in having both? Can I find out why > gnome-keyring-daemon was added? gnome-keyring-daemon tends to be installed by default on some systems. It may have already been there before the update, or may have been pulled in as a "recommended" dependency. It used to be the main provider of Secret Service API, but nowadays KWallet can also provide that API (as of 5.97 or so). You can check if you have any secrets stored in gnome keyring (e.g. using Seahorse), and if not, try uninstalling the daemon. It can sometimes conflict with other Secret Service providers such as KWallet, so it's best to remove it if you don't need it. Btw, re your original issue, try also checking if there are any permission problems, such as SElinux blocking access to KWallet. And check your block list in KWalletManager. (Though Debian should be using AppArmor by default, IIRC.) -- You are receiving this mail because: You are watching all bug changes.
