This ticket is obsolete

Gpg4win 4.4:
When a keyserver is configured you can now check a box to directly upload the revocation there:

I assume the problem has been resolved because we never got feedback that the problem persists.

Interesting. Just a few days ago I noticed that Kleopatra creates a new tab with the imported certificates except when the import is done via the notepad (or via the clipboard). I guess we could add an option to open a tab with the imported certificates to the import result window.

This problem has been fixed quite some time ago. See https://bugs.kde.org/show_bug.cgi?id=415168.

This doesn't look like a problem in Kleopatra.

We have to take the list of OIDs to ignore into account that can be configured for gpgsm with ignore-cert-with-oid.

We won't revert to the old UI which had its own share of problems. In the meantime Kleopatra supports certificate groups which should help if you often need to encrypt for the same keys.

Closed, since this was documentation for the workaround, four years ago.

Kleopatra now let's gpg deal with I/O directly. This makes decryption with Kleopatra as fast (or slow) as with gpg on the command line. Hence I'll remove the Kleopatra tag.

Just a reminder: with Gnuk 1.2.15 and an ed25519 key PubkeyAuthentication unbound is required for hosts using the new feature.

Then please upload whatever README you want there. My release checklist does not mention any README.

Put it under lower priority, as it's basically programming error.

OK, it's done. closed.

I get this message even with --quiet:

Here is my proposal to avoid unsynched state for data.

diff --git a/src/client.c b/src/client.c
index 410f940..0989984 100644
--- a/src/client.c
+++ b/src/client.c
@@ -250,6 +250,7 @@ assuan_transact (assuan_context_t ctx,
   int off;
   char *line;
   int linelen;
+  gpg_error_t last_err = 0;

Done for 2.5.0.

Done in 2.5.0.

Fixed in 2.5.0.

Fixed in 2.5.0.

Fixed in 2.5.0 and 2.4.6.

Fixed in 2.5.0 and 2.4.6.

Fixed in 2.4.6.

Fixed in 2.4.6.

Fixed in 2.4.6.

I believe this was fixed by T7386. Or it is now no hard lock up by T7402.
So, let me close this ticket.
If any new symptom, please add information into T7396.

I can say it's fixed in 2.4.7.

Fixed.

I also checked this on Windows 10 with light, dark and high contrast (theme No. 1) colors: