Done and backported for VSD 3.4.

This was fixed in Okular with https://gitlab.freedesktop.org/poppler/poppler/-/merge_requests/2115 . The MR was merged 2026-02-05.

It turns out that the problem occurs if one clicks with the mouse quickly (< 1 s) after typing a character.

I cannot reproduce this with the released Gpg4win 5.0.1 on Windows 10 (VM).

Done.

Backported for VSD 3.4

We decided to backport to VSD 3.4 because it fixes an accessibility issue.

Backported for VSD 3.4

We decided to backport to VSD 3.4 because it fixes an accessibility issue (wrong tab order).

Fixed.

The fix also fixes the wrong tab order of the Close button. (See T8125: Kleopatra: Wrong tab order of "Show Email" button for the same problem concerning the Show Email button.)

Regarding the above comments:
Currently, the Show Email button is never shown in the notepad and the Close button (as X) is only shown in the notepad. So, in the notepad there's only Show Audit Log next to X. And elsewhere there's Show Audit Log and, if applicable, Show Email below.

Changing the position needs some more thought. There can be up to four buttons displayed next to the result:

• Force decryption is shown if decryption failed due to a missing integrity check (MDC)
• Show Audit Log is always shown (unless retrieving the audit log failed)
• Show Email is shown if the decrypted content is something that can be opened in the mail viewer
• Close is always shown in the notepad

"Show audit log" is already a button (probably changed for another ticket). I'll look into the remaining points.

I have implemented this for all tables in T6568. I missed this extra ticket. I'll merge it with T6568.

The workaround is ready for testing. Kleopatra shouldn't show duplicate LDAP servers in the settings dialog. As a side effect global ldapserver entries should no longer multiply in the local dirmngr.conf each time the LDAP servers are changed, but one copy of the global ldapserver entries is still written to the local dirmngr.conf.

Backported for VSD 3.4

Done.

One doesn't even need a global config file to reproduce the duplication.

I'm okay with omitting the list of suggestions for shared secret keys. The person distributing the key should have told the recipients how to import and certify them properly.

Also backported for VSD 3.4.

Now also available in Gpg4win 5.

Ready for testing in VSD 3.3

What about always using PEM for all generated CSRs? As far as I can see, gpgsm command line always uses PEM when generating CSRs.

Backported for VSD 3.4

For all tables where the visible columns can be configured via the context menu of the table header the visible columns can now also be configured via the context menu of the table cells/rows. (The only exception is the result table in the selftest where it doesn't really make sense to change the visible columns. Instead we should disable the context menu of the table header.)