Fixed with this update: https://packages.qa.debian.org/d/deluge ... 0355Z.html

Probably fixed with this update: https://packages.qa.debian.org/d/deluge ... 0355Z.html

I'm having this issue as well. I checked and it's not the different users' config problem. It seems to have been introduced in the latest 1.3.10 client. I see the deluged client listening on the port, and I connect from another machine (which is running the 1.3.6 windows client) but I can't connect ...

rm ~/.config/deluge/ipc/deluge-gtk.lock

Easy peasy. It's the lockfile that prevents multiple instances of the gtk interface that didn't get cleaned up because of a hard reboot.

#!/bin/bash # Assumes that newly-finished torrent files are automatically # moved to the SEEDING directory # directory of finished torrents that are seeding SEEDING=/mnt/Vault/Seeding/ # blacklist BLACKLIST=/mnt/Vault/Finished/blacklist.txt # where to move files for archival staging # files can be ...

I would attack this problem at the script level. Make your script check for duplicates before it downloads the torrent.

Cool! As far as I can tell, this issue has been resolved. I will continue to look out for strange behavior and let you know, but I think we're good now, so thank you.

To be honest, I'm not sure how to grab that revision. I can say the problem still exists in 1.1.8. I'll try to figure out how to get the newest revision and let you know how it goes. If you don't hear from me, assume I'm waiting until 1.1.9

Has anything changed that would suggest it would be fixed? If it's not fixed, it will take me an hour to move all my files again.

Alright, some of the backend libraries were updated in whatever Ubuntu repo I use, and now everything works.