https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #46 from michaelk83 <mk.mat...@gmail.com> --- (In reply to Frank Kruger from comment #45) > Appreciated, but your solution seems to be restricted to a fix when setting > up a GPG wallet. What about current users? The proposed fix should work the same whether the wallet is new or existed previously. It does not affect the wallet data in any way. The patch I proposed in comment 40 (once translated from pseudo- to actual code - still TODO) would take effect when unlocking the GPG wallet, so it should work with existing wallets as well. It's the same fix, just automated, and only applied while unlocking the wallet (instead of a permanent configuration change). Btw, Secret Service integration did not exist at all in KWallet prior to 5.97.0. So there are three types of KWallet users: - Those using a blowfish wallet. They are not affected by this bug. - Those who were using a GPG wallet with a 3rd-party Secret Service provider. In their case, GPG was likely taking the key passphrase from the 3rd party Secret Service provider. These need the patch from Bug 458069, and to disable the new integration in KWallet, so that the 3rd party provider can function as before. - Those who were using a GPG wallet *without* a Secret Service provider (likely the majority). In their case, GPG was *not* taking the key passphrase from Secret Service, since Secret Service was not available. Adjusting `gpg-agent.conf` as suggested above (comment 36 Option A) restores the previous GPG behavior for those users. -- You are receiving this mail because: You are watching all bug changes.
