Completed downloads not moving to completed dir in 1.2.3

[Spadge]

Hi

I am noticing strange behaviour in Deluge 1.2.3, whereby completed torrents aren't moving to the completed downloads dir as set up in the configs:

Code: Select all

$ grep -i move ./deluge/core.conf
"move_completed_path": "/home/Shared/BitTorrent/Finished",
"move_completed": true,

and I notice that the "move_completed" rule isn't being passed on to new torrents added via the dir specified in "autoadd_location".

Is this a known issue that other people are seeing, or is it just me?

It could be worth mentioning at this point that I'm using headless FreeBSD7.1 with the web UI, Python 2.6, libtorrent 0.15.

Thanks.

[Spadge]

I have also just noticed that when I tick the 'move completed' tickybox in the web UI per-torrent options tab and click apply, it's not remembering the setting when I go back and look.

[Cas]

and I notice that the "move_completed" rule isn't being passed on to new torrents added via the dir specified in "autoadd_location"

It could be a bug but make sure that the permissions allow files to be created in that directory.

I have also just noticed that when I tick the 'move completed' tickybox in the web UI per-torrent options tab and click apply, it's not remembering the setting when I go back and look.

Yep im seeing that too so it seems to be a bug, you should raise a ticket.

[Spadge]

777 on the entire /home/Shared/ hierarchy, with the Bittorrent dir and its little recursives chowned to the user running deluged.

I have no idea how to raise a ticket.

[Cas]

You can create a new ticket here

[Spadge]

Updating FreeBSD to 7.3 broke the web UI - I will raise a ticket when I get it working again.

Currently, I am trying to get deluge to work with libtorrent-rasterbar-15 installed from ports, rather than having to drop the source into the deluge source dir and have it compile every time I want to build deluge. Because that's the sane way of handling it, right?

This whole thing has turned into a nightmare.