https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #43 from Frank Kruger <fkrue...@mailbox.org> --- (In reply to michaelk83 from comment #36) > Reopening because the fix should ideally be automated by KWallet when > setting up a GPG wallet, or at least properly documented. > To summarize: > > This affects GPG wallets with Secret Service enabled. By default, GPG tries > to retrieve the key passphrase from Secret Service. If Secret Service is > provided by KWallet, this creates a dependency cycle, which prevents the > wallet from unlocking. There are three ways to break the cycle: > > - Option A (recommended): To prevent GPG from trying to retrieve the > passphrase from Secret Service, add the `no-allow-external-cache` option to > `~/.gnupg/gpg-agent.conf`. You can either edit the file manually, or run: > `echo no-allow-external-cache:0:1 | gpgconf --change-options gpg-agent`. GPG > will prompt the user directly when the key passphrase is needed for the > first time. > - Option B: Disable the Secret Service API support in KWallet settings. You > may use a different Secret Service provider if desired. > - Option C: Do not use a GPG wallet (downgrade to a traditional blowfish > wallet). Recommendation A works fine for me - thanks for the "solution". However, I am really puzzled by the fact that the regression definitely introduced by the upgrade to KDE's KWallet 5.97.0 for those of us who are using GPG wallet together with Secret Service API support in KWallet is simply called "resolved upstream". So, who is going to inform all the users hit by this bug and using different distros to change their ~/.gnupg/gpg-agent.conf accordingly? Sorry, but the bug is not solved at all! -- You are receiving this mail because: You are watching all bug changes.
