Imagine you have almost finished that huge download that was well over 100Mb in size. Any second, it will be completed... or so it would seem. The second the bar should hit 100%, it drops down to 70% or something (not sure if it's a fixed size in Mb, a percentage, or a random number). Instantly, you have just lost a huge chunk of the file, and the download must continue from the 70% mark (or whatever it jumped back to). Since I'm on dial-up, this isn't the sort of thing I want to beta-test. ;) Reproducible: Sometimes Steps to Reproduce: I'm not sure if it's 100% of the time or not, but I know this used to happen to me quite often (not certain if the version was the same or not since it was so long ago), but I'm sure it was an older version. 1. I downloaded a file through d4x via passive FTP. My file system is ext3. 2. Waited until 100% (I assume it made it to 100%... see the above reference URL for further details). 3. Observe as the progress 'may/will' jump back. Actual Results: The last 30% of my download or something was lost. Expected Results: Completed the download, and progressed on to the next download in my list (I was downloading one at a time). I actually have a hunch (I just thought of it) that it may be relating to my download list file. I manually ran File->Save List, and chose a file to save everything to (a process I have always done when using D4X without even thinking about it). That shouldn't be a problem anyway, but it may be the kind of behaviour that triggered it since a lot of people may not use that. I also have 'Save list of downloads every [5] minutes' set. I realize that I haven't provided you much insight, but I'll send you my ~/.ntrc_2/Default.dl and download_list.txt for you to test (provided you have the bandwidth). Good luck! Portage 2.0.50-r6 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.4.26) ================================================================= System uname: 2.4.26 i686 Pentium III (Katmai) Gentoo Base System version 1.4.9 distcc 2.13 i486-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -mcpu=i486 -pipe" CHOST="i486-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -mcpu=i486 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distcc sandbox" GENTOO_MIRRORS="ftp://planetmirror.com/pub/gentoo ftp://mirror.pacific.net.au/linux/Gentoo ftp://ftp.vic.keypoint.com.au http://gentoo.oregonstate.edu http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X Xaw3d aalib acpi alsa apm arts avi berkdb bonobo cdr cjk crypt cups curl dga directfb doc dvb dvd emacs encode esd ethereal evo fbcon flash foomaticdb gb gd gdbm ggi gif gnome gphoto2 gpm gstreamer gtk gtk2 gtkhtml guile imap imlib java jikes joystick jpeg junit kde ladcca lcms leim libg++ libgda libwww mad mbox mcal memlimit mikmod motif mozilla mpeg mpi mule mysql nas ncurses nls nocd odbc oggvorbis opengl oss pam pda pdflib perl plotutils png postgres prelude python qt quicktime readline ruby samba sasl scanner sdl slang slp snmp spell ssl svga tcltk tcpd tetex tiff truetype unicode usb video_cards_sis videos wmf wxwindows x86 xinerama xml xml2 xmms xosd xv zeo zlib"
Created attachment 29944 [details] ~/.ntrc_2/Default.dl
Created attachment 29945 [details] ~/downloads/d4x.list (manually saved list)
I can now confirm that this error doesn't always occur at 100% - it seems it can happen anywhere. And it also seems that this problem only occurs when I am using an extreamly bad connection. Normally via dial-up (but probably not always) it works fine, however when I start downloading another couple of things via BitTorrent which can on occasion cause a D4X FTP connection to time out, the problem starts to occur MUCH more frequently! It just seems that it tries to resume, but doesn't always correctly recall where it was just up to.
Looking at the ChangeLog of d4x 2.5.0rc4 (http://www.krasu.ru/soft/chuchelo/changelog.php3?2.5.0rc4) it is possible that this bug was fixed ("Fixed one probability to weird behavior with FTP"). But before you emerge rc4, I've just filed a bug for getting d4x 2.5.0 final into portage (http://bugs.gentoo.org/show_bug.cgi?id=59741) as it's just come out.
fixed with 2.5.0.
