Trackers: Not Contacted Yet

[dimalif]

Please provide the following information

qBittorrent version and Operating System

Windows 10 Pro / 64 & Qbit 4.3.1

What is the problem

I see some added magnets with "Trackers Not Contacted Yet" for hours (see the capture torrent 4, 6, 7 marked as ... active)

No errors logged anywhere.

[dimalif]

Moving # 7 for example at the top of the Queue, seems to solve this. Still strange behaviour.

[FranciscoPombal]

@dimalif

Do you have the 2 "always announce..." settings activated in the advanced settings?

What are your queuing settings?

[dimalif]

@FranciscoPombal

Yes, two always announce in adv settings activated.

As for my queue settings:

[FranciscoPombal]

@dimalif

Well, I would expect those torrents to not announce at all until they move up enough places in the queue to become active. Are those all torrents or are some magnets?

[dimalif]

All of them are magnets. So this is normal behavior? Why they are in ACTIVE category and not queued?

And why such a totally different behavior from all other torrent clients?

Also force to reannounce to tracker(s) doesn't change that. Is that also normal?

[FranciscoPombal]

@dimalif

If you look closely in your screenshot, torrents 4, 6 and 7 are not quite ready yet, they are "Downloading metadata", and thus not yet queued (my question before was redundant, it was easy to see that they are magnets from the start). Pretty sure this is expected behavior.

As for the speed limit exemption in the queue, beware of the intended meaning of the checkboxes, it might not mean what you expect: #12728.

[dimalif]

@FranciscoPombal I hope you (all) are not baptizing bugs into normal behavior.

Personally i find this NOT normal, still i can't do anything about it.

Thanks for the time.

[FranciscoPombal]

Actually, I just checked and torrents downloading metadata should, in fact, also be queued (although it would still make sense to me the other way around, this is a design decision). This is a duplicate of #13961. Try a recent test build as linked in #13961 (comment), since this was recently fixed in #13870, and please report there if it fixes the issue for you.