I am sorry, that I can't give it a high priority. See the discussion on the mailing list. I'll try my best, though.

Or maybe not. I just did 0.11.0 (T7449) and will do more releases if there is demand for it or we have collected enough patches.

Gpg4win doesn't include libexpat anymore (since it doesn't include gpa and pinentry-gtk anymore).

We stopped maintaining GPA in favor of Kleopatra.

Finally had some time to look into this a bit more.

A simple first step would be to install pinentry-gtk only in the GPA variant.

I think this is because we install pinentry-gtk, too. So we have that GTK dependency.

I verified that manually putting the DB in WAL mode also resolved this issue, since writers don't block readers in WAL mode.

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.

Done for gpa.
Please test.

Done for pinentry.

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 bernhard@intevation.de

on the command line.

Sorry, I can' reproduce thus. What kind of key is causing the crash?

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?

Fixed.

Taking: Still does not work although now --quick-set-expire is used by gpgme.

Yeah, this can be done.

Well, gpa needs to use gpgme's interface for receiving and sending keys. The use of the helper programs an old hack.

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.

Hello,
when can we fix it?

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?

@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)

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

And please do not use Gpg4win 3.16 but the bug fixed release 3.1.7.

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.

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.

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?

0.10.0

Which version of gpa is that?

Yes please use the command line ( gpg --gen-key ) or Kleopatra. This issue is fixed in the latest version of the GPGME library.

Can i generate a key using shell?

Version gpg (GnuPG) 2.2.11

Version of gpa and best also of gpgme? The latest gpa releases show that in the About dialog.
The installed version of gpg is also of inetrest. In a shell enter "gpg --version".

Regession due to my commit 10 days after the last release. Thus no need to do a release.

Should we close this or do you want to investigate why the segfault happened after the error?

Thanks.

I ran it with GPGME_DEBUG and it errors out at
GPGME 2018-12-07 10:34:32 <0x19c43> gpgme_op_genkey_start:293: error: Invalid argument <GPGME>

Sorry, I am still not able to replicate it:

Just by going through the standard "new key wizard".

Can you give me a reproducer on Linux. I am not able to reproduce it. What versions of gnupg and gpgme are you using (see gpa's about)

Gets reported multiple times and should be fixed for the next Gpg4win release as it is a bad first impression. (Although it can convert users to Kleopatra ;-) )

Thanks. There is an easier solution for this, though: I now trim trailing LFs.

Thanks. I added these files.

In addition to what I said above - the patch comes with two small side-effects - The size of the content in the tab is constant over the tabs, so that even a page with not very many settings will show a scrollbar, even if it only makes it possible to scroll in empty space from below.

I have made a patch for this, that add scrollbars to scroll up and down in the settings. This adds the need to set a default window size, which I have set to 700 x 500, which seems fine. Tested on a relatively low-resolution machine (1366 x 768), where it seems to work fine for me.