Libkleo does not specify the curve in the parameter file becuase keyCurvve:isEmpty is asserted:

Works on the command line and adding a subkey later does also work.

config file: Sorry, I got confused, it has to be %APPDATA%\GnuPG VS-Desktop\kleopatrarc in this case (VS-Desktop-4.0.90.1203-Beta), of course. And this one works.
Registry entry SOFTWARE\GnuPG VS-Desktop\Kleopatra\CMS\SaveCSRAsPEM does not work, though. But this is a separate issue, seems all Registry entries do not work in that build.

• config file: According to T7717: Location of qt-application config files %APPDATA%/Gpg4win/kleopatrarc should work.
• registry: According to T5707: Kleopatra: Use windows registry additionally to config files this should be SOFTWARE\Gpg4win\Kleopatra\CMS\SaveCSRAsPEM now

Works with VS-Desktop-4.0.90.1203-Beta when putting this in C:\Program Files\GnuPG VS-Desktop\share\kleopatrarc
CSR is then saved as .pem file with ascii-armored content.

The new German tool tip is shown in Gpg4win 5.0.2 (Beta)

I found that it's not that simple to accept the case of no newline at the end.
Because we need to handle the edge case where no newline occurs at the maximum buffer length, too.
It's something like the following.

Done and backported for VSD 3.4.

Thanks for the info!

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

Does not work in the latest Gpg4win builds (5.0.0. to 5.0.2).
I have no idea which commit would be needed, I see no commit with this bug-ID.

So ok, go ahead Ingo with your plan in https://dev.gnupg.org/T7502#213972

As the migration to keyboxd will happen not too far in the future, we'll close this ticket.
Keylisting should meanwhile already be faster due to other changes.

Closing this as invalid.

I tend to agree with keeping it short and close to the wording we use for normal public key imports.

Ok, the behavior in gpg4win-5.0.0-beta413 @ win10 is the same (< 1s).
I can also reproduce the same behavior in other windows dialogs, e.g. in the explorer (changing the location address, clicking on the search input field).
So i'd also say, that this is a virtualbox or win issue and would just close this as invalid without further testing?

I'll also retest this with gpg4win-5.0.0-beta413. I think, this bug was different back then (no need to do it quickly). If it's gone there, too, it might have been a virtualbox or win bug. If it's still there, it might hint at qt/kde.

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

I was too fast with closing this, seems it is reproducible under special conditions. But not by me, here it works.

Me neither, neither on Win10 or 11. I tried the original description and https://dev.gnupg.org/T7943#208784

I can still reproduce this with gpg4win-5.0.1 @ win11

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