Custom Query (2447 matches)

deluge crashes on startup:

checking for ubuntu...
no existing Deluge session
Starting new Deluge session...
Traceback (most recent call last):
  File "/usr/bin/deluge", line 145, in <module>
    start_deluge()
  File "/usr/bin/deluge", line 128, in start_deluge
    interface = deluge.interface.DelugeGTK()
  File "/usr/lib/python2.5/site-packages/deluge/interface.py", line 54, in __init__
  File "/usr/lib/python2.5/site-packages/deluge/core.py", line 205, in __init__
  File "/usr/share/python2.5/posixpath.py", line 171, in exists
TypeError: coercing to Unicode: need string or buffer, NoneType found

It seems that "prefs.state" causes problems. I can provide whole config directory on request.

WebUI cannot change port settings (in 1.3.5), the settings either do not take effect or only one of the fields gets stored in the config and the other reverts to its default value of 9881 or something.

Looking at "cat ~/.config/deluge/core.conf", I see that the port values are not changed to what I selected unless I use the GTK GUI. Something is not right in the either the JSON RPC or the WebUI-daemon's talking to the daemon.

This will sadly require libtorrent 0.16 in order to work (because that release adds port-reusing and forced ports ​http://code.google.com/p/libtorrent/issues/detail?id=305), but it would be a MAJOR improvement to Deluge, for multiple reasons:

• A static port is best for DHT, because old clients will be lookng for you at your last-known IP and port, which is why clients like uTorrent have a single port setting.

• Your router will be getting requests to old ports and will fill its logs with "UDP blocked" messages, similar to a Denial of Service attack, which can actually crash lower specced routers.

Once Deluge works well with libtorrent 0.16, it really would be worth looking into defaulting to a single, static port, randomly selected on config file generation.

Requesting a single port is easy in 0.16; see the libtorrent bug tracker link above. You just pass in two flags to tell it to re-use the port even if it's in TIME_WAIT state (the state just before it is freed by the system) and to disallow the system from choosing another port at random. It'll also require a small check that says "the only port we wanted is in use? okay, don't start the daemon, instead log a fatal error"