Custom Query (7948 matches)

When transferring a whole directory to an empty directory on a 1GB/sec network, I will randomly get the dialog box to confirm overwrite of the existing file. (Remember that the target directory was empty originally.) I believe there is some kind of logic problem in the way the two copy threads decide which is the next file to copy. I notice this most when one thread is working on a large file and the second thread is working on a bunch of very short files.

Thanks in advance, Brian Bulaw

FileZilla Client

Version: 3.5.3

Build information:

Compiled for: i586-pc-mingw32msvc Compiled on: x86_64-unknown-linux-gnu Build date: 2012-01-08 Compiled with: i586-mingw32msvc-gcc (GCC) 4.2.1-sjlj (mingw32-2) Compiler flags: -g -O2 -Wall -g -fexceptions

Linked against:

wxWidgets: 2.8.12 GnuTLS: 2.10.4

Operating system:

Name: Windows XP (build 2600, Service Pack 3) Version: 5.1 Platform: 32 bit system

After upgrading to 2.2.12a, file listings are now inconsistent. I'm using explicit FTPS (FTP with TLS) and after I connect, the directory listing I receive is incomplete. If I refresh the listing, I get a different result almost every time I do so.

For example, I should see 5 directories off of the root of the FTP site, however on first connect, I'll see some random number of them like 3, 2, or 4. If I refresh the list, one of the other directories may pop-up (or mabye not), or one may disappear from the listing. As I said, it seems almost random.

As an additional FYI, this is against Ipswitch WS_FTP Server 5.04 Hotfix 1 (which was working fine with FileZilla 2.2.11; I think with exception to the recursive delete problem I logged in this bug forum long ago and I think has not yet been fixed).

I've tried downloading FileZilla from two separate mirrors (Phoenix, AZ and Kent, UK). In both instances, my virus checker (AVG Free) doesn't allow me to finish the download.

The virus is apparently called: Trojan horse Downloader.Istbar.8.K

I don't know if this is the SourceForge's problem or yours, but since it's happening on at least two different mirrors, I'm guessing the problem is from the upload. Please check, as I would like to download the crash fix soon.