Deluge-gtk, deluged not playing nice after Ubuntu upgrade

[RogueElement]

I'm using deluge-gtk and deluge-console with deluged (v1.3.6) and everything has been working fine for the past couple of years. I recently upgraded to Ubuntu 13.10 and now Deluge freezes up, can't connect to deluged (even when it launched it), or it connects fine to deluged but then stops communicating with it within minutes of launching. I can use deluge-gtk to launch deluged, but then can't shut it down from deluge-gtk or I can't reconnect to the daemon if I relaunch deluge-gtk.

I've tried a fresh installation, changing the auth files in both the profile and /var/lib/deluged/config directories. Nothing seems to work. I haven't noticed any strange errors, but I'm not even sure what to consider as a possible culprit in this situation. Suggestions?

[Cas]

Without more info impossible to say

[RogueElement]

I started having problems almost immediately after upgrading to Ubuntu 13.10. I can start deluged from deluge-gtk and things are fine for a while, then everything just stops working. deluged continues to run, but deluge-gtk is no longer connected to it. If I restart deluge-gtk, it can't connect to the instance of deluged that it started. Error logs show "connection refused" errors, as well as errors telling me that I can't launch more than one instance of deluged using the same configuration. I also use Flexget to automate torrents and Flexget will make a connection to deluge, but will hang indefinitely trying to actually send a torrent to it.

I've tried completely removing and reinstalling Deluge, including deleting the configuration directory and rebuilding it all several times. I've gone back through the setup to make sure I'm not missing anything. This was working flawlessly for years without a problem and only recently has been giving me nothing but grief.

I'm not sure what other information I can provide. It doesn't make sense to me why deluge-gtk will start a daemon and work fine for a few minutes then either lose connectivity with the daemon or not be able to reconnect to the daemon it spawned when the client is restarted. I also don't get why Flexget can connect to the daemon but not be able to do anything more than hang indefinitely. Are there other things I should be checking?

[RogueElement]

I did a complete uninstall and reinstall of deluge-gtk, deluged and deluge-console. I manually deleted any directory I could find related to Deluge. I then configured everything according to the instructions found on this site for running deluge-gtk with the daemon. Everything worked fine for about an hour, then went right back to the exact same problems as before.

When running deluge-gtk from the command line, I see this error "Connection to daemon at 127.0.0.1:58846 failed: Connection was refused by other side: 111: Connection refused." There is no explanation. All the torrents show up in deluge-gtk, but I have no control over them. I can't shut down the daemon from deluge-gtk or interact with it in any way whatsoever.

[Cas]

Is deluged running? What version of libtorrent are you using? How many torrents?

[RogueElement]

Yes, deluged is running. libtorrent-rasterbar7 0.16.11. The torrent count doesn't appear to have any effect on it. It seems to be a problem whether it's a few torrents or many.

[Cas]

Can you try with latest libtorrent from this PPA: https://launchpad.net/~surfernsk/+archi ... es_filter=

[RogueElement]

Tried that. It seems to work a lot better, but still sometimes breaks. The big problem, though, is that the libtorrent from that PPA seems to ignore the proxy settings, which creates an even bigger issue.

Update: I'm assuming it was libtorrent that was ignoring proxy settings. I suppose it could be Deluge, though I didn't seem to have that problem before trying the libtorrent version from the PPA.

[Cas]

Seems unlikely going from 0.16.11 to 0.16.13, you should only be setting one proxy when using 0.16.

[RogueElement]

That's my thinking. I've got each of the proxy types configured with the same settings. I'm not sure why the proxy failed (or is failing).

I tried installing the Deluge PPA version instead of the one in the Ubuntu repositories to see if that would make a difference. It doesn't appear to. Deluge is definitely ignoring the proxy settings. qBittorrent appears to be working just fine, though, using the same version of libtorrent.