Custom Query (2447 matches)

Setup: 2x Deluged daemons

Symptom:

Adding 2 instances to the connection manager, lets say both are online and you connect to one of the instances. All torrents registrered to this server appear properly and up until this point all is fine.

The error occurs when connecting to the second instance of deluge without first disconnecting the first instance. While the statuses changes, the torrent list are not cleaned up properly.

The proper behaviour would be to first clear torrents when connecting to the new instance.

Hello and thank you for all the hard work and effort invested into creating and maintaining Deluge, it's appreciated.

After updating Deluge from v1.3.12 to v1.3.13, the "Resume All" taskbar icon menu item is non-functional; this menu item is very useful, especially when the "Add all torrents in paused state" option is active. Curiously, "Resume All" does work on torrents after they've been directly started -- but -- any torrent not directly started will not be included in the "Resume All" selection.

The "Pause All" taskbar icon menu option seems to work, but that may only be because I choose to "add all torrents in a paused state", so naturally, I would only pause a torrent again after it had already been directly started. So "Pause All" may seem to work only after it falls within the workaround described above to get the "Resume All" function to work.

Please advise, thank you.

$ grep deluge /var/log/dnf.log
Jul 28 21:48:42 DEBUG ---> Package deluge.noarch 1.3.12-3.fc23 will be upgraded
Jul 28 21:48:42 DEBUG ---> Package deluge.noarch 1.3.13-1.fc23 will be an upgrade

I have noticed this happening several times. A restart of the web service will help for a few days, but then the same behavior occurs. This started to happen about a week ago which seems to relate to the Deluge package update on Arch Linux.

I don't know what logs you need here. I switched back to 1.3.12 for now. I'm happy to help debug this further.