Custom Query (8169 matches)


Show under each result:

Results (460 - 462 of 8169)

Ticket Resolution Summary Owner Reporter
#466 item not transalated in pref panel anonymous

the panel layout option in the pref is blank in the tree and is not translated in french

see the image

#467 corrupted xml file anonymous
  1. Started filezilla v2.1.8 when the hard-disk was full.
  2. Got a message "hard disk full"
  3. Cleaned some disk space
  4. Repeatedly getting the following message at startup:


Error, can't parse 'FileZilla.xml', the file may be corrupt. For this session, the registry will be used to store the settings.


  1. All config data was clear . FileZilla.xml is of size
  2. Even after adding new configuration.
#468 File listing and long username's jimpower


Easy to reproduce bug, tested on FileZilla 2.1.7 and 2.2

When you try to LIST the content of a remote directory who has long username (more than the standard 8 characters), some files won't appear when their size is to big.

Example :

Owner | Group | Size (in Bytes) | Filename | Result

root other 3842072 trtContinu.dup : Listed streamserve streamserve 3842072 trtContinu.dup : NOT Listed streamserve streamserve 842072 trtContinu.dup : Listed

I haven't try to exactly determine what was the limit of username's lenght which cause the bug but I think it would not be complicated to resolve.

Hope explanations are clear enough ;)


Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.