Package: deluge
Version: 1.2.3+git20100712.0b609bf-1
Severity: normal
Tags: squeeze upstream
Hello,
I've recently upgraded from lenny to squeeze to find that there are several
issues with the new version of deluge. I've taken this text from an article on
my blog, so it is more directed towards users.
When upgrading from lenny's deluge to squeeze's deluge, the new version of the
app is quite different from the previous version. Here are some things to take
into account or that are bothersome:
* when starting for the first time the new version it will take ages to
check (and probably recalculate some checksums); any of the torrents will not
be available until this check is done
A message box or something of that sort would be preferable to announce the
user that this check is one time thing and, if the user has the time, he should
allow it. Otherwise the computer might be stuck with I/O operation rendering it
unusable for some time, especially if there are many torrents available.
* the new version relies on a client-server model which is disabled if you
use the "classic mode" (Edit->Preferences->Interface)
It would be nice if the user is warned of this somehow. Maybe in the suggested
message that warns about the checksums?
* some features available in the old version are not available in the new
version (e.g.: graph for traffic and embedded search function)
I consider this a regression, although not an important one. The graph
functionality was useful to provide a picture of the performance/download and
upload speed in the last few minutes. Sometimes is a useful debugging tool. It
would be nice if upstream provided a module to provide again the functionality.
The search function was really useful. It would be really nice of upstream to
bring it back.
* some features are available as modules, but there are just a few modules;
iirc, the enabled/disabled status of the plugins was not "ported" to the new
version
Not a problem, per se, but in some cases it might be - e.g. blocklists.
* when starting the graphical interface in the new mode, don't use the
"Start daemon" button, use the "Connect" button. If you start the daemon via
the "Start daemon" button the "Connect" button will become "Disconnect"
although the client is NOT connected. Using the "Connect" button directly
solves the problem.
This is actually a functionality problem.
* when choosing the place to save a torrent and trying to set that place as
the default location, deluge will not remember that setting
I consider this also a bug. The interface is misleading and if the
functionality is not available, the button should either be absent or it should
be disabled.
* closing now (with the daemon option) the app will close just the client,
but the server/daemon will remain in the background, unless is explicitly
closed (there is a dedicated menu entry)
I am really unsure that people want this behaviour to be the default one. At
least a warning on close with some „I also want to stop the daemon” would
be nice.
* There is an ugly side panel (on the left side) which, IMHO has no real
function or use, except filtering in the view the active downloads or similar
things
Not a bug per se, but an observation :-)
-- System Information:
Debian Release: 6.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-bpo.5-amd64 (SMP w/2 CPU cores)
Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages deluge depends on:
ii deluge-gtk 1.2.3+git20100712.0b609bf-1 bittorrent client written in Pytho
ii python 2.6.6-3+squeeze5 interactive high-level object-orie
deluge recommends no packages.
deluge suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
