Torrents from watch directory don't start on startup

Bug #758291 reported by Dule Dulic
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qBittorrent
Fix Released
Low
Christophe Dumez

Bug Description

If torrent file is present in the watch directory BEFORE qbittorrent is started, it will get added on startup, but it won't start automatically. It will just read as "Stalled" until it's paused and resumed. I don't think this is expected behaviour, torrent should either start or get added as paused?

Thanks.

Revision history for this message
Christophe Dumez (hydr0g3n) wrote :

I have just tried to reproduce but I couldn't. It starts downloading just fine here.

Here is what I did:
1. Added a watched folder to program preferences
2. Close qBittorrent
3. Add a torrent file to the watched folder
4. Start qBittorrent
-> The torrent is added to the list and starts downloading straight away.

Do you have other settings enabled such as "Add in pause"? What's your version of libtorrent and qBittorrent? What OS are you using?

Changed in qbittorrent:
assignee: nobody → Christophe Dumez (hydr0g3n)
status: New → Incomplete
Revision history for this message
Dule Dulic (karabaja4) wrote :

I did a little more testing and seen that this happenes only on certain private tracker, and only on torrents downloaded from there. Sorry for missing such a detail.

I cannot link the torrent because of the nature of the tracker (private, invite only), but, if you (Christophe Dumez) think that having that *.torrent file could help you resolve this issue I'll send it to you via email...

I don't have "don't start the download automatically". I'm using libtorrent-rasterbar 0.15.5, qbittorrent 2.7.2 and Archlinux rolling release (updated daily).

Revision history for this message
Christophe Dumez (hydr0g3n) wrote :

Does it have anything to do with folder watching? Note that many private trackers are using whitelisting and not all of them whitelist qbittorrent.

Revision history for this message
Dule Dulic (karabaja4) wrote :

Hm, what do you mean?

Yes, it has to do with folder watching because that's the only case when torrent doesn't start.

If it's added to watch directory while qbittorrent is running, or added manually, it starts fine. This particular tracker has qbittorent whitelisted (or rather not blacklisted) for sure.

Revision history for this message
Christophe Dumez (hydr0g3n) wrote :

Hmm, then it might be an initialization problem.

Can I register at this private tracker and test?
Would having the torrent be enough for me to test?

Revision history for this message
Dule Dulic (karabaja4) wrote :

You cannot register without an invitation which I can't send at the moment.

Yes, having a torrent file should be enough because it's tied to my account (as long as you don't abuse it and promise that it won't leave your computer ;)).

Revision history for this message
Christophe Dumez (hydr0g3n) wrote :

Well, then please send me the torrent for me to test (chris <at> qbittorrent.org). If I'm able to reproduce, I may be able to fix it.

To confirm the initialization problem, you can also try to pass the torrent directly as program argument:
qbittorrent path/to/file.torrent

This way, we can make sure it is a race/initialization problem on start up and that it has nothing to do with folder watching.

Revision history for this message
Christophe Dumez (hydr0g3n) wrote :

I have found the problem and fixed in for next bugfix release. Thanks a lot for reporting this. It was indeed an initialization problem: this private tracker blacklists the default port but torrents from watched directories were added before the new port was set.

Changed in qbittorrent:
importance: Undecided → Low
milestone: none → 2.7.3
status: Incomplete → Fix Committed
Changed in qbittorrent:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.