Custom Query (2449 matches)


Show under each result:

Results (238 - 240 of 2449)

Ticket Resolution Summary Owner Reporter
#261 Fixed cannot launch Deluge r3201 markybob szabolcs

szabolcs@sin:~/svn/deluge$ deluge no existing Deluge session Starting new Deluge session... deluge_core; using libtorrent 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>


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/", line 64, in init


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

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

File "/usr/share/deluge/plugins/MoveTorrent/", 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

#792 Fixed config --set requires real values, not integer? andar sysadmn

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 should probably be updated to note this.


#2681 Fixed [Win32] Error: "The parameter is incorrect" sylinen

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.

Note: See TracQuery for help on using queries.