https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #80 from michaelk83 <mk.mat...@gmail.com> --- (In reply to jackdinn from comment #78) > I noticed it has > Exe=/usr/bin/gnome-keyring-daemon > CommandLine=/usr/bin/gnome-keyring-daemon --foreground > But iv never had gnome-keyring installed, ever. Yes, as I said, some users have Gnome Keyring installed without knowing. It's probably bundled with the distribution, or may be a dependency of some other software. So, what you had happening in this step is, since your KSecretD is disabled, Gnome Keyring was able to take over the Secret Service bus, to provide that service. Since it's independent from KWallet, it wasn't hanging. But since your secrets are still stored in KSecretD, they weren't accessible. Now that you've also disabled Gnome Keyring, you have no Secret Service running at all, as you saw with the latest busctl call. But since 6.14, KWalletD is only a proxy to Secret Service, so with no Secret Service running, it has nowhere to save the secrets to. And of course, your previous secrets in KSecretD are not accessible, since you still have it disabled. I couldn't find how we can confirm that you're using a GPG wallet, but let's try the following configuration: - In your kwalletrc, either remove the `[KSecretD] Enabled=false` part, or set it to `Enabled=true`. - In the KWalletManager settings, under "Secret Service", uncheck the "Use KWallet for the Secret Service interface". (Or alternatively, in kwalletrc, under `[org.freedesktop.secrets]`, set `apiEnabled` to false. It's the same setting.) What this should do, is let your KSecretD run (`[KSecretD] Enabled=true`), but tell it not to use the org.freedesktop.secrets address (`[org.freedesktop.secrets] apiEnabled=false`). It should still run Secret Service on its own internal address, org.kde.secretservicecompat. With this setup, your old secrets should be accessible from KSecretD, and you should be able to see them in KWalletManager. But since KSecretD won't be using the main org.freedesktop.secrets address, you shouldn't be affected by the bug discussed in this ticket. If this still doesn't work, you most likely have a different problem. -- You are receiving this mail because: You are watching all bug changes.
