I've moved the gpg task to a new ticket, T7133: Add feature to load designated revoker from LDAP
The Kleopatra task is obsolete, as it was noticed that the proposed option is already in gpg and should not be implemented twice.

I assume you only implement this for encryption and not decryption. The latter should always be possible.

Tested with VS-Desktop-3.2.93.391-Beta:

Does not work on windows at all. Seems it doesn't any more on Linux, either (info Tobias)

works, VS-Desktop-3.2.93.391-Beta

works, VS-Desktop-3.2.93.391-Beta

ok, its even on by default, VS-Desktop-3.2.93.391-Beta

tested with VS-Desktop-3.2.93.391-Beta, looks ok.

Go ahead and split it of, then. And setting a key to disabled in Kleopatra itself is not that urgent that it has to be in vsd33.

What is the status here? Werners opinion is that only the kleopatragroupsrc needs to be migrated.

Was mentioned before, but not written here:

We decided to go with Tobias' proposal.

To clarify: this works for "Restart background processes" only, as was the aim of this ticket

forgot to keep it open for test with gpg 2.4 branch versions...

restarting gpg-agent works in release version 3.2.2

I think it would be the most logical solution to always clear the recipients after a switch of protocol. No restoration for other recipients necessary from my point of view.

Well I expect to not get an error if I click on something which might be an unusual use case but is a valid operation.
I do not want Kleopatra to select an appropriate certificate, I expect it to not suggest any certificate for the recipients.

may be related to https://dev.gnupg.org/T5957#163468

Alexander suggested that we could avoid another window by putting check boxes in the revocation window for automatically uploading to the configured keyserver and creating a public key export with the revocation. That could then be configurable via the registry on windows, so that companies could adapt that according to their SOP.

Works on Gpg4win 4.3.1, too.

That said I think we should then strive to use only one "next" window.

We decided the latter is to small an issue, we'll close this ticket without opening another for the reverse case.
Tested only in VS-Desktop-3.1.92.39-Beta yet

The General Error happens also when the PIN is blocked and no Pinentry opens.
As in this case, where the indicated "Generate New Keys" button was used on a blocked card.

I assume the support answers helped, therefore closing this.
In case there is evidence of a bug please give more information and reopen the ticket.

Yes, this ticket was made as a task to be completed for vsd33, so we left out the refinement you suggested on purpose.

As we are running as 32bit software on Windows, the "?" in the output below are a matter of course.

yes, the box comes up, the second "user-level"-Kleopatra exits again after clicking the "ok" Button.
After quitting the Kleopatra process with the admin rights again the privileged background processes remain, like I mentioned in https://dev.gnupg.org/T7050#184583.

Yes, the kleopatra.exe process ist shut down for me with that version, too.
But I wonder if the remaining gpg-agent and scdaemon processes which remain may cause issues later on. The are still running with elevated rights according to the process explorer after restarting as normal user. It does not cause any immediately obvious issues, though.

No more additional dirmngr.exe processes come up in VS-Desktop-3.1.92.39-Beta, too.

Following your suggestion I have created T7067: Kleopatra: Add origin information in search results for the last open point

Note to self: The error message that nothing was found on the keyserver will still come up if one is configured. That will be fixed with T6493.

The certificates from the same test smart card work in Version 3.2.2.231170 (Gpg4win-4.3.1), too, but there all certificates are shown, that is one more than in the VSD version. Seems gpg2.4 can handle certificates which 2.2 does not accept. But that is nothing to complain about.

ok, then I set this ticket to resolved, as it now works in version VS-Desktop-3.1.92.39-Beta as far as in Gpg4win.
That is only the "Refresh Keys" does not work yet. Which we now track in the above mentioned Tickets T7036 and T7037

what about the case that the key has a mail address? Is WKD still checked?

works for latest VSD Beta, too (VS-Desktop-3.1.92.39-Beta)