Deluge
#436 closed bug (Fixed)
Incorrect handling of torrents with some files marked don't download
| Reported by: | ari-_-e | Owned by: | andar |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Core | Version: | 0.9.06 (1.0.0_RC6) |
| Keywords: | Cc: |
Description
Deluge is not handling torrents which have files that are set to "don't download" correctly. When Deluge is started up and one of these torrents has previously been added to Deluge and all of the files not marked "don't download" have finished downloading, it looks like Deluge mistakenly thinks that the torrent is not finished downloading and will start downloading it if it is resumed. If a force recheck is performed on the torrent, Deluge seems to get even more confused, and changes the torrent's progress bar to reflect its perception that the torrent has not finished downloading. However, at that point if I do anything with the priority of the files in that torrent (including setting something to the value it already had), Deluge magically sees the error in its ways and starts seeding the torrent exclusively. Skipping the force recheck step does not appear to solve the problem.
As a side note, the Deluge 0.5 series did something similar to this as well.
Change History (3)
comment:1 Changed 16 years ago by ari-_-e
comment:2 Changed 16 years ago by andar
- Milestone set to 1.0.0
- Resolution set to fixed
- Status changed from new to closed
This has been fixed in svn.
Still happening with rc7...
Also, it's actually easier to "fix" this problem than I thought. All you have to do is take one of the files that's marked don't download, set it to normal, and set it to don't download again. Toggling the state of a file that is set to normal does NOT fix the problem.