I also don't think, that a backport to 2.2 is neccessary.
As gnupg26 was tested in gpg4win5 beta413 as well, I also move this to done on the gnup26 workboard and mark this issue as resolved.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Dec 4 2025
Dec 2 2025
This also happens in vsd 3.3.2 and gpg4win-5.0.0-beta413 @ win11
Dec 1 2025
I meant more like if it's worth a ticket at all, as it's an edge case and not necessarily a problem. Ebo and me already agreed, that we can live with it - but if you think it's worth it, I'll create another ticket.
Nov 28 2025
They can be expanded/collapsed with +/-
Tested on gpg4win-5.0.0-beta413 @ win11.
(removed unfinished text)
This seems not to work in Kleopatra/gpg in gpg4win-5.0.0-beta413 @ win11.
When an uncertified cert is uploaded, the main button of the warning message also says Export Certificate. Should this be another ticket?
Nov 27 2025
Tested on gpg4win-5.0.0-beta413 @ win11 with the following entries in dirmngr.conf:
Nov 26 2025
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
- https://dev.gnupg.org/T7955 Wrong NVDA level in tree views
In gpg4win-5.0.0-beta413 @ win11 there's a failing patch for kcrash:
Nov 25 2025
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:
Nov 24 2025
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.
Nov 21 2025
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 gpg4win-5.0.0-beta413 @ win11
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.
Forgot to note: Setting S/MIME debug level in kleopatra via GnuPG System will write the right key to gpgsm.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
Nov 20 2025
Nov 6 2025
Nov 5 2025
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






