Package: deluge Version: 1.3.1-1 Severity: normal If deluge terminated by some event (f.e. reboot) after start it checking file consistency. But if folder for saved torrents does not exists it keep 'checking' state endlessly.
How to reproduce: 1) Set 'save to' value to some path. 2) Start downloading torrent with folders within torrent 3) Kill deluge by -9 signal 4) remove 'save to' folder (and, probaly) upper directory [not sure] 5) Start deluge Expected behavior: some kind of error mark for 'bad' torrents. Actual: Got endless 'checking' state without progress bar and 30-40% CPU load P.S. I got this state after mount failure for deluge volume, when my /srv/ catalogue was empty instead /srv/deluge/temp-download. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages deluge depends on: ii deluge-gtk 1.3.1-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]
