Hi,

This usually happens when you finish downloading a torrent, then move it or
delete from the hard-drive (without using qbittorrent to do so).
Therefore, qbittorrent remembers that the torrent is supposed to be
completed but it cannot find all the files on the disk so it asks the users
if he wants to put it back in download (or delete it from the list).

Could you please confirm that the files are indeed still on the hard drive
(all of them), that you did not alter them and that there are located where
qbittorrent first downloaded them?

I do agree that the message is not explicit enough and that I should give
more information and options to the user. I will improve this. I will also
provide more information in properties dialog.


> From: Christian Ohm <[EMAIL PROTECTED]>
> To: Debian Bug Tracking System <[EMAIL PROTECTED]>
> Date: Tue, 12 Aug 2008 12:14:32 +0200
> Subject: Bug#494801: qbittorrent: Moves torrents back and forth between
> "Finished" and "Downloads"
> Package: qbittorrent
> Version: 1.1.0~rc1-2
> Severity: normal
>
> Hello,
>
> When I got on my computer this morning, some of my torrents were
> finished, and for 4 of the 5 I got the following message when switching
> to the "Finished" tab:
>
> "Imcomplete torrent in seeding list"
> "It appears that the state of '<torrentname>' torrent changed from
> 'seeding' to 'downloading'. Would you like to move it back to download
> list?  (otherwise the torrent will simply be deleted)"
>
> So I guess those torrents didn't download all chunks without errors, but
> then why the error message? Why not automatically move them back and try
> to download the erroneous chunks (or not move them to "Finished" in the
> first place? Or the problem is something else, then the message is not
> very descriptive.
>
> Clicking "Yes" then moved them back to the "Downloads" tab (I didn't try
> "No" yet since googling the error message suggests it then deletes the
> torrent including data, which is _not_ what I want), clicking the
> "Downloads" tab moves them to finished... and the cycle starts again.
>
> I didn't notice this behaviour before upgrading to the rc version (which
> I did just yesterdsay), but since qbittorrent isn't very informative
> (compared to Azureus, which lists all kind of stuff, including the
> number of erroneous chunks) I don't know if it wasn't there before or
> just didn't happen to me.
>
> Best regards,
> Christian Ohm
>
> -- System Information:
> Debian Release: lenny/sid
>  APT prefers unstable
>  APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'testing')
> Architecture: i386 (i686)
>
> Kernel: Linux 2.6.22.12-ck1-2 (SMP w/2 CPU cores; PREEMPT)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored:
> LC_ALL set to en_GB.utf8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages qbittorrent depends on:
> ii  libboost-filesystem 1.34.1-11            filesystem operations
> (portable pa
> ii  libboost-thread1.34 1.34.1-11            portable C++ multi-threading
> ii  libc6               2.7-13               GNU C Library: Shared
> libraries
> ii  libcurl3            7.18.2-7             Multi-protocol file transfer
> libra
> ii  libgcc1             1:4.3.1-8            GCC support library
> ii  libmagick++10       7:6.3.7.9.dfsg1-2+b2 C++ API to the ImageMagick
> library
> ii  libqt4-network      4.4.0-4              Qt 4 network module
> ii  libqt4-xml          4.4.0-4              Qt 4 XML module
> ii  libqtcore4          4.4.0-4              Qt 4 core module
> ii  libqtgui4           4.4.0-4              Qt 4 GUI module
> ii  libssl0.9.8         0.9.8g-13            SSL shared libraries
> ii  libstdc++6          4.3.1-8              The GNU Standard C++ Library
> v3
> ii  libtorrent-rasterba 0.13.1-2             C++ bittorrent library by
> Rasterba
> ii  libzzip-0-13        0.13.49-4            library providing read access
> on Z
> ii  python              2.5.2-2              An interactive high-level
> object-o
>
> qbittorrent recommends no packages.
>
> qbittorrent suggests no packages.
>
> -- no debconf information
>
> --
> How many nuclear engineers does it take to change a light bulb ?
>
> Seven:  One to install the new bulb, and six to determine what to do
>        with the old one for the next 10,000 years.
>
>
>
>
>

Reply via email to