Better but still not perfect. It still can happen that it is opened in the background if you put the options dialog in the background before the window pops up. But I think that is acceptable for such a rarely used feature.

@dcialdella I've checked the Ubuntu Patches, they don't include the patch that caused the problem for GpgOL in this issue. Please report your problem either to Ubuntu or open a new issue, ideally with some instructions how to reproduce your problem.

Ok, so I guess that you can close this ticket.

At the very least the dialog should not be easily closable if the CSR was not exported to a file. This makes it too easy to accidentally loose the CSR.

I've just checked the current build to the previous one (even when I get rid of the build directories, I keep a copy of the config.log since you never know when it might come in handy).

FYI: this most recent update broke builds on OS X 10.9 for Qt, but everything else is fine.

Thanks.

I assume -z0 could be used as a workaround but without compression then.
Fix goes into 2.2.7 to be release tomorrow (tm)

Confirmed. it is also not Windows specific.

A strangeness I see is when I am searching for "zitis" on x500.bund.de I get the same key over and over again (until the list is truncated). I'm not sure if the response from the server is wrong or if we have a bug there. If I search for "Telekom" for example I get 10 different certificates, so it works there.

I felt confident enough to push a fix for the console window. The code was obvious and the fix, too.

Yes! Works nicely. I tested with unreachable and invalid servers, and with multiple queries against x500.bund.de and ca.intevation.de all is fine!

No longer happens when the good old ldapwrapper is used.

By standard I mean "behaves" somewhat like coreutils. Filename encoding,.. meh I see that this could be a problem.

The highest priority I see here is for T3953 which I think is a bug that might result in a good signature shown for an expired, but otherwise valid and trusted certificate.

Glad that we could locate the issue.

Thanks for the detailed information. From the log I can see the same behavior as in T3769 with the TITUS plugin. No Read event is passed to us.
I've added MailStore to the list of incompatible addons for now https://wiki.gnupg.org/GpgOL/IncompatibleAddons

Thanks for the great direction on how to debug the issue any further.

gpg 2.2.4-1ubunt amd64 GNU Privacy Guard -- minimalist p

The hang appears random. It sometimes works 4 out of 5 times.

With latest gpg-error and latest gnupg It still hangs for me after printing the certificate.

It's possible that was one of the upstream patches they decided to include.

It is in 1.30 which I released a few minutes ago. Only minor other changes.

@dcialdella Do you have a "non standard" GnuPG / GPGME installed? What are the versions?

I have the same issue with Xubuntu 18.04 lts, and GNUPG.
./start_linux_64bit
[Error] Source: GPGME String: "Invalid crypto engine"
[Error] Source: GPGME String: "Invalid crypto engine"
[Error] Source: GPGME String: "Invalid crypto engine"

Clearly getting SWIG and Windows to play together nicely is a bit of a big ask, but it may be possible to leverage GPGME's compiled libraries with something like CFFI's ABI calling method (yeah, I know, ABI is never ideal, but it's better than what Windows has now).

The last change to the python installer was, IIRC, one I discussed with Justus off-list around the middle of, um, last year? Maybe the year before?

@werner I'm afraid you are too late. Looks like this was merged into master about three years ago. I probably should not have commented on a commit that was merged so long ago :)

You need to give the --with-foo options for each package.

No, we won't cripple GnuPG for testing purposes. You intended to test something else than the provided GnuPG.

Please don't apply this, SYSROOT is not a well defined feature and it needs to be implemented everywhere in the same way.

SYSROOT support is not yet fully implemented. You need to give the --with-foo options for each package.
I will retitle this bug to indicates tha tit is a feature request.

Now there it gets complicated. According to the card software author in 3.3 and even 2.2 there is a fix. BUT there was a small amount of cards already created in 3.3 without the fix. Nobody ever told my how to diferentiate them.
There is no Version 3.3.1 you can by - it is only 3.3. So you can buy one and hope you have a good one.
At least this is my understanding.

@aheinecke maybe recheck with GNUPG 2.2.6 or 2.2.7.

I'm using the kdepim-docker for tests, that is based on KDE Neon, that is based on Ubuntu xenial (16.04), so the version for GnuPG2 is 2.1.11-6ubuntu2. Good to know, that the GnuPG version also matters for this stuff.