Bug 172063 - timeout when searching a key not handled properly
Summary: timeout when searching a key not handled properly
Status: RESOLVED WORKSFORME
Alias: None
Product: kgpg
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Rolf Eike Beer
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2008-10-03 06:09 UTC by Philippe Cloutier
Modified: 2018-10-29 02:05 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe Cloutier 2008-10-03 06:09:44 UTC
Version:            (using KDE 3.5.10)
OS:                Linux
Installed from:    Debian testing/unstable Packages

When there's a timeout searching for a key, KGpg doesn't tell, but simply shows "Found 0 matching keys". While this is not technically incorrect, this is very misleading.

For example, this currently happens when searching on 212.55.198.213, though this is part of the wwwkeys.eu.pgp.net round-robin and will hopefully be fixed quickly.
Comment 1 Kavinda 2018-05-09 17:01:35 UTC
Is this still an issue?
Comment 2 Philippe Cloutier 2018-05-10 02:55:01 UTC
I haven't used KGpg since about the time I filed this report. And the server which exposed the problem must have been fixed or decommissioned since, so sorry, but I don't know and surely couldn't easily test.
Comment 3 Andrew Crouthamel 2018-09-28 03:37:40 UTC
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 set the bug status 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!
Comment 4 Andrew Crouthamel 2018-10-29 02:05:13 UTC
Dear Bug Submitter,

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!