Version: 4.4 (using KDE 4.4.5) OS: Linux Some keyservers such as onak can return long keyids/fingerprints. Kleopatra fails dealing with such keys/keyservers. Reproducible: Always Steps to Reproduce: In Kleopatra, specify a keyserver which runs e.g. onak Search for keys. Actual Results: In the dialog box with the list of found keys, if some keys have a long UID, fingerprint of the first one will be empty and the list will stop, failing to display the remainder keys. Behind the scene, kleopatra (or whatever middleware) uses gpg to query the keyserver. Here is an example in command-line of the query from kleopatra, searching for keys with "teuwen" in it: $ gpg --use-agent --batch --no-sk-comment --status-fd 1 --no-tty --charset utf8 --enable-progress-filter --display :0.0 --ttyname /dev/pts/6 --ttytype xterm --with-colons --fixed-list-mode --with-fingerprint --with-fingerprint --search-keys -- teuwen gpg: searching for "teuwen" from hkp server xxx.xxxxxxx.xxx info:1:2 pub:00112233445566778899AABBCCDDEEFF00112233:1:3072:1201784426:: uid:Philippe Teuwen <censored> pub:440A3A9E56E9D90E99D763A87A135F579AD7E3DB:17:1024:1020637827:: uid:Philippe Teuwen (Doegox) <phil@teuwen.org> In Kleopatra, I'll see only the firs key, without fingerprint info in the dialogbox Now if I intercept gpg call and truncate keyIDs to keep the last 8 bytes: pub:CCDDEEFF00112233:1:3072:1201784426:: uid:Philippe Teuwen <censored> pub:7A135F579AD7E3DB:17:1024:1020637827:: uid:Philippe Teuwen (Doegox) <phil@teuwen.org> Kleopatra happily displays the keys and accepts to import them.
I forgot to tell, same error from Kleopatra 2.1.0 in gpg4win 2.1.0
Is it still relevant with current Kleopatra? Can you give us a (public) domain of the keyserver to reproduce?
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Created attachment 155016 [details] attachment-28097-0.html Hello I don't use KDE anymore so I cannot test it. On 04/01/2023 08:05, Justin Zobel wrote: > https://bugs.kde.org/show_bug.cgi?id=270149 > > Justin Zobel<justin.zobel@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > Status|REPORTED |NEEDSINFO > > --- Comment #5 from Justin Zobel<justin.zobel@gmail.com> --- > Thank you for reporting this issue in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! >
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!