I had run with debug output, but I have not saved it, because it revealed no relevant information.

The application crashes when adding certain magnet links. I have been running as a daemon, controlled remotely. The crash manifests as a segmentation fault (core dump). Following is the stack trace from gdb: #0 0x00007ffff5a52bd5 in boost::python::objects::polymorphic_id_generator<libtorrent::alert>...

Whether running as a daemon or graphical interface, the application hangs on startup. Following is the debug output (some path names redacted): $ deluge --config $(pwd) -L debug 23:52:58 [INFO ][deluge.configmanager:49 ] Setting config directory to: <config_path> 23:52:58 [DEBUG ][deluge.configmanag...

your issue with multi-tracker torrents indeed can be overcome with ltconfig I am trying to configure the plugin, as suggested. The interface for the plugin has two check boxes for the named options, shown on either side of the option names. I believe the left box enables overriding the application ...

I am trying to migrate from another client to Deluge. Part of the process has been to capture the magnet links of torrents currently managed by the previous client, and then to add them to Deluge. The torrents successfully populate the Deluge instance, but communication with trackers has presented a...