[solved] Problems in WebUI deluge 1.3.1
Posted: Fri Nov 12, 2010 3:25 pm
Hello,
I've been using deluged 1.2.2 for a long time on one of my embedded platforms (Geode cpu) and now i have upgraded to the latest release.
Since i was using a debian setup before, i switched over to a slimmed ubuntu setup so i could use the deb files from launchpad instead.
The problems i'm looking into is that the WebUI does not update some of the settings i configure in the preference menu.
Each time when i change something (apply/ok) and re-open the menu, the settings are back to default (this is not with ALL the options, some parameters are being stored but not all).
Instead i have now manually updated the core.conf file with the settings i was looking into, but it would be easier to do it through the WebUI.
An example is when i choose the incoming ports the system never saves the changes (it saves the option to not use random ports, but not the filled in ones).
I also have this problem in some other parts of the settings too. This was not in the old release so something must be different.
Also when i click on a torrent and want to change the seed ratio, the system does not keep these settings.
I'm also wondering if i can use the plugins which are shown in the menu? (like the blocklist one)
Does the preference menu activate them or should this be done manually? (can't see anything happening on the WebUI).
My setup:
Ubuntu 10.10 Maverick - casper mode (persistent)
Kernel: Linux ubuntu 2.6.35-22-generic
Latest updates installed
Using Firefox 3.6.12 for WebUI
packages:
ii deluge-common 1.3.1-2~maverick~ppa1 bittorrent client written in Python/PyGTK (common files)
ii deluge-console 1.3.1-2~maverick~ppa1 bittorrent client written in Python/PyGTK (console ui)
ii deluge-web 1.3.1-2~maverick~ppa1 bittorrent client written in Python/PyGTK (web ui)
ii deluge-webui 1.3.1-2~maverick~ppa1 bittorrent client (web ui transitional package)
ii deluged 1.3.1-2~maverick~ppa1 bittorrent client written in Python/PyGTK (daemon)
I didn't really found the bug in the roadmap, so i'm wondering if this is some fault on my side or if this is new.
Thanks
I've been using deluged 1.2.2 for a long time on one of my embedded platforms (Geode cpu) and now i have upgraded to the latest release.
Since i was using a debian setup before, i switched over to a slimmed ubuntu setup so i could use the deb files from launchpad instead.
The problems i'm looking into is that the WebUI does not update some of the settings i configure in the preference menu.
Each time when i change something (apply/ok) and re-open the menu, the settings are back to default (this is not with ALL the options, some parameters are being stored but not all).
Instead i have now manually updated the core.conf file with the settings i was looking into, but it would be easier to do it through the WebUI.
An example is when i choose the incoming ports the system never saves the changes (it saves the option to not use random ports, but not the filled in ones).
I also have this problem in some other parts of the settings too. This was not in the old release so something must be different.
Also when i click on a torrent and want to change the seed ratio, the system does not keep these settings.
I'm also wondering if i can use the plugins which are shown in the menu? (like the blocklist one)
Does the preference menu activate them or should this be done manually? (can't see anything happening on the WebUI).
My setup:
Ubuntu 10.10 Maverick - casper mode (persistent)
Kernel: Linux ubuntu 2.6.35-22-generic
Latest updates installed
Using Firefox 3.6.12 for WebUI
packages:
ii deluge-common 1.3.1-2~maverick~ppa1 bittorrent client written in Python/PyGTK (common files)
ii deluge-console 1.3.1-2~maverick~ppa1 bittorrent client written in Python/PyGTK (console ui)
ii deluge-web 1.3.1-2~maverick~ppa1 bittorrent client written in Python/PyGTK (web ui)
ii deluge-webui 1.3.1-2~maverick~ppa1 bittorrent client (web ui transitional package)
ii deluged 1.3.1-2~maverick~ppa1 bittorrent client written in Python/PyGTK (daemon)
I didn't really found the bug in the roadmap, so i'm wondering if this is some fault on my side or if this is new.
Thanks