Not sure, which shell had problems, but it works on both zsh and bash with my last build gpg4win-5.0.1-beta24-x86_64.AppImage. So i guess, i can close this.

A different order is pretty much impossible to implement in upstream kconfig without big changes/refactoring.

Also done: The tab order for the close button is now correct.

Note: On gpg4win-5.0.1, there's also no audit log for notepad pgp sign/encrypt. So this is expected?

Looks good to me on gpg4win-5.0.2-beta2 @ win11.

Just to be sure: The "Show Email" button is still never shown on the notepad, right?

In general looks good to me on gpg4win-5.0.2-beta2 @ win11:

Looks good to me on gpg4win-5.0.2-beta2 @ win11:

• first manual gpg -K and gpgsm -K displays the correct output now
• the loop ran without a hang for 50 times

Looks good to me on gpg4win-5.0.2-beta2 @ win11:

Looks good to me on parallel install of

1. gpg4win-5.0.2-beta2 @ win11
2. vsd-4.0.0-beta1203 @ win11

Looks good to me on gpg4win-5.0.2-beta2 @ win11:

The registry keys "GnuPG Desktop" and "GnuPG VS-Desktop" now work correctly, i.e. existing registry keys should be considered in the next VSD 4 build.

There shouldn't be any RegCreateKey anymore for HKLM\SOFTWARE\<product name>\... or HKCU\SOFTWARE\<product name>\.... And, of course, no registry keys should be created.

In any case, the order still needs to be adjusted.
The current implementation is still (neither the order in the description nor on the settings page):

Seems to work in principle with gpg4win-5.0.2-beta2 and vsd-4.0.0-beta1203.
I'll wait for a new vsd beta release (with some fixes) for further testing.

with Gpg4win-5.0.2-beta2:

The missing signature indication can also be seen now in the customer mails sent via kmail (ted:INBOX, e.g. 18.02. 12:52). This was fine before.

Looks good to me on gpg4win-5.0.2-beta2 @ win11.
Tested import on 5 normal starts and 5 gdb starts.

The basic fix for the msg box looks good to me on gpg4win-5.0.2 (beta) @ win11.
There's only no signature shown anymore, not even for the formerly working case 1.
Note: I also tested those mails sent to an exchange server with the same result as via IMAP.

Looks like the "read config from registry" patch that was upstreamed wasn't tested properly.

Works with Gpg4win-5.0.2-beta2

Fixed.

Here's a full log of a gdb run, which segfaults on start:

full debugview log:

Please always attach the full Debugview log. Sometimes (like here) I really want to know everything that was logged since the start.

Fixed. This regression was caused by changes made for T8056: Support config options RSAKeySizes and PGPKeyType for Kf6.

In T8029#212310, @werner wrote:

My actual plan is to rework the imp[ort/export of secret keys to gpg-agent. Right now gpg-agent has knowledge of OpenPGP for import/export. This is not good and the required conversion should be moved to a helper tools for easier testing and to have this out of the gpg-agent process. For Kyber we right now don't use any conversion mut store the secret keys in gpg-agent's native format. Thus the passphrase is not necessary. We need to figure out why we have this problem here.

@werner said the reading order should be like on the page https://gnupg.com/vsd/kleopatra-settings.html:

Tested with Gpg4win 5.0.2 (Beta):
Registry settings SOFTWARE\Gpg4win\Kleopatra\<config group>\<config entry>
works (I used [CertificateCreationWizard] EMAIL_placeholder for testing)

This is not "Unbreak now" because we have not released the software yet. Unbreak now should be used for bugs in deployed software but not during development.

Note: This was fine on gpg4win-5.0.1

Regarding some broken "reg create" on some filepath: split into T8141: Kleopatra: Many wrong registry keys created in HKCU\Software\Gpg4Win

I rechecked the keyboxd locking of pubring.db. On crash via gdb the file was unlocked before, so this doesn't seem to be the problem:

Ok in Gpg4win 5.0.2. (Beta), in German:

Libkleo does not specify the curve in the parameter file becuase keyCurvve:isEmpty is asserted:

Works on the command line and adding a subkey later does also work.

config file: Sorry, I got confused, it has to be %APPDATA%\GnuPG VS-Desktop\kleopatrarc in this case (VS-Desktop-4.0.90.1203-Beta), of course. And this one works.
Registry entry SOFTWARE\GnuPG VS-Desktop\Kleopatra\CMS\SaveCSRAsPEM does not work, though. But this is a separate issue, seems all Registry entries do not work in that build.

• config file: According to T7717: Location of qt-application config files %APPDATA%/Gpg4win/kleopatrarc should work.
• registry: According to T5707: Kleopatra: Use windows registry additionally to config files this should be SOFTWARE\Gpg4win\Kleopatra\CMS\SaveCSRAsPEM now

Works with VS-Desktop-4.0.90.1203-Beta when putting this in C:\Program Files\GnuPG VS-Desktop\share\kleopatrarc
CSR is then saved as .pem file with ascii-armored content.

The new German tool tip is shown in Gpg4win 5.0.2 (Beta)

Done and backported for VSD 3.4.

Thanks for the info!

This was fixed in Okular with https://gitlab.freedesktop.org/poppler/poppler/-/merge_requests/2115 . The MR was merged 2026-02-05.

Does not work in the latest Gpg4win builds (5.0.0. to 5.0.2).
I have no idea which commit would be needed, I see no commit with this bug-ID.