You're right, it also errors on gpg directly:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jul 1 2025
I can't reproduce. Please check whether this works if you use gpg directly; it's a bit unlikely that this is kleopatra-specific, since kleopatra doesn't really care whether the key is on a smartcard or not.
a: expired certificate
Jun 30 2025
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:
This only happens, if the smartcard key
- is the only key in the keyring or
- was used for sign/encrypt earlier and thus saved as selection default.
Not sure, what to expect, but generally looks fine for me in gpg4win-5.0.0-beta336 @ win10:
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:
I guess, that's ok then, moving this to done.
Thanks, confirmed then, moving to Done.
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).
Issue with pretty kyber names moved into: T7708.
Moving this to done.
General issues with unformatted fingerprints/keyids moved into T7707.
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?)
Ingo tested this and it worked.
Looks good to me on gpg4win-5.0.0-beta336 @ win10:
- Full stops are fine now
- "not VS-NfD compliant" for invalid signatures not shown anymore (tested in vsd compliance mode)
Looks good to me on gpg4win-5.0.0-beta336 @ win10:
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?
Tested on gpg4win-5.0.0-beta336 @ win10.
Looks good to me on gpg4win-5.0.0-beta336 @ win10.
Looks good to me on gpg4win-5.0.0-beta336 @ win10.
Looks good to me on gpg4win-5.0.0-beta336 @ win10.
I tested the VSD elements on gpg4win-5.0.0-beta336 @ win10 (beta compliance mode).
Happens also in the group config (warning icon):
Looks good to me on gpg4win-5.0.0-beta336 @ win10.
Jun 29 2025
Jun 28 2025
Jun 27 2025
Mostly looks good to me on gpg4win-5.0.0-beta336 @ win10/win11.
since @ebo asked about this: the current state is that the first column of all tables can't be moved. This seems to be what we want, so nothing needs to be changed and nothing was done to change this. I guess this ticket can be closed.
Related? In smartcards view:
Jun 26 2025
Shouldn't the enabled close button in win10 / disabled text / nr2 have green color? (it's the "search certs on server" dialog).
















