Bug 304278 - Magnet links with broken trackers fail to do open
Summary: Magnet links with broken trackers fail to do open
Status: RESOLVED DUPLICATE of bug 302997
Alias: None
Product: ktorrent
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: FreeBSD Ports FreeBSD
: NOR normal
Target Milestone: ---
Assignee: Joris Guisson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-30 10:52 UTC by bugmenot2
Modified: 2012-07-30 16:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bugmenot2 2012-07-30 10:52:55 UTC
If a magnet link has trackers which are unable to be reached Ktorrent does not time out or alert the user of anything, it waits indefinitely with no feedback.

I think this is what is happening for other people, in the case of :
https://bugs.kde.org/show_bug.cgi?id=302152

Since it is waiting for the file list, there is no feedback and a user might click many times trying to get the torrent to work, resulting in requests that just sit around. The attempt should be aborted and the user notified. It would also be nice to have the torrent added before the file list is fetched, this would enable manual tracker entry.

At the moment I have to adjust the url to use a working tracker each time - pretty much all public trackers are blocked and I don't use DHT (does not seem to help even if enabled)

Reproducible: Always

Steps to Reproduce:
1. Get a valid magnet link with a tracker
2. Break the tracker URI to something that will not work
3. Try to get Ktorrent to download the magnet link
Actual Results:  
Nothing visible happens, no user feedback (A warning about DHT if you have that disabled, but it's unrelated)

Expected Results:  
To be able to specify the tracker for the torrent, or at least notified that there was a problem.

Ktorrent is lovely - to the devs; keep up the good work :)
Comment 1 Joris Guisson 2012-07-30 16:08:26 UTC

*** This bug has been marked as a duplicate of bug 302997 ***