Directory listing includes date as part of filename when connected to xbfilezilla

[dingotush]

Using FileZilla 3.2.2.1 to connect to the FileZilla server embedded in XBMC the remote directory listing includes the date as part of the filename making it awkward to navigate the remote tree. This seems to be a new fault that didn't exist in a previous version (though I don't know what version the previous working one was).

For example, using Windows XP ftp client to list directories:

ftp> cd F
250 CWD successful. "/F" is current directory.
ftp> dir
200 Port command successful
150 Opening data channel for directory list.
drwxr-xr-x   1 ftp      ftp             0 Feb 29 19:26 Games
drwxr-xr-x   1 ftp      ftp             0 Feb 29 19:26 Apps
drwxr-xr-x   1 ftp      ftp             0 Feb 29 19:27 Pictures
drwxr-xr-x   1 ftp      ftp             0 Feb 29 19:27 Music
drwxr-xr-x   1 ftp      ftp             0 Feb 29 19:28 Video
drwxr-xr-x   1 ftp      ftp             0 Mar 10 07:41 hddloader
226- Free space: [C:\ 308.97 MB] [E:\ 4.77 GB] [F:\ 138.40 GB] [G:\ 0.00 bytes]

226 Transfer OK
ftp: 378 bytes received in 0.02Seconds 23.63Kbytes/sec.
ftp>

However, in FileZilla's remote tree I see

Filename /              File Type    Last Modified
..
Feb 29 19:26 Apps       File Folder
Feb 29 19:26 Games      File Folder
Feb 29 19:27 Music      File Folder
Feb 29 19:27 Pictures   File Folder
Feb 29 19:28 Video      File Folder
hddloader               File Folder  10/03/2009 07:41:00

The fault only appears to affect filenames with a capital letter at the start, so "hddloader" is reported correctly and is the only one to show a last modified date.

For reference here is the welcome message from the remote machine.

$ ftp xbox
Connected to xbox.private.
220-Welcome to XBOX FileZilla (XBMC)
220-version: XBMC:FileZilla version 1.5.6, (based on FileZilla Server 0.8.8)
220 http://sourceforge.net/projects/xbfilezilla
User (xbox.private:(none)): 

[Tim Kosse]

Enable raw directory listings in the settings and post a complete log from FileZilla.

[Tim Kosse]

Forget my last comment, I figured it out: Invalid date, there's no 2009-02-29, not a leap year.

[dingotush]

Why didn't I spot that - thanks for the prompt response.