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.

I have no idea how to test this aside from the test done in T7146.

In VSD 3.3.0 I can not check with "Rückstellcode" as the error message is now "Falsche PIN".
And the same in the released version Gpg4win 4.4.0.
Seems the gpg version now returns a different string:

No totally new install: I quit Kleopatra, then deleted %APPDATA%\kleopatra\kleopatrastaterc and %APPDATA%\gnupg and restarted Kleopatra. Then I imported the shown test certificate which has no expiry date.

I can't reproduce this. Was this with a fresh install or is it possible that there were existing column widths loaded from a state file?

Checked again with VSD 3.3.0: no error any more. Therefore setting this to resolved, I probably made a mistake the last time.

works as described.

Closing this ticket after creation of two follow up tickets for the remaining issues.

The certificate can also be downloaded from https://www.bsi.bund.de/DE/Service-Navi/Kontakt/smime.html

Remarks:

• This works now on Windows and with the AppImage. This was achieved by customizing the internal application name of Kleopatra: kleopatra-vsd for GnuPG VS-Desktop, kleopatra-gpd for GnuPG Desktop, kleopatra for everything else.
• As a side effect the different flavors of Kleopatra now use different names for the main config file and for the state file, i.e. Gpg4win uses kleopatrarc and kleopatrastaterc, GnuPG VS-Desktop will use kleopatra-vsdrc and kleopatra-vsdstaterc, and GnuPG Desktop will use kleopatra-gpdrc and kleopatra-gpdstaterc.
• The internal application name is also used for config entries retrieved from the registry. That means that for VSD and GPD different registry paths are used in future releases.
• Testing on Windows requires T7040: Make it possible to install GnuPG VSD and GPD in parallel.

Some remarks:

• All Kleopatras use GNUPGHOME/kleopatra for the config files, but they use different names for the main config file and for the state file, i.e. Gpg4win uses kleopatrarc and kleopatrastaterc, GnuPG VS-Desktop will use kleopatra-vsdrc and kleopatra-vsdstaterc, and GnuPG Desktop will use kleopatra-gpdrc and kleopatra-gpdstaterc. That's a side effect of the changes for T7528: Make it possible to run Kleopatra VSD and Kleopatra GPD in parallel where the internal application name is set to kleopatra, kleopatra-vsd or kleopatra-gpd for the different flavors.
• The Kleopatra configuration files are not migrated to the new location. (The group configuration should already have been migrated.)

By the way, this also works for different GNUPGHOME. Tested with a gpgconf.ctl file with content gnupg = gnupg-gpd next to gpgconf.exe.

Kleopatra now writes/reads all config files to/from GNUPGHOME/kleopatra.