Kleopatra has no influence on this. This does surely also happen when a new keypair is created on the command line.

Works as well for VS-Desktop-3.2.94.481-Beta

In VS-Desktop-3.2.94.481-Beta the feature is not available in the context menu in Kleopatra.
So in VSD 3.3.0 this will be missing. What works is disable/enable on the command line and Kleopatra will then not list a disabled certificate with most filters.

VS-Desktop-3.2.94.481-Beta: OK

VS-Desktop-3.2.94.481-Beta: OK

VS-Desktop-3.2.94.481-Beta: looks the same as with Gpg4win 4.4.

The component here is KDateComboBox and it desperately needs something like this. It should probably be colors signifying a "disabled" state for those dates

In case of build problems related to a failed test you may want to apply rEb6df311368133df90c3bf338fbf5c90bd8d950f8.

With VS-Desktop-3.2.94.481-Beta:
If an Ldap NtdsKeyserver is configured, there is now no warning on the upload. But the success message is wrong or at least not right:
"OpenPGP certificates exported successfully." Made me think I did mistakenly choose something other than "Publish on server".
And the menu entry is "Publish on Server..." so there has to be another window before action is taken.

Same in VS-Desktop-3.2.94.481-Beta

If you want to write a new thing please also consider the rendering hints gpg-agent can send to the pinentry. This is enabled if the Pineentry sends back a FEATURES sstatus tring with the keyword "tabbing".

Ok now:

FWIW, the original idea with Pinentry was to have a stripped down Widget which allows to securely enter the password. For that we even replaced the Gtk text widget to have better control over the code path from keyboard to screen. After a few years more more more stuff was requested and meanwhile the QT version of the Pinentry is probably larger than the gpg-agent process.

VS-Desktop-3.2.94.481-Beta: We now bring up the German version for the SecOps, as we do not have an official translation yet. The document will be replaced when we have that

Works in VS-Desktop-3.2.94.481-Beta and you even see beforehand which algo will be used:

For command line, reported issues have been fixed; Confusions for wrong errors are gone, it correctly reports appropriate errors of:

• GPG_ERR_PIN_BLOCKED
• GPG_ERR_NO_RESET_CODE
• GPG_ERR_BAD_PIN

Do you think it's too difficult for a beginner to write a pinentry-gtk4?

VS-Desktop-3.2.94.481-Beta: same as for the Gpg4win version.
And there is a hint if you enter "hkps://something" that this is not the right format (that is included in Gpg4win 4.4.0, too)

VS-Desktop-3.2.94.481-Beta: the option is removed in the Kleopatra settings and the tags are shown in the main certificate list as well as in the tabs of the certificate details.

The Qt dialog on fullscreen is interesting and it gives me an idea. Maybe if we center its contents? (on GTK, of course)

The Signature Card V2.0 is automatically loaded in VS-Desktop-3.2.94.481-Beta.
Other Telesec Cards, too, though this might take quite a while (e.g. the NetKey 3.0 card) and often a new reload is required.

Still, it is possible to provide a simple password entry window with GTK4, and there could be a way to enable fullscreen mode for that.

VSD-Beta-481: Encrypting/signing with gpgtar on the cli and decrypting/verifying with Kleopatra works

I set this to resolved after a quick replay of the original report situation did not show any issue.
If it occurs again please reopen.

What is the status (or maybe better scope) of this ticket? Why was it set to the milestone 2.4.5?
I do not see any improvement in Kleopatra from Gpg4win 4.4 (with gpg 2.4.7) regarding the behavior when trying to unblock a card.

Reported gnupg channel on IRC.
An ascii armored file in question was: https://github.com/syncthing/syncthing/releases/download/v1.29.2/sha256sum.txt.asc

Fixed in: rGb1857a2836c9: gpg: Fix handling with no CRC armor.

When CHECKCRC == 0 (no CRC), ->any_data was not set, resulted

	no valid OpenPGP data found.

wrongly.

I think I can understand you, too much complexity.