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?)

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.

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.

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.

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.

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.

One screenshot of the test setup for reference:

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:

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

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

Created new ticket for decision described above in https://dev.gnupg.org/T7699#202399

Thanks for the Windows 11 screen shots.

We decided to only add a green check mark (or red X in case it fails) on the left side in the message frame.

Thanks for the feedback. The issues are the same as on win10:

After discussion with Ingo and others it seems that separate Kleo processes per GNUPGHOME would confuse more users than being helpful for power users. Considering the use case of gpgpass the conclusion was to add an option to Kleo which allows to start is as a certificate manager without doing the UniqueApplicaiton thing and also entirely quit after closing the window.

Regarding the "unsure" findings:

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

1. Issues found

But we have the same problems on Unix as described by T7699. (funny, the other bug mentioned above has 76 reversed)

This will never happen on stock Linux.

We decided to keep the color white for these cases and only add some further information, see T7701: Draft: Kleopatra: Add information for verification results

I know of no current Linux issue with this, I thought only the MSI installer is affected

That is not Windows specific. They should end up in %GNUPGHOME%/kleopatra/

What about including the output of

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

Note that the first screenshot shows still "Sign/Encrypt" as button text instead of "Finish", but I didn't notice that again after this

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.

We decided in T7579: Kleopatra: improve menu items to remove this action. Users will instead have to mark certificates they want to update and use the Update Certificates action in the "Certificates" menu.

Can be tested with next VSD 3.3.x build.