So, I wanted to contribute to deluge, so I created a ticket, forked the repo on github, and created a pull request. Now what? Do I just wait? I am in no hurry, I just want some closure here. https://github.com/deluge-torrent/deluge/pull/295 https://dev.deluge-torrent.org/ticket/3406 Do I need to do ...

I created a bug for this:

https://dev.deluge-torrent.org/ticket/3407

It's happening on master still. Seems to be related to the change to Wayland - see the bug.

Thanks mate! The problem seems to have returned but at a lower rate of incidence. If as you say the problem is not 'real' then I will just wait on the updates to be pushed through.

OK thanks very much for the attention. All my torrents (750 currently) are on one tracker (the same one) as far as I know so perhaps this problem you mention is not relevant to me.

Anyway, changing to google dns seems to have fixed it for now so I am happy.

Thanks again!

Hmm I had logging enabled but I'm not seeing relevant looking errors. Perhaps the log level is too low?

I have: built off deluge git dev branch (in archlinux) a couple of weeks ago.

I also changed from TalkTalk to google DNS servers 2 hours ago and the problem has not recurred yet, which is some indication it might have been a DNS issue.

It's just cosmetic? That's great! Are you sure it is the same issue though? I am using thin client connection from both linux & windows to a deluge daemon running on archlinux. I don't know what libtorrent 1.2.3 means in unix-lib terms. I see: $ ll /lib/libtorrent* lrwxrwxrwx 1 root root 30 Apr ...

Hi, My torrents have started generating 'no route to host' errors. When I check the daemon often 1/3 of the torrents could be in this state. If I select them all and do 'update tracker' they are ok again. But the problem just recurs some time later. Is there something I can do about this deluge-side...

Nearly all my archive dirs have the year in parentheses at the end of the dir name eg ' (1984)' - but all these have been clipped off in the restored paths! How odd.

I think I sorted it - I changed the group ownership of the archive directories to a user in the 'deluge' group - this appears to be sufficient for deluge to 'remember' where all the torrents were moved to - and now most of them have recovered. The confusing thing was that the torrents had reverted t...