Deluge not resuming queued torrents after scheduled stop

[jorobe]

After the scheduler stops and then starts, all queued torrents then show as paused. But they will usually still start when the queue changes.
This has happened with deluge versions 1.3.5 and 1.3.6 and also libtorrent versions 0.16.3.0 and 0.16.7.0. I've tried running deluged as different users and still the same.
Deluged is running headless on 3.5.0-25-generic #39-Ubuntu. The client in running on windows, and no there are no version miss-matches.
Anyone have any initial ideas or do I have to enable logging, post logs, etc. etc. etc...?

[Cas]

sounds like this issue: http://dev.deluge-torrent.org/ticket/1330

[jorobe]

It does sound similar, except that for me when the scheduler goes into red it pauses all of the torrents, when it moves back into a green zone it restarts the previously active torrents but any that were queued (both seeding and downloading) show as paused. When the queue moves it usually treats those torrents correctly, but a couple times when testing I've had to select the torrent, pause and then resume it to get it started again. That ticket is also 3 years old, and I believe the problem appeared for me when I upgraded to quantal.
I took the tip though, about using the slow setting and setting active torrents to zero. It seems to have the desired effect and I don't use separate full, slow and stop modes anyway.
So thanks, it should work fine for me using slow, but the stop mode problem persists.

[jorobe]

ok that isn't working out too well, any torrents I have unmarked as auto-managed continue even when active number of torrents are set to zero, and I use the management system quite extensively.
I also found this problem exists even if deluged and deluge are on the same system!
So what am I the only one experiencing this?