Deluge GTK UI doesn't connect to selected daemon automatically on start-up

[narren]

While "Automatically connect to selected host on start-up" option is enabled in connection manager, deluge fails to do that. Client-side log file attached.

[narren]

Client side log file

[andar]

This has been fixed

[boteeka]

It does not seem to be fixed in 1.2.0-rc3. I am using packages from the Deluge Team PPA on Ubuntu 9.10 64bit. Package version: 1.2.0~rc3-5~karmic~ppa2

[andar]

This works for me. Have you tried RC4?

[narren]

It's not working. I've checked that all options are set correctly in connection manager. I have RC4 1.2.0~rc4 from Deluge Team PPA. I'm attaching client-side log (Launched client while daemon is running and quit).

[ankle]

This is still not working for me in trunk - the GTK client doesn't automatically connect to the specified host on start-up, even when "automatically connect to selected host on start-up" is selected.

[Chase]

Yeah, I'm having the same problem with 1.2 RC4. Windows client, connecting to a remote windows daemon.

[andar]

Ok, I think I found the problem.

This should be fixed in [6015].

Thanks for the log.

[ankle]

[6015] only corrects connecting to localhost - it should (and used to) connect automatically to whichever host is selected, even if it's a remote host.

I changed the title of this bug to reflect this - hope that's ok.

[andar]

I've tested this with a remote host and it works.. Can you try the latest revision.. I've made some additional fixes to the connection manager stuff.

[ankle]

Auto-connection seems to be working now, thanks.

There's still something funny going on when stopping a daemon other than the one you're connected to, in the connection manager, but that should probably stay separate from this bug.

[boteeka]

I have Deluge 1.2-rc4 on Ubuntu 9.10 x86_64. Autoconnect still doesn't work. I'm attaching a log.

[boteeka]

GtkUi log

[boteeka]

The hostlist.conf.1.2 doesn't exist, but I have a hostlist.conf.1.1

[boteeka]

I reinstalled Deluge with all of its components (but I kept my configuration files), and now not even the connection manager can be opened to manually connect. If I click on the icon in the toolbar nothing happens. At the moment I can only use Deluge with the classical interface.

If there is anything that I can help with, please let me know.

And sorry about poisoning this ticket with so many replies.

[andar]

This has been fixed in rc5, please use the latest version when reporting bugs.

[boteeka]

It doesn't seem to work in rc5 either.

[narren]

It works for me in RC5.

[boteeka]

I am glad that it works for you, but there clearly has to be some issues remaininig as it is not working for me. I will try to find out what is happening, just give me some clues where to look.

Eventually could you attach your configuration files so I can compare them to my config files to see if there are any significant differences.

[narren]

I'm attaching my log-file and conf-files here. Run "deluge -L debug -l deluge.log". Then you can compare your log with mine.

[boteeka]

Ok, the only significant difference I can find is in the gtkui.conf file, and the difference is that the line:

"autoconnect_host_uri": "http://localclient:49c672058469a4302694dcde141ca7d60445b79a@127.0.0.1:58846", 

is missing from my config file.

I also set Deluge to not use the classic interface, started deluged, then issued the command:

deluge -L debug -l deluge.log

I will attach the deluge.log file, and I also attach the terminal output from that command, as it seems it throws a bunch of errors.

[andar]

Can you try deleting ~/.config/deluge/{hostlist.conf.1.2,gtkui.conf}

Then give it another go.

[boteeka]

I tried your suggestion, but it didn't help. Then I tried deleting the ~/.config/deluge directory which seems to have helped me. Now everything works as expected (at least for now).

I am still with rc5 because the PPA hasn't been updated as of now.