https://bugs.kde.org/show_bug.cgi?id=392321

            Bug ID: 392321
           Summary: ktorrent still cannot download torrents from magnet
                    links
           Product: ktorrent
           Version: 5.1
          Platform: Kubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: joris.guis...@gmail.com
          Reporter: vatb...@yahoo.com
  Target Milestone: ---

Kubuntu 17.10 with backport KDE 5.12.3 running a vpn connection:

I clicked on the below magnet link on a famous bay/pirate site: 
ktorrent starts, with in the Magnet Downloader section showing "Status:
Downloading" and "peers: 12" but nothing appear in the Torrents section!
I then ran ktorrent from konsole, output see below.
My ktorrent can download torrents with regular torrent files just fine.

But this famous site has only magnet links.

Transmission just works with magnet links. 

I have looked at https://bugs.kde.org/show_bug.cgi?id=302152
and https://bugs.kde.org/show_bug.cgi?id=302997
and
https://forums.opensuse.org/showthread.php/504004-ktorrent-magnet-link-issue?p=2686856#post2686856


magnet:?xt=urn:btih:14d95e3b9c7a5711f7360a671a1343ee84877a6f&dn=SQL%3A+Practical+Guide+for+Developers+-+PDF&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969&tr=udp%3A%2F%2Fzer0day.ch%3A1337&tr=udp%3A%2F%2Fopen.demonii.com%3A1337&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr=udp%3A%2F%2Fexodus.desync.com%3A6969

