I decided to add a retry count (=1). I check the implementation of usbd-ccid-0.4.0, it's ZLP (zero length packet) handling mistake.

In short, it looks like the icon change was only applied to separate mail windows, not to mails in the preview pane

We explicitly don't want potentially disastrous low-level card operations like a factory reset to be possible from within Kleopatra.

But I wonder anyway if we could a) sometime in the future implement a heuristic to insert a break before an error message if there is not enough space for it or b) only give the filename in these kinds of messages. The path is not important in this case, at least. I'm not sure if the path is important in other cases, too, though.

Allright, set to Wontfix.

I suggest to close this ticket. There will always be situations where the layout is suboptimal.

I don't think that Kleopatra can influence that gpg/gpgsm/gpg-agent shows a second pinentry if on the first try a wrong passphrase was entered. Therefore I think the "retry" has to be implemented in GnuPG.

@ikloecker I guess, this issue is not specific to smartcard errors?

test with gpg4win-5.1.0-beta658 and gpgol-2.7.3-beta11_dd853c7.dll on WIN 10

Note that all highlighting (i.e. grey background) of the icon in the following screenshots is due to opening the settings, before i did that, they were not highlighted if it was not sign+encrypt chosen but only one of them.

Looks beautiful to me on gpg4win-5.1.0-beta658 @ win11

In T8018#219988, @ebo wrote:

seems to me, that the details here are no details and could be dropped completely. I'm i overlooking something?
And wouldn't "Could not sign: Wrong passphrase" be better? Or even better: "Signature failed: Wrong passphrase"?
In Kleopatra we have: "Signing failed: %1"

The "missing path" on verification of test.txt is caused by a bug in the code: T8337: Kleopatra: Verifying detached OpenPGP signatures uses different code paths.

Wouldn't it be an idea to use a short delay and a retry count limit?

I need this patch for ccid-driver.c (which is not clean, but device specific):

diff --git a/scd/ccid-driver.c b/scd/ccid-driver.c
index 2e955ea52..df7bfefc2 100644
--- a/scd/ccid-driver.c
+++ b/scd/ccid-driver.c
@@ -2139,6 +2139,9 @@ bulk_in (ccid_driver_t handle, unsigned char *buffer, size_t length,
     return CCID_DRIVER_ERR_INV_VALUE;  /* Faulty libusb.  */
   *nread = msglen;

Following the description of https://github.com/Nitrokey/nitrokey-3-firmware/blob/main/docs/usbip.md
I managed to run it by cargo run --features ccid.
I can see it by lsusb:

... ID 20a0:42b2 Clay Logic Nitrokey 3A Mini/3A NFC/3C NFC

But it fails (disappeared) when I do lsusb -v -d.
When I do usbip attach -r localhost -b 1-1 again, it appears again.

In T6702#219802, @ebo wrote:

Yes, that's a separate issue.

does a ticket exist for it?

Yes, that's a separate issue.

does a ticket exist for it?

In T6702#219707, @timegrid wrote:

• On gpg4win, the button is not red - that's ok?

Looks good to me on gpg4win-5.1.0-beta646 @ win11: