Confirmed OK for Version 4.0.0.250370 (Gpg4win-5.0.0-beta145)

Version 4.0.0.250370 (Gpg4win-5.0.0-beta145):

tested with Version 4.0.0.250370 (Gpg4win-5.0.0-beta145) on Windows, works!

with version 4.0.0.250370 (Gpg4win-5.0.0-beta145), Kleopatra from Friday.

We have to talk about the workflows in the different variations. This needs to be simplified further.

I looked with alexk at the suggestion from ikloecker https://dev.gnupg.org/T7091#185587
We would modify it a bit to:

Tested with version 4.0.0.250370 (Gpg4win-5.0.0-beta125)
and Yubikey:

Checked with version 4.0.0.250370 (Gpg4win-5.0.0-beta125):

tested with version 4.0.0.250370 (Gpg4win-5.0.0-beta125): no pop-ups

works, Version 4.0.0.250370 (Gpg4win-5.0.0-beta125)

Version 4.0.0.250370 (Gpg4win-5.0.0-beta125):

After testing the feature again with Beta 5.0.0-125 I repeat myself: this works.
There is the action "Unblock card" for unblocking the card with the rest code / PUK.

I think "not certified" is ok if several UIDs with different certification states exist.

Sounds like the animation causes/relies on a deferred destruction. Do we/KF6 delete the popup manually?

Version 4.0.0.250370 (Gpg4win-5.0.0-beta125):

Works as described with Version 4.0.0.250370 (Gpg4win-5.0.0-beta125):

Making some progress on understanding this:

rG25d48663f9 seems to fix this for me. However in my test cases I got a hang in dirmngr simply by running several gpgsm instances to get the details of an X.509 key. I had different logging options enabled, though.

I had this again yesterday. I don't think that scdaemon is involved. gpg-agent.log has this

2025-03-05 15:54:29 gpg-agent[1248] socket file removed - retrying binding
2025-03-05 15:54:29 gpg-agent[1248] Der Socket kann nicht an `C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.gpg-agent' gebunden werden: Unknown error
2025-03-05 15:54:29 gpg-agent[1248] system error code: 0 (0x0)
2025-03-05 15:54:29 gpg-agent[1248] secmem usage: 0/32768 bytes in 0 blocks
2025-03-05 15:55:17 gpg-agent[2088] socket file removed - retrying binding
2025-03-05 15:55:17 gpg-agent[2088] Es wird auf Socket `C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.gpg-agent' gehört
2025-03-05 15:55:17 gpg-agent[2088] socket file removed - retrying binding
2025-03-05 15:55:17 gpg-agent[2088] Es wird auf Socket `C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.gpg-agent.extra' gehört
2025-03-05 15:55:17 gpg-agent[2088] socket file removed - retrying binding
2025-03-05 15:55:17 gpg-agent[2088] Es wird auf Socket `C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.gpg-agent.browser' gehört
2025-03-05 15:55:17 gpg-agent[2088] socket file removed - retrying binding
2025-03-05 15:55:17 gpg-agent[2088] Es wird auf Socket `C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.gpg-agent.ssh' gehört
2025-03-05 15:55:17 gpg-agent[2088] gpg-agent (GnuPG) 2.5.5-beta11 started

and scdaemon logged

2025-03-05 15:55:19 scdaemon[4100] Es wird auf Socket `C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.scdaemon' gehört
2025-03-05 15:55:19 scdaemon[4100] Handhabungsroutine für fd -1 gestartet
2025-03-05 15:55:19 scdaemon[4100] DBG: chan_0x00000000000002d0 -> OK GNU Privacy Guard's Smartcard server ready, process 4100

i.e. there wasn't any scdaemon running before the second gpg-agent started successfully.

When opening the notepad in Kleopatra, open it in a new (non modal) window.
This has the advantage that you can to open several notepads.
Kleopatra has currently only two views for the main window: "Certificates" and "Notepad". Using a separate window for the notepad removes necessity for the the "Certificate" button in the icon bar, as well as the corresponding entry in the "View" menu.
That would also make Kleopatra more homogeneous and cleaner.

Point 1 from the list in the descryption seems to be covered.
Regarding point 2: Is there some visual feedback possible like in web forms when you type a not valid value?
And point 3 from the list: Ingo suggested to do the same as we do for the mail field when adding a UID or creating a key.

It is KF6.9.0 in Gpg4win-5.0.0-beta125

Ok, the behavior is different depending on if

Oh, then I mistakenly assumed that this behavior is the same in Gpg4win and GnuPG-VSD…
Then this seems to be by design although it does not make sense IMHO to handle this aspect differently between 4win und VSD.

I can find no difference between e.g. gpg4win-4.3.0 and 5.0-beta here:

• The window gets smaller when entering a password in both versions
• there is no whitespace between characters in the old version either

Not reproducible on Linux (with KF 6.11): When clicking the drop down triangle the popup briefly flashes (opens and immediately closes) before the error window is shown. Maybe the bug was fixed in the meantime. Needs to be checked.

In the spirit of making the UI less cluttered, I'd be in favor of removing this line entirely.

Tobias: Maybe add the patch versioned for kwidgetsaddons-6.9.0 for now so that it can be evaluated early.

As of KF6.112, the datepicker will indicate invalid dates and not allow selecting them. We should update to that version, once it's out, or patch in c3f643639164914238dd8f19f03ea49298408293 of kwidgetsaddons

Ok, with VSD 3.3.0 and 4win 4.4.0 both I see

--import-options only-pubkeys

in a gpgme log when importing a key from WKD.

I remove the milestone tag, as that one means "fixed in version 2.2.46" and added the general gnupg tag

You could probably check that Kleopatra/gpgme calls gpg with the import option "only-pubkeys". For a real world test you'd have to upload a secret key to WKD.