deluge 1.20rc1-rc3 problems I encountered

[coffeemonk]

Can you please confirm whether full allocation is really running eventhough you already set it in GTK or configfile?

To check, see if the file you are downloading have the full file size or not.

I checked the individual file sizes, and found that the full-allocation setting was obviously in force. I've now updated to RC3, and removed and manually re-added the problematic torrent, and now full-allocation and file priority settings are working as expected. So, under specific, non-obvious circumstances, these functions are working.

Here's what I think happened in my case:
1) usually, I run with full-alloc set. I did notice at some point after adding the problematic torrent, that this setting in preferences was set to "compact." This not being what I wanted, I switched it back.
2) Since the problematic torrent was likely loaded (from the watch folder) while "compact" allocation was set, it appears the torrent was set up this way, and that subsequent changes to the main allocation preference had no effect.
3) When I was attempting to set file-level priority the preferences pane showed "full" but the torrent itself was set to "compact", thus the priority settings were disabled or non-functional.

This is probably more like a defect, rather than a bug, and it's in the file allocation settings, rather than file priority.

I see two possible ways to correct this:
A) Ensure that the allocation setting is "universal," since it apparently can only be changed in the main program settings or general preferences, and that it affects all torrents in the queue.
B) Add the ability to change the allocation setting (at *least* FROM compact TO full, since the other way around makes somewhat less sense) for each individual torrent in the queue.

Lastly, there's currently no way (that I've found) to see what the current allocation setting is for a specific torrent. Probably something should be added to the interface(s) to indicate this.

[abubin]

how did you change to full alloc through config file? I do not have gui installed, so I can use gui to change allocation.

What I did of changing compact allocation to false in config file does not seems to work.

EDIT:

ok, I just remembered I can use deluge-console. So, I tried going into deluge-console for the first time after few years of using deluge. Manage to eventually set the compact_allocation to false. Then restarted deluge. Then removed the torrent and add them again viola!! Full allocation seems to be working as I can change priority without it going back to normal.

Webui is also showing FULL.

[thesoul]

Hi, sorry to bump up this thread, but this was the one with more information available about the problem.

So, does anyone got success on fixing those problems?
I just tried the rc4 and notice the problems on the webui, like:
- Can't change the file allocation to FULL;
- Because of the previous problem, I can't change file priority;
- Can't change speeds on the bottom bar;

I'm running a Linux distribution I've installed in the beginning of the year (Linux Mint, apparently a Ubuntu Intrepid) and did a complete apt-get upgrade that took all day to complete, in order to install the 1.2.0rc.

I believe that he 1.1.9 version I've installed was from the PPA's Intrepid repository.
When I was updating, I first tried to install 1.2.0 from PPA's jaunty (since there's no Intrepid), but didn't work, so I installed from the .tar.gz and worked, then ever since I'm using the .tar.gz.

This time I also tried to do

Code: Select all

sudo rm -r /usr/lib/python2.5/site-packages/deluge*
sudo rm -r /usr/bin/deluge*

Before compiling and installing, but apparently it was all the same.

I also tried the deluge-console to change the config, but now, if I type a "config --help" or "config -set compact-allocation false" it closes the consoles and I get back to terminal.

If anyone needs more info, just ask explaining what I should do (since I'm not really familiarized with Linux), just don't ask me to format and reinstall the complete system with a newer distribution, because it took me some time to set up everything on this machine, to work as a "headless" internet caching (and downloading box)...

Thanks,

PS: I really liked the 1.2.0 webui and don't want to get back to the 1.1.9 one...

[avsess]

In advance I am sorry for the bad English. A problem following: on a server (gentoo) the demon and webinterface works. I come from other computer (Windows 7) on webinterface and I try to add a torrent-file from a local folder. And I receive a path (without dependence from a folder) c:\fake_path\torrentname. Accordingly I can not add torrent. The version 1.2-rc3. In version 1.1.9 there were some kinds webinterface, and there too there were problems with ajax. Why have cleaned the others? And how to solve my problem?

[igor_mk]

Hello,

I have the same problems, I guess the biggest problem is that the move completed torrents, and others are grayed out, and also the full allocation problem. I tried using deluge-console to set the compact-allocation value to false, it worked, but after restart of the daemon and deluge-web client it turned back to it's old state.

I'm using Ubuntu 8.04 server 32bit, I installed deluge via PPA.

Did someone managed to fix these problems? Thanks.

[thesoul]

As a workaround, I installed Deluge in my main PC and used it as a "thin client" to connect to the daemon on the linux machine... not the ideal fix, but it's working for me.

This way, I can change the allocation settings, but if I go to the webui > settings, the compact allocation is set as default again and I have to change through the thin client back to full allocation.


But hoping to see those problems fixed, to go back and use only the webui.