Nope: There are many different error codes returned, Kleopatra may want to map them to a common one.

In the meantime pinentry has been updated also for VSD 3.4.

Backported for VSD 3.4

Backported for VSD 3.4

the issue is the same in Gpg4win-5.0.0-beta357:

Looks good to me on GnuPG-VS-Desktop-3.3.90.8-Beta-Standard.msi (3.3.3 betaversion) @ win10
(tested with 10 restarts)

We decided to remove one more item:

Copy to card

Because it is only doe once, usually.

We decided to remove one more item:

• Copy to card

Because it is only doe once, usually.

https://invent.kde.org/pim/kleopatra/-/merge_requests/410 has been merged for the accelerators

I've also fixed the problem that a file named mail.P7M was not treated as encrypted email message. I think this could be tested/verified.

After studying the logs created by NVDA and its source code I strongly suspect that the problem needs to be fixed in NVDA. NVDA tries to avoid repeating the text of common ancestors of the old and the new focus object, but it fails to detect the Create OpenPGP Certificate dialog as common ancestor of the text edit field in this dialog and the Error (child) window.

We need a better error code from gpg to change this

We decided that gpg should emit a status message for success, too.
gpgme should then look for that status message instead of only absence of error.

Fixed by adding a patch for Qt 6 (and a patch for Qt 5 in gpg4win-4-branch for VSD 3.4).

A quick check with passing ASSUAN_PIPE_CONNECT_DETACHED does not changed anything.

I wonder whether rA3bccb33ccd9028ff505d9979fd6c8a37393b892d which changes Assuan's waitpid function for Windows is well aligned with the my_waitpid in gpgme's assuan-support.c (which does nothing). gpgme creates a detached process in most cases but for gpgsm assuan_pipe_connect is used without the ASSUAN_PIPE_CONNECT_DETACHED flag.

Another data point is that the faulty versions use libassuan 3 with a slightly changed API. May one of the follwing chnages cause the problem?

Although in VSD 3.2.2 we get no warning when configuring S/MIME debugging wrong we then get a nice message "Configuration error" when trying to encrypt with S/MIME, instead of gpgsm hanging without any message at all:

Logging all

The issue also occurs in VSD-3.3.2 and 4win-4.4.1 but not in VSD 3.1.26

works in vsd3.3.3, tested with VS-Desktop-3.3.90.8-Beta

OK on Linux now with new enough versions (Fedora 42).

Tested with Fedora 42 (which includes gpgme 1.24.3): this works now, you can drag a public or secret key from Kleopatra to a file manager to export the public key.

Fixed and backported for VSD 3.4

Solved by focusing the result message after the notepad operation is complete. I think that's an acceptable compromise for ensuring that users of assistive tools are informed about the result even if the focus is moved to a different UI element (which, in general, should be avoided because users can get lost).

Finally came around to check this.
On Fedora with Kleopatra 25.04.03, gpg 2.4.5 and pinentry 1.3.1 the pinentry window ist above the Kleoaptra windows.

The gold rule of tab order is that tab order follows the usual reading direction, i.e. line by line from left to right. If you press Enter after entering the password in the first input field then the focus should jump to the second input field.