Trackers are not added through magnets.

[nemonein]

I'm using Deluge as client/server model.
Both deluges are 2.1.0 on Ubuntu machines.

I added a torrent through magnet.

Code: Select all

magnet:?xt=urn:btih:FRVWQWGWDWUVIPKCGGTR3NFRZETEWBUF&dn=ubuntu-22.04-desktop-amd64.iso&xl=3654957056&tr.1=https%3A%2F%2Ftorrent.ubuntu.com%2Fannounce&tr.2=https%3A%2F%2Ftorrent.ubuntu.com%2Fannounce&tr.3=https%3A%2F%2Fipv6.torrent.ubuntu.com%2Fannounce

There are info about trackers on the magnet, but when it is added to Deluge 2.1.0, trackers are ignored.

[Spire]

Same problem here.

Deluge running in Client/Server configuration on Ubuntu 18.04 (client)/20.04 (server). Installed via Deluge Team PPA.

Click magnet link, torrent is added, however, trackers are not added for the torrent.

[mhertz]

Hmm, I tested it briefly yesterday, and worked seemingly - check with right-clicking magnet and select 'edit trackers' to see them added. I didn't post yesterday because needed first look into how deluge works with multi-tracker torrents, well I know it only announce to one tier by default, and with the magnet-URI's '&tr=' arg then gets new tier each defined tracker, and so need ltconfig Plugin and enabling announcing to all trackers/tiers additionally if wanted otherwise, but I mean that I don't know how works in deluge's gtk-UI, regarding if only show tracker when actually announced to, or what.

Also needed check why I see a unsupported url protocol message for the dht - never seen that before and not sure if related to I'm using libtorrent 2.0, or if in some way is because of the added trackers. Usually that means no https openssl support, but do have that, plus is for the dht this time strangely.

Anyway, but check if not in the list of 'edit trackers' context-menu.

[nemonein]

It has worked fine until Deluge 2.0.5.
When I add the magnet above to Deluge 2.1.0 sever, the tracker context menu(Edit Trackers) has nothing(Empty). However, if I add a torrent file(*.torrent), I can see all the trackers are on the list.
Actually, the magnet link above is made from Ubuntu torrent file.

Here is another one.

Code: Select all

magnet:?xt=urn:btih:3B5D5THRPUIIA4NXARAE4TTH5WWBVGTQ&dn=KaOS-2022.06-x86_64.iso&xl=3091660800&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce&tr=udp%3A%2F%2Ffosstorrents.com%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce

I also tested this with Transdroid. (Deluge 2 RPC)
Transdroid --> Deluge 2.0.5 : Trackers alive.
Transdroid --> Deluge 2.1.0 : Trackers dead.

[nemonein]

I have tested, and found out something.
If magnet has multiple trackers as well as numbered keys, deluged could not add trackers. Both 2.0.5 and 2.1.0 do not handle trackers.
For example,
This WORKS. (But Only on Deluged 2.0.5)

Code: Select all

magnet:?xt=urn:btih:3B5D5THRPUIIA4NXARAE4TTH5WWBVGTQ&dn=KaOS-2022.06-x86_64.iso&xl=3091660800&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce&tr=udp%3A%2F%2Ffosstorrents.com%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce

This DOES NOT.

Code: Select all

magnet:?xt=urn:btih:3B5D5THRPUIIA4NXARAE4TTH5WWBVGTQ&dn=KaOS-2022.06-x86_64.iso&xl=3091660800&tr.1=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce&tr.2=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce&tr.3=udp%3A%2F%2Ffosstorrents.com%3A6969%2Fannounce&tr.4=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce

Either from Deluge 2.0.5 or Transdroid to Deluge 2.0.5, numberless tracker magnet link DOES add trackers.
To Deluge 2.1.0 always fails adding trackers.
Numbered tracker magnet links DOES NOT add any trackers, when it is added to Deluge 2.1.0.

[mhertz]

Strange, because here it does work, like your example yesterday did, and now all of your examples in fact, on 2.10 and 2.0.5 both, granted on other linux distro but cannot see why would change anyrhing. Just in case I retested with libtorrent 1.2.15 instead of 2.0.6, with same result.

I believe the '&tr.1=' etc args are not in spec, and unofficial extensions, but must be widely used enought so that got incorporated into libtorrent also - I might be wrong though, but checked the spec yesterday because was curious about the new to me '&xl=' arg, but see it's spec-compliant as allowed non-standard user-field.

I guess I can see if I still have my old ubuntu VM and retest tomorrow or something, but honestly this shouldn't change anything - I tested here from official deluge repo package of v2.0.5 as not updated yet here, and made a venv of latest v2.1.0 from pip and git-repo master branch(which is 2.1.0 release branch currently - hmm should have just used 'pip install deluge' obviously don't know why I complicated it needlessly, but still wouldn't change this test though)

[Cas]

What version of libtorrent?

Could you create a Trac issue with details of the problem, thanks

[nemonein]

For Deluge 2.0.5 machine, libtorrent-rasterbar9, 1.1.13-1.1build2, on Ubuntu server 20.04.
For Deluge 2.1.0 machine, libtorrent-rasterbar10, 1.2.16~daily10769+e0dd73971-202206291010~ubuntu20.04.1, on Armbian(Ubuntu 20.04 based).

@mhertz
If you say so, I'll try with VMs.

@cas
I want to try, but I don't know how to open a Trac Issue. (I know about github issues though..)

[Spire]

My version of Deluge/libtorrent is:

Client: Deluge, 2.1.0-0~202206291031~ubuntu18.04.1
Server: Deluge, 2.1.0-0~202206291031~ubuntu20.04.1 / libtorrent-rasterbar, 1.2.16~daily10769+e0dd73971-202206291010~ubuntu20.04.1 on x86_64.

No trackers in Trackers tab or 'Edit Tracker' list.

[mhertz]

First, i'm sorry if sounded like I thought you was wrong - that wasen't my intention and I just meant that I personally couldn't reproduce myself merely, that's all I'll make the report for you if wanted, but want to be able to reproduce first atleast.

I did check your previous post and PPA previously, after posting, so knew you was on libtorrent 1.2.16, which I hadn't tested and wanted test again later in said VM(I read changelog, but nothing stood out).

I just tested this in an ubuntu 21.10 VM, tested from the stable deluge PPA, so deluge 2.1.0 and libtorrent 1.2.16. Result was, hmm, wait a minute, I can reproduce now - sorry testing while writing

Okay, seemingly you are correct in that there is an issue, and I apologize for being somewhat abbrasive possibly, I really do apologize for that and thanks alot for the reporting!

I will make a ticket later when have time, but in doing so then first I will try see if I cannot track the commit down being the culprit to help little in said ticket(probably over my head to actually fix i'm guessing), but regardless, in essence, when adding a magnet and the files are shown before pressing add or okay or whatever was(closed deluge now), then no trackers added on beluge 2.1.0, as you said. If waiting till the files show up to add i.e. prefetch metadata finished fully, then will work also in deluge 2.1.0(and 2.0.5). It doesn't change which used of libtorrent 1.2.15, 1.2.16 and 2.0.6 in my testing here, upon all 4 test link submitted by OP, and neither if numbers added or not to the '&tr=' args.

Thanks again and sorry once more.

Edit: Just saw Spire's post now after posting mine, thanks mate for confirming the issue, appreciated.