In a current version I see this at least if I do not quit Kleopatra completely and restart to another screen setting. Further testing at the moment is not warranted, as there will be changes to the columns handling with the switch to Qt6. (T6924)

From your description it is not clear what you did exactly.

I assume you mean the information shown in the subkeys window int the column "Strength"?

with Version 3.2.2.231170+git~ (Gpg4win-4.3.1-beta12):

• no error message any more with keyserver = none
• correct error message when choosing "publish on server"

But in the case "Refresh OpenPGP keys" (in Kleopatras certificate Details) there is no error message but instead ~"the key is unchanged".

Version 3.2.2.231170+git~ (Gpg4win-4.3.1-beta12): works, when entering a mail address the search result is presented very fast now. When entering only a name, nothing happens. So functionality is there, the improvement in UX is T6493.

Andre said instead of removing "more documentation" for Gpg4win, he'd like to put links to relevant documentation there, e.g. the gpg manual.

For VSD there should at least no info message be shown - which has to be clicked away - when keyserver is set to "None"

While we see issues with gpg-agent not starting in different circumstances (like with the empty keylist) I would like to keep this task here about the smart card tab.

Ingo came up with the idea to put all the filter definitions in a config file in the GNUPGHOME.

The validity column does not contain that information in case only the encryption subkey has expired.
As is the case if people extended an expired keypair via Kleopatra with VSD up to 3.1.26.

This is basically done although not exactly as proposed here.
But WKD and Keyserver search are now combined. With WKD search only if you configure keyserver "none".

Werner wants the import via gpg-agent

It seems I did not express myself clearly.
I would prefer it if the "with subkeys" checkbox could not be enabled in case it won't extend any subkeys anyway.
With a bonus tooltip.

A workaround which (currently) works for flagging and categories both is:

As a change in behavior is not possible, we continue with the button solution here: T6984: Kleopatra: Add icon for folder encryption

But like it is now one would only go into the subkey view after things start behaving unexpectedly. After all, "I told the program to extend the subkeys", why should I verify if it really did this?
If the box "extend validity for subkeys" could not be checked in case no keys will be extended, I would then go to the subkey details, if I wanted to extend them, too.

I would like to change the description of this ticket.
Which way do we want to go?

Closing this outdated ticket

Setting a date on the command line is in UTC, displayed in Kleopatra is the corresponding local date which might therefore be one day of. This is as intended and the same for dates before or after the Y2038 cut off.
-> Works with Gpg4win-4.3.0

As in my test case Kleopatra didn't check the box for "with subkeys" when the extension wouldn't work I propose as minimal solution:

• disable the checkbox if no key would be extended anyway + info why the box is not checkable (via tooltip)

You are (of course) right, gpg -k shows the keys in that order. Which is different from the order shown in the smartcard management view and what gpg-card shows. So lets drop that point for now and maybe discuss this some time in the future.

Hidden for Gpg4win-4.3.0-beta571, too

In Gpg4win-4.3.0-beta571 with GnuPG 2.4.4-beta132

>echo test | gpg --sign --default-key F8D51DE0EE16E9B57009B8DE458612006D8E6F0D
gpg: Warning: not using 'F8D51DE0EE16E9B57009B8DE458612006D8E6F0D' as default key: Key expired
gpg: all values passed to '--default-key' ignored
gpg: no default secret key: Unusable secret key
gpg: signing failed: Unusable secret key

works in Gpg4win-4.3.0-beta571

@aheinecke For Gpg4win I do not have a suitable test version yet.

Is the problem that another success message is shown after deleting the local copy?

The fix was not included in the Testbuid...

Does not work in Gpg4win-4.2.1-beta178

works in Gpg4win-4.2.1-beta178
Note to self: need to check with "to the second" expiry time, in case this only occurs with summertime

works in Gpg4win-4.2.1-beta178