konsole output:
vat@bier:~$ ktorrent 
zo mrt. 25 18:58:09 2018: Cannot create socket : Address family not supported
by protocol
zo mrt. 25 18:58:09 2018: Failed to set the reuseaddr option : Bad file
descriptor
zo mrt. 25 18:58:09 2018: Cannot bind to port :::6881 : Bad file descriptor
zo mrt. 25 18:58:09 2018: Bound to 0.0.0.0
zo mrt. 25 18:58:09 2018: Bound to TCP port 6881
zo mrt. 25 18:58:09 2018: DHT: Starting on port 7881
zo mrt. 25 18:58:09 2018: Cannot create socket : Address family not supported
by protocol
zo mrt. 25 18:58:09 2018: Failed to set the reuseaddr option : Bad file
descriptor
zo mrt. 25 18:58:09 2018: Cannot bind to port :::7881 : Bad file descriptor
zo mrt. 25 18:58:09 2018: DHT: Failed to bind to ::
zo mrt. 25 18:58:09 2018: Bound to 0.0.0.0
zo mrt. 25 18:58:09 2018: DHT: Bound to 0.0.0.0
zo mrt. 25 18:58:09 2018: Cannot open /home/xbmc/.local/share/ktorrent/groups :
No such file or directory
zo mrt. 25 18:58:09 2018: Cannot create socket : Address family not supported
by protocol
zo mrt. 25 18:58:09 2018: Failed to set the reuseaddr option : Bad file
descriptor
zo mrt. 25 18:58:09 2018: Cannot bind to port :::8881 : Bad file descriptor
zo mrt. 25 18:58:09 2018: Bound to 0.0.0.0
zo mrt. 25 18:58:09 2018: Doing tracker request to url :
udp://tracker.leechers-paradise.org:6969
zo mrt. 25 18:58:09 2018: Doing tracker request to url : udp://zer0day.ch:1337
zo mrt. 25 18:58:09 2018: Doing tracker request to url :
udp://open.demonii.com:1337
zo mrt. 25 18:58:09 2018: Doing tracker request to url :
udp://tracker.coppersurfer.tk:6969
zo mrt. 25 18:58:09 2018: Doing tracker request to url :
udp://exodus.desync.com:6969
zo mrt. 25 18:58:09 2018: DHT: Doing announce 
zo mrt. 25 18:58:09 2018: Loading home page from
/usr/share/ktorrent/search/home/home.html
zo mrt. 25 18:58:09 2018: Started update timer
zo mrt. 25 18:58:10 2018: DHT: Got 1 potential peers for torrent SQL%3A
Practical Guide for Developers - PDF
zo mrt. 25 18:58:10 2018: DHT: finding node 
zo mrt. 25 18:58:10 2018: DHT: Got 1 potential peers for torrent SQL%3A
Practical Guide for Developers - PDF
zo mrt. 25 18:58:10 2018: DHT: Got 1 potential peers for torrent SQL%3A
Practical Guide for Developers - PDF
zo mrt. 25 18:58:10 2018: Suppressing sleep
zo mrt. 25 18:58:10 2018: DHT: Got 5 potential peers for torrent SQL%3A
Practical Guide for Developers - PDF
zo mrt. 25 18:58:10 2018: Initiating connection to 138.199.64.240 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 5.121.15.16 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 14.202.8.212 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 23.19.87.230 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 23.19.87.230 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 23.83.37.183 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 23.227.207.19 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 37.133.34.11 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 37.230.180.42 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 58.7.109.110 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 64.62.244.51 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 64.120.52.221 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 66.73.204.230 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 67.58.203.120 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 68.175.101.3 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 71.56.241.24 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 72.182.150.170 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 75.106.61.1 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 77.48.148.6 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 78.30.36.29 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 78.46.45.113 via (TCP)
zo mrt. 25 18:58:10 2018: Authentication to 37.133.34.11 : failure
zo mrt. 25 18:58:10 2018: Authentication to 64.62.244.51 : failure
zo mrt. 25 18:58:10 2018: Authentication to 77.48.148.6 : failure
zo mrt. 25 18:58:10 2018: Initiating connection to 78.96.83.186 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 78.100.207.162 via (TCP)
zo mrt. 25 18:58:10 2018: Initiating connection to 78.192.236.75 via (TCP)
zo mrt. 25 18:58:10 2018: Not enough data received, encrypted authentication
failed
zo mrt. 25 18:58:10 2018: Authentication to 68.175.101.3 : failure
zo mrt. 25 18:58:10 2018: Initiating connection to 79.116.243.129 via (TCP)
zo mrt. 25 18:58:11 2018: Authentication to 78.100.207.162 : failure
zo mrt. 25 18:58:11 2018: Initiating connection to 79.138.106.51 via (TCP)
zo mrt. 25 18:58:12 2018: Authentication to 79.116.243.129 : ok
zo mrt. 25 18:58:12 2018: Starting socketmonitor threads
zo mrt. 25 18:58:12 2018: Initiating connection to 81.171.97.59 via (TCP)
zo mrt. 25 18:58:14 2018: PEX: found 30 peers
zo mrt. 25 18:58:15 2018: Timeout occurred
zo mrt. 25 18:58:15 2018: Authentication to 138.199.64.240 : failure
zo mrt. 25 18:58:15 2018: Timeout occurred
zo mrt. 25 18:58:15 2018: Authentication to 5.121.15.16 : failure
zo mrt. 25 18:58:15 2018: Timeout occurred
zo mrt. 25 18:58:15 2018: Authentication to 14.202.8.212 : failure
zo mrt. 25 18:58:15 2018: Timeout occurred
zo mrt. 25 18:58:15 2018: Authentication to 23.19.87.230 : failure
zo mrt. 25 18:58:15 2018: Timeout occurred
zo mrt. 25 18:58:15 2018: Authentication to 23.19.87.230 : failure
zo mrt. 25 18:58:15 2018: Timeout occurred
zo mrt. 25 18:58:15 2018: Authentication to 23.83.37.183 : failure
zo mrt. 25 18:58:15 2018: Timeout occurred
zo mrt. 25 18:58:15 2018: Authentication to 23.227.207.19 : failure
zo mrt. 25 18:58:15 2018: Timeout occurred
zo mrt. 25 18:58:15 2018: Authentication to 37.230.180.42 : failure
zo mrt. 25 18:58:15 2018: Timeout occurred
zo mrt. 25 18:58:15 2018: Authentication to 58.7.109.110 : failure
zo mrt. 25 18:58:15 2018: Timeout occurred
zo mrt. 25 18:58:15 2018: Authentication to 64.120.52.221 : failure
zo mrt. 25 18:58:15 2018: Timeout occurred
zo mrt. 25 18:58:15 2018: Authentication to 66.73.204.230 : failure
zo mrt. 25 18:58:15 2018: Timeout occurred
zo mrt. 25 18:58:15 2018: Authentication to 67.58.203.120 : failure
zo mrt. 25 18:58:15 2018: Timeout occurred
zo mrt. 25 18:58:15 2018: Authentication to 71.56.241.24 : failure
zo mrt. 25 18:58:15 2018: Timeout occurred
zo mrt. 25 18:58:15 2018: Authentication to 72.182.150.170 : failure
zo mrt. 25 18:58:15 2018: Timeout occurred
and it continues at nauseum.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to