Still open in this ticket (see https://dev.gnupg.org/T6568#208755 ):

• Collapsible items in tree views can't be expanded/collapsed, at least not with space or arrow left/right
• Tab navigation in the Smartcard Dialog is broken

New tickets split from this:

• https://dev.gnupg.org/T7952 Make table column headings for other tables accessible
• https://dev.gnupg.org/T7953 Make table header column width accessible
• https://dev.gnupg.org/T7954 Highlight focused cell in tables

In gpg4win-5.0.0-beta413 @ win11 there's a failing patch for kcrash:

I can't reproduce this on gpg4win-5.0.0-beta413 @ win11.

This seems to apply only for non vsd compliant algos. Importing and certifying a

• rsa/brainpool cert results in security level 4
• cv25519 cert results in security level 2

I rechecked: the revoked userid has to match the email address of the sender. Still there's another non revoked userid with the same email address:

I'd prefer the language switch for testing, but I mostly had tests for translation issues in mind, e.g. wrong translation language, tooltip size in some language - which probably should be covered by setting the language via the envvar. I'll do some tests to see, if this would work.

• Column sort order and visibility can be configured only via view and nowhere else. That's how it should be, right?

What do you mean?

Ah, I see. I heard the continuous beeps with another pitch once (probably in the installer then) and thought this was possible. Shall I set this to won't fix then?

Regarding the tests: Being able to set the language for Kleopatra via some environment variable would be fine, too.

Separate ticket for the "initial language selection": https://dev.gnupg.org/T7949

Yes, sorry, a typo, I corrected it.

Looks good to me on gpg4win-5.0.0-beta413 @ win11.

I also tried to check all tables i can find and it mostly looks good:

• Certificates Lists:
  • Main
  • Import ("Show imported")
  • Cert Selection (e.g. Sign as)
  • Keyserver Lookup
  • Smartcard
  • Groups (both available and in group)
• Certificate Details
  • User IDs
  • Sub-keys
  • Certifications

Looks good to me on gpg4win-5.0.0-beta413 @ win11

Actually pinentry has the same behaviour, so this might be a general problem, if one form input field is changed.
It also applies to clicking on other form elements.

As this looks good to me on gpg4win-5.0.0-beta413 @ win11, I move this to done on the gpd5x board.

Looks good to me on gpg4win-5.0.0-beta413 @ win11:

Looks good to me on gpg4win-5.0.0-beta413 @ win11

Looks good to me on gpg4win-5.0.0-beta413 @ win11

Looks good to me on gpg4win-5.0.0-beta413 @ win11.

Looks good to me on gpg4win-5.0.0-beta413 @ win11:

Looks good to me on gpg4win-5.0.0-beta413 @ win11

Looks good to me on gpg4win-5.0.0-beta413 @ win11

Looks good to me on vsd-3.3.3-beta90.32 @ win10.

Looks good to me on gpg4win-5.0.0-beta413 @ win11: The option is removed in the S/MIME tab.

Note: Backup/Restore secret kyber keys looks good to me on gpg4win-5.0.0-beta413 @ win11 now.

Looks good to me on gpg4win-5.0.0-beta413 @ win11.
The error message in debugview is gone.

Looks good to me on gpg4win-5.0.0-beta413 @ win11:

Tested on gpg4win-5.0.0-beta413 @ win11

Looks good to me on gpg4win-5.0.0-beta413 @ win11.

Looks good to me on gpg4win-5.0.0-beta413 @ win11:

Looks good to me on gpg4win-5.0.0-beta413 @ win11.

Looks good to me on gpg4win-5.0.0-beta413 @ win11:

• Email/Name
  
• Name
  
• Email
  

Forgot to note: Setting S/MIME debug level in kleopatra via GnuPG System will write the right key to gpg.conf (if I understood it right, this was also a problem)

On gpg4win-5.0.0-beta413 @ win11

• The diagnostics button is displayed
• The message contains a hint to adsk
  

Looks good to me on gpg4win-5.0.0-beta413 @ win11

Still needs to be tested on VSD 3.4.

Looks good to me on gpg4win-5.0.0-beta413 @ win11

Looks good to me on gpg4win-5.0.0-beta413 @ win11

I think last time I didn't test the actual problem.

Looks good to me on gpg4win-5.0.0-beta413 @ win11

Thanks for clarification. I added this to the doc enhancement ticket https://dev.gnupg.org/T7911 and set this ticket to invalid.

So, for the current vsd docs (3.3): https://gnupg.com/vsd/kleopatra-settings.html
This would be more correct, if i understood it right?

HKEY_LOCAL_MACHINE\Software\Wow6432node\GNU\Kleopatra
HKEY_CURRENT_USER\Software\Wow6432node\GNU\Kleopatra

My point about action restrictions was to add one sentence in the docs section to clarify, what exactly is restricted then.

Allright, then the dash notation for those two groups are intended and the documentation needs to be adjusted

Note: The tab name is displayed after restart, if

• The tab was renamed manually
• The filter was changed (leading to a rename)

So this means, the order in the description should be implemented, right?

The [KDE Action Restrictions][$i] in XDG_SYSTEM_DIRS/kleopatrarc prevents any changes within the whole group afterwards.
I guess, this is intended by defining an "immutable group", but i doubt that we want to prevent admins to change those settings?

So, regarding the minor version change: the change of order seems not critical (as there was no settings file before), but the introduction of the settings file might be.

I verified, that both in vsd 3.3.2 and vsd 3.3.3 beta90.29 the current implementation is

The configuration readout order still needs to be specified/fixed.

Looks good to me on vsd-3.3.3-beta90.29 @ win11

In gpg4win-4.4.1 it works too.

Note: In the current vsd beta (29) it works (pinentry for the next key is opened):

Note: It works with gpg-card url --clear.

Right, gpg CLI output depends on it, too.

ZeitControl OpenPGP v3.4 card

Windows Language Settings:

• ISO: EnglishInternational
• Windows Language: English (United Kingdom) - note: i installed English (United States), but can't select it
• Country or Region: German
• Regional Format: German

The screenshots were made with

• ISO: EnglishInternational
• Windows Language: English (United Kingdom) - note: i installed English (United States), but can't select it
• Country or Region: German
• Regional Format: German

• I might want to know the fingerprints of those unknown recipients to search for them (in the audit log I can't see, which of those fingerprints are unknown immediately)