Deluge Forum

Updated from 1.1.9 to 1.2.0-rc1 and had a rainbow of problems.

Daemon was not connectible from the gui client. 127.0.0.1 only listed, localhost did not start.
Deluge config files were installed to a new directory in C:\Users\ (using truncated user account name.)

Switched back to "classic mode."

Reloaded Deluge. Torrents loaded and began seeding as normal for an hour; Before all of them going into an "Error" status.
Deluge would not terminate without use of task manager.
Preference pane would not close when OK was clicked.

Uninstalled, rebooted, re-downloaded and reinstalled.
Uninstall of 1.2.0-rc1 removed components from GTK+ requiring it to be re-installed as well.

Reinstall repeats issues as listed above.
Torrents remain in perpetual Error status at load.

Have rolled back to 1.1.9 (Which is working fine post 1.2.0)

So it looks like I'm not gonna be using 1.2.0 for a bit.

System is Vista 32 with SP2
Stock firewall. Manual scan only AV.

Hmm.. Strange. I didn't really notice any of these issues with my XP vm. I did have an issue with not being able to Quit properly, but I thought I had fixed that.. It at least worked for me in my XP vm.

I haven't exactly done much testing on the Windows build, so I will go back and try to reproduce some of the issues you've mentioned.

I'm on Vista x64 and the daemon doesn't seem to be starting properly, deluged.log has this:
deluge.log is empty.


*edit: running in 'Classic' mode seems to work, going to check if I can still connect to the daemon remotely.

phuzz wrote:I'm on Vista x64 and the daemon doesn't seem to be starting properly, deluged.log has this:

Code: Select all

[ERROR   ] 16:39:59 __init__:1082 Password does not match
Traceback (most recent call last):
  File "deluge\core\rpcserver.py", line 245, in dispatch
  File "deluge\core\authmanager.py", line 93, in authorize
BadLoginError: Password does not match

deluge.log is empty.


*edit: running in 'Classic' mode seems to work, going to check if I can still connect to the daemon remotely.

Yes, I've fixed this error in svn already.