What can be done is to use gpgconf --list-dirs bindir as a fallback for pinentry.

Sorry, hhis is a bug tracker and not a help line. Please ask on a mailing list - see gpg4win.org or gnupg.org

Backported to 2.2. Note that an updated libgcrypt is also required (for 2.2 and master)

For the Debian problem it might be better to use "gpgconf --launch" and we add an option here to wait for the daemon to be started. That can be implemented in gpg-connect-agent which then should get the same option.

Frankly, I do not like this change - in particulalr not for the stable branch. Having a timeout on connections is actually a Good Thing and better than to wait indefinitely. There is a high risk on regressions and that is not acceptable for the stable branch. The branch already had a couple of regressions in 2.2.2x and we need to fix them and not introduce others.

Only enabled for UNIX #ifdef/#else/#endif

I had overlooked this fix rG044379772fc5: common: Fix the previous commit., after the commit of D510.

All right, using the current master a Windows user with a Unicode name (e.g. Ⓐlfred E. Neumann) is now able to use gpg properly. Quite a lot of changes were required and backported to 2.2 will also be some work. More testing is of course required. Note that libassuan needs to be taken from Git until we have done a new release.

I created this patch D509: Yubikey supports two (or more) apps, serial number problem.

My sks keyserver is in Linux Ubuntu 18.04 LTS. As a client I'm using windows 10 and gpg4win is 3.1.13.

Hmm, interesting. I'm using the Back button all of the time to get back to the certificate list from the smartcard manager. Might be a Windows-only bug.