Wed, Sep 8
I verified that manually putting the DB in WAL mode also resolved this issue, since writers don't block readers in WAL mode.
Aug 13 2021
May 11 2021
Thanks for using GPA. Unfortunately, I have to tell you that GPA development has been stopped and I can't say whether we will fix that bug any time soon. Please consider to switch to Kleopatra which is the standard key manager included in gpg4win.
Apr 15 2021
Done for gpa.
Done for pinentry.
Jan 23 2021
Jan 5 2021
Dec 10 2020
Dec 9 2020
I have reproduced the bug
A backtrace with gdb from migw-w64 results in
I did a fresh install of Gpg4win 3.1.14 and imported my standard pubkey, by using
gpg --locate-key email@example.com
on the command line.
Sorry, I can' reproduce thus. What kind of key is causing the crash?
Oct 19 2020
Which version of Gpg4win did you install, from where, and which OS version are you using? Why did you install gpg4win at a non-default location?
Aug 14 2020
Aug 13 2020
Taking: Still does not work although now --quick-set-expire is used by gpgme.
Feb 17 2020
Yeah, this can be done.
Sep 9 2019
Jul 31 2019
Well, gpa needs to use gpgme's interface for receiving and sending keys. The use of the helper programs an old hack.
Jul 24 2019
Jul 18 2019
Jul 1 2019
Werner: I'm assigning this to you. Because the underlying reason is a missing status from gpg. I think we should add that for 2.3 as any new status line tends to break things.
Jun 20 2019
when can we fix it?
Jun 3 2019
Apr 26 2019
Closing this as invalid until the info requested in the last comment is provided.
@werner This issue also applies to GPA. Looking at the edit key interface I can't see how we can handle this. Am I overlooking something or do we just loose the error information / is it not emited by gnupg?
Apr 10 2019
@sapienza Can you try it with Kleopatra please and if it fails there, too please post the "Diagnostics" from Kleopatra. (See "Blocco note" in Kleopatra for the same functionality)
Apr 9 2019
Did you encrypt to a key of yours? You can only decrypt if you have the matching secret key for the public key you used for encryption. The error message: "No secret key" should be obvious.
I've tested it with Gpg4win-3.1.7, too and it works for me so something must be special.
this error comes to me when I try to decrypt a message and I get this message
Apr 7 2019
And please do not use Gpg4win 3.16 but the bug fixed release 3.1.7.
Mar 28 2019
Mar 27 2019
Mar 21 2019
Mar 4 2019
Btw. I'll try to get a new release out this week. In the meantime either downgrade to 3.1.5 or use Kleopatra.
Jep that was part of Gpg4win as Gpg4win needed features / fixes from that version.
Mar 3 2019
GPGME 1.12.1-beta43 is nowhere near the current master. Current is around 1.12.1-beta130 (or above) and beta 43 would've been months ago, probably early November or late October.
Feb 28 2019
Okay, this is the latest released version. I now wonder what you mean by version 1.12.1-beta43. This sounds like our current development version of the GPGME library, right? How did you install this software? Is it from Gpg4win or did you build it from source?