Closed GoogleCodeExporter closed 9 years ago
I think the test to see if the interface is working correctly is to set it,
disconnect, reconnect, and see if it's as you set it (files set to not
download). If so, then it's been persisted on Transmission and we can probably
rule the interface out as there's nothing more it can really do.
I know of two reasons this could happen. One (you may have guessed) is if you
set it to unwanted after the file had downloaded. If so, it will stay.
The other likely reason is because of the way bittorrent downloads chunks and
they need to be checksummed. If a chunk overlaps a wanted file and an unwanted
file, it has to download the whole chunk to checksum it, and Transmission will
keep and report the actual downloaded size for the unwanted file. So for small
files like this it's quite normal when you download the larger files. Chunk
size can be different between torrents if I remember rightly.
Does the same happen on other torrents with more regular file sizes, when you
set this straight away?
Original comment by a...@eth0.org.uk
on 9 Dec 2011 at 1:22
ok, it's a "problem" of checksum. It isn't an transmission-remote-gtk error.
Original comment by si...@simonbcn.net
on 9 Dec 2011 at 1:34
Original comment by a...@eth0.org.uk
on 9 Dec 2011 at 1:39
Original issue reported on code.google.com by
si...@simonbcn.net
on 7 Dec 2011 at 2:45