Reseeding in Deluge 2.0.3

[paraguas]

Hi.

I'm trying to reseed a torrent in Deluge 2.0.3. I copied the files to the download directory, added the torrent in paused state and did a manual recheck. Torrent is shown as completed in the GUI, so I started it. It connect to the tracker fine and seems to be seeding, but there's a catch. In the tracker web page, that torrent is shown as leeching (with 0% completion), not as seeding. I replicated this with a torrent from a different tracker to see if it was a tracker issue and the exact same thing happened.

Could this be a bug in Deluge or I'm missing something?

Thanks for your assistance.

[paraguas]

I've been monitoring the communication with the tracker with Wireshark and I see that Deluge is sending announces with the parameter 'left' with a value of the size of the torrent instead zero (as one would expect for a torrent listed as completed and seeding).

I've been checking torrents.state, to find is_finished set to true, as expected.

Also I've checked torrents.fastresume, to find that completed_time is not zero and has the time of the hash check finish. The field total_downloaded is set to zero. I'm not sure if this should be the size of the torrent for a torrent that is being reseeded.

Anyway it looks like Deluge gets confused somehow.

[paraguas]

This has been accepted as a libtorrent bug and is set to be fixed in version 1.2.2.