Custom Query (2449 matches)

szabolcs@sin:~/svn/deluge$ deluge no existing Deluge session Starting new Deluge session... deluge_core; using libtorrent 0.13.0.0. Compiled with NDEBUG. Applying preferences Scanning plugin dir /usr/share/deluge/plugins Initialising plugin DesiredRatio Initialising plugin WebSeed Initialising plugin NetworkGraph Initialising plugin TorrentCreator Traceback (most recent call last):

File "/usr/bin/deluge", line 132, in <module>

start_deluge()

File "/usr/bin/deluge", line 115, in start_deluge

interface = deluge.interface.DelugeGTK(config_dir=deluge.common.CONFIG_DIR)

File "/usr/lib/python2.5/site-packages/deluge/interface.py", line 64, in init

self.plugins.scan_for_plugins()

File "/usr/lib/python2.5/site-packages/deluge/plugins.py", line 61, in scan_for_plugins

mod = import(modname, globals(), locals(), [])

File "/usr/share/deluge/plugins/MoveTorrent/init.py", line 133

self.dialogs.show_popup_warning(self.window, "An error occured while trying to move the torrent. Please check your permissions and note that you cannot move a torrent's files to the same directory that they are already stored or move a torrent's files before any of its files have actually been created."))

SyntaxError: invalid syntax

Deluge 1.1.2, running on Ubuntu 8.10.

Using the suggested workaround for changing Deluge settings from cron only works for real values:

$  deluge -u console -a "config --set max_upload_speed 40.0"
 * Configuration value successfully updated.
$  deluge -u console -a "config --set max_upload_speed 40"
 * Configuration value provided has incorrect type.

If this is intended, then the documentation at ​http://dev.deluge-torrent.org/wiki/Scheduling should probably be updated to note this.

Thanks.

Torrents of folders containing more than one file return the error "The parameter is incorrect: SomeDirectory\SomeFilename.xyz" (placeholder names used here) when the storage path of those torrents is a Storage Spaces drive. Torrents of folders with exactly one file in them work correctly, as do single file torrents of any size. Forcing a re-check does not resolve the error. The particular Storage Spaces drive in question is a 9.4TB simple space, running on 4x3TB drives. The same torrents that cause errors work correctly when downloaded to a hardware RAID0 array.