It's intentional that with Gpg4win migration from %LOCALAPPDATA% does not work because %LOCALAPPDATA% is used by VSD (and GPD) but not by any old Gpg4win.

Staring at some Process Monitor logs I noticed that dirmngr wastes 3-4 seconds trying to connect to localhost:9050 and localhost:9150 looking for tor. After adding no-use-tor to dirmngr.conf dirmngr starts reasonably fast.

In T7379#195089, @ikloecker wrote:

Kleopatra does now read the certificates from the card and import them itself instead of relying on gpgsm --learn-card.

I have built the run-* test programs of gpgme for Windows. run-keylist --cms --secret takes about 23 seconds. 3.7 seconds are gpgme initialization/setup (gpgconf --list-dirs, gpgconf --list-components, gpg --version, gpgsm --version, gpgconf --version). Most time (2 x 6-8 s) is lost starting gpg-agent and dirmngr. (keyboxd is not enabled here.)

Closing. I don't think we need this "Klammer-Ticket" anymore and it's cluttering my task list.

I'm not working on this anymore. Kleopatra should be prepared for using VSD, GPD, and Gpg4win in parallel (provided they use different homedirs). What's left is the actual parallel installation which might be solved in part by using NSIS for Gpg4win and MSI for VSD/GPD. I'm not sure how the parallel installation of different versions of gnupg is solved, but I guess Werner has that covered.

For KF5-based builds this is resolved because the improved heuristic for detecting light high-contrast themes (like "Desert") is used for VSD 3.3 and Gpg4win 4.4.

For simplicity (and because I think entering tab characters isn't really essential for the notepad) I decided to go with the first solution.

Ready for testing.

A second patch fixes the problem with the button in the smart card view.

I have added a patch to disable recoloring of the status icons in Gpg4win. This ensures that the status icons in the selected rows don't get all-white.

Upstream bug report for invisible status icons: https://bugs.kde.org/show_bug.cgi?id=506434 (Icon coloring is inherently incompatible with colored Breeze status icons)

gpg --version?
gpg -K?

In T7639#202620, @timegrid wrote:

If this should also work in gpg4win-5.0.0-beta336 @ win10 (beta compliance mode), it does not:

In T7610#202487, @timegrid wrote:

• compliance note in sign/encrypt next to sign/encrypt button (both for file and clipboard) unreadable in black/nr1/nr2 and also in dark mode:

In T7610#202487, @timegrid wrote:

• compliance note in sign/encrypt next to sign/encrypt button (both for file and clipboard) unreadable in black/nr1/nr2 and also in dark mode:

In T7594#202471, @timegrid wrote:

Shouldn't the enabled close button in win10 / disabled text / nr2 have green color? (it's the "search certs on server" dialog).

In T7232#202509, @timegrid wrote:

With above configuration it seems to work on gpg4win-5.0.0-beta336 @ win10.
Any way to verify in kleopatra, that the setting was applied?

In T7394#202514, @timegrid wrote:

• Kyber algorithms display only their ecc part

I guess that the missing formatting of fingerprint or key ID isn't restricted to v5 keys. -> separate ticket

In T7345#202503, @timegrid wrote:

• Some/Most "Not VS-NfD compliant" notes do not have the (beta) suffix (probably fine?)

This also happens on Linux. And even with the Fusion style.

Thanks for the Windows 11 screen shots.

Regarding the "unsure" findings:

• invalid state in cert list tooltip (red on black)

This will never happen on stock Linux.

This is more a technical ticket. There's not really something to test. Setting to Resolved/Done as discussed with ebo.

Most issues with icons in high contrast modes (of Windows 10) should have been fixed. Needs to be verified especially with the high contrast modes of Windows 11.

Setting to Testing.

Moving to QA. All changes should be in the latest beta.

Many issues have been fixed. Setting to Testing to check what I have missed.

The problem with the invalid certificates seems to be unrelated. Isn't there already a ticket for Okular for certificates which expire after 2038?

And in the first case, about 6 seconds are lost starting keyboxd:

2025-06-23 13:16:55 gpgsm[3252] DBG: chan_0x000000000000022c <- VERIFY
2025-06-23 13:16:57 gpgsm[3252] Kein aktiver keyboxd - `C:\\Program Files\\GnuPG\\bin\\keyboxd.exe' wird gestartet
2025-06-23 13:16:59 gpgsm[3252] Warte bis der Keyboxd bereit ist ... (8s)
2025-06-23 13:17:01 gpgsm[3252] DBG: chan_0x0000000000000260 <- # Home: C:\Users\g10\AppData\Roaming\gnupg
2025-06-23 13:17:01 gpgsm[3252] DBG: chan_0x0000000000000260 <- # Config: [none]
2025-06-23 13:17:01 gpgsm[3252] DBG: chan_0x0000000000000260 <- OK Keyboxd 2.5.6 at your service, process 4748

The keylisting hangs ticket for Kleopatra: T6623