Deluge Forum

Just wanted to say "Thank you, it was quite quick fix". I'm just sorry that I'm quite late with my feedback.

It still won't add any torrent for me.

It added some torrents by using auto add folder, but not all of them.

And when I start it from the commandline it crashes.

Running Windows Vista SP1

PolarZoe wrote:It still won't add any torrent for me.

It added some torrents by using auto add folder, but not all of them.

And when I start it from the commandline it crashes.

Running Windows Vista SP1

Same here. Since the last few RC versions, Deluge will refuse to add torrents. It also does not let me choose what folder to install in.

Just noticed a bug in 1.0.2, windows vista x64 if it matters...
The files tab, when choosing multiple files <shift>, <ctrl> I notice there is an arrow that points down showing the expanded folder, when holding down <shift> or <ctrl> it blinks rapidly and then clicking on any other file collapses the folder making multiple file selection impossible. Simple workaround was to scroll down below the first line all works as expected.

still no fix yet on adding torrents with choose files bug? It still is showing files from other torrent. Appriciate if this could be fixed soon cause it's quite a few steps when trying to select certain files to download in webui. The torrent list just keep on refreshing if I am not quick enough to choose the files within 10secs. Thanks and keep up the good work.

Pause then restart a torrent causes ratio to be reset or changed.

loki wrote:Pause then restart a torrent causes ratio to be reset or changed.

Ah yes, some recent libtorrent change made the way I calculate the ratio not work properly. Rest assured this is only a visual bug.

I'm afraid Deluge 1.0.3 is also not working for me, it will simply not start, the cmd window shows and then disappears and then the deluge window opens but the windows stays white and after that it will say "Not Responding"

P.S: Is there a guide somewhere to enable logging on windows?

Using Windows Vista SP1.

PolarZoe wrote:I'm afraid Deluge 1.0.3 is also not working for me, it will simply not start, the cmd window shows and then disappears and then the deluge window opens but the windows stays white and after that it will say "Not Responding"

P.S: Is there a guide somewhere to enable logging on windows?

Using Windows Vista SP1.

Logging is on by default in windows.. You should see both a deluge.log and deluged.log in your App Data/Roaming/Deluge folder (something like that, I can't remember exactly.)

Thank you andar for pointing out the location.

I am now going to try to find out why Daemon disconnects and becomes unresponsive after several hours of seeding on Windows XP SP3 32 bit with version 1.02 using these log files.

Here is the error in the Deluged.log. Let me know if I have a misconfiguration in the client or if I need to do something to my firewall.

[DEBUG ] 19:10:27 signalmanager:61 Registering http://127.0.0.1:40433 as a signal reciever..
[DEBUG ] 19:10:27 core:922 new_release: 1.0.3
[WARNING ] 19:10:28 signalmanager:75 Unable to emit signal to client <ServerProxy for 127.0.0.1:62854/RPC2>: (10061, 'Connection refused') (1)
[WARNING ] 19:10:30 signalmanager:75 Unable to emit signal to client <ServerProxy for 127.0.0.1:62854/RPC2>: (10061, 'Connection refused') (2)
[WARNING ] 19:10:32 signalmanager:75 Unable to emit signal to client <ServerProxy for 127.0.0.1:62854/RPC2>: (10061, 'Connection refused') (3)
[WARNING ] 19:10:34 signalmanager:75 Unable to emit signal to client <ServerProxy for 127.0.0.1:62854/RPC2>: (10061, 'Connection refused') (4)
[WARNING ] 19:10:36 signalmanager:75 Unable to emit signal to client <ServerProxy for 127.0.0.1:62854/RPC2>: (10061, 'Connection refused') (5)
[WARNING ] 19:10:38 signalmanager:75 Unable to emit signal to client <ServerProxy for 127.0.0.1:62854/RPC2>: (10061, 'Connection refused') (6)
[WARNING ] 19:10:40 signalmanager:75 Unable to emit signal to client <ServerProxy for 127.0.0.1:62854/RPC2>: (10061, 'Connection refused') (7)
[WARNING ] 19:10:42 signalmanager:75 Unable to emit signal to client <ServerProxy for 127.0.0.1:62854/RPC2>: (10061, 'Connection refused') (8)
[WARNING ] 19:10:44 signalmanager:75 Unable to emit signal to client <ServerProxy for 127.0.0.1:62854/RPC2>: (10061, 'Connection refused') (9)
[WARNING ] 19:10:46 signalmanager:75 Unable to emit signal to client <ServerProxy for 127.0.0.1:62854/RPC2>: (10061, 'Connection refused') (10)
[WARNING ] 19:10:48 signalmanager:75 Unable to emit signal to client <ServerProxy for 127.0.0.1:62854/RPC2>: (10061, 'Connection refused') (11)
[WARNING ] 19:10:50 signalmanager:75 Unable to emit signal to client <ServerProxy for 127.0.0.1:62854/RPC2>: (10061, 'Connection refused') (12)