Custom Query (2449 matches)

1. Start Deluge and observe the "Added" column first show the correct date and time.
2. After a short period the date and time will change to 01/01/70 01:00:00 for all torrents.
3. Deluge will either get stuck on that date and time or revert to the correct information.

Here's a video of the behavior: ​http://sendvid.com/7o4xa8wa

OS X Yosemite 10.0.10.3

1. Configure everything to your liking and quit the thin client.
2. Reopen the thin client and observe none of the settings have been saved.

There is only one fix that I found on the ​official forum:

I was walking through different settings when I noticed that suddenly my torrentview.state file had been created. Finally pinpointed it down to toggling the Label-plugin. Basically, when you untick Label in plugins, the configuration will be saved.

I've also locked the file because width gets added to the rightmost column after a few restarts.

OS X Yosemite 10.10.3

Any paused torrent will not remember it's paused state after a force-recheck, and will resume immediately upon recheck completion.

Steps to reproduce: -Add a torrent -Pause torrent -Begin a force-recheck on torrent

Expected result: Torrent performs a recheck, and returns to paused state.

Observed result: Torrent performs a recheck, and resumes; beginning downloading/seeding immediately.

I've observed in core/torrent.py that Deluge automatically stores the torrent's current state in variable forcing_recheck_paused, requests a force-recheck, and then resumes the torrent. However, this state is not being properly reinstated when on_alert_torrent_checked() in core/torrentmanager.py is called after the recheck is complete.