https://bugs.kde.org/show_bug.cgi?id=458085
--- Comment #27 from michaelk83 <mk.mat...@gmail.com> --- (In reply to michaelk83 from comment #26) > So short-circuiting `OpenSession` while waiting on GPG should fix this, IMO. > It should return something like `InvalidMethodCall`, or simply `NotSupported`. On further thought, this can still cause problems if two or more apps try to unlock the wallet at the same time. The 1st one would short-circuit `OpenSession` while unlocking the wallet, and then the 2nd may get the short-circuit response instead of the normal response. A more robust approach is to check if the key/passphrase are already loaded into gpg-agent, and if not, display a prompt and pre-load the passphrase before trying to unlock. See https://linux.die.net/man/1/gpg-preset-passphrase . -- You are receiving this mail because: You are watching all bug changes.
