Opened 3 months ago

Last modified 8 weeks ago

#12573 new Bug report

Directory Listing Failure

Reported by: Development Staff Only Owned by:
Priority: normal Component: FileZilla Client
Keywords: Local File Listing Cc: Development Staff Only
Component version: 3.56.2 Operating system type: Windows
Operating system version: Windows 7 SP 1

Description

I have been running FileZilla for many years with any major issues, but when I upgraded from 3.56.1 to 3.56.2 FileZilla Become unusable in my circumstances. I attempted to find and reinstall 3.56.1 so FileZilla would be viable to me again, but after a long search it seems like it no longer exists on the world wide web in binary install format.
The directory listing window will not display folders nor files, except one just downloaded in the only the root folder of the selected drive.
Can not even navigate drive C. Issue was first noticed on other drive letters, namely, drive B an internal SSD, and drive E an USB 3.0 SSD.
Please provide access to 3.56.1 so that I can use FileZilla. Please correct the issue in next release so I can stay on most recent. Please provide a way to disable auto-updates so I can operate quickly until issues is corrected. Thank you.

Change History (3)

comment:1 by guru-glenn, 8 weeks ago

I'm not sure whether this bug is reporting directory listing failures on client-local or server directories, but I'm seeing a very abbreviated server directory listing for one of my server directories.

I can see them all fine by logging in to the server via Putty, and I can't see any variation in the permissions that would prevent the listing.

Curiously, of the directory and files that are listed, only one of them actually exists on the server, all the ones from the synchronized client listing (which is accurate) also appear in the server listing (those include the one listed that actually exists on the server), and then there are two listed in the server listing that do not exist on either side.

This seems like a quite serious bug, disabling FileZilla when the bug is triggered. I have no idea what triggers it, not all directory listings seem as incomplete as this one I was trying to access today.

FileZilla Client


Version: 3.56.2

Build information:

Compiled for: x86_64-w64-mingw32
Compiled on: x86_64-pc-linux-gnu
Build date: 2021-10-27
Compiled with: x86_64-w64-mingw32-gcc (GCC) 10-win32 20210110
Compiler flags: -O2 -g -Wall -Wextra -Wno-deprecated-copy -ffunction-sections -fdata-sections -Wno-cast-function-type

Linked against:

wxWidgets: 3.0.6
SQLite: 3.35.5
GnuTLS: 3.7.2

Operating system:

Name: Windows 10 (build 19042), 64-bit edition
Version: 10.0
Platform: 64-bit system
CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx avx2 aes pclmulqdq rdrnd bmi bmi2 adx lm
Settings dir: C:\Users\glenn\AppData\Roaming\FileZilla\

comment:2 by guru-glenn, 8 weeks ago

Reinstalling 3.51.1 cured the issue for that directory, so it seems to be a recently introduced bug.

comment:3 by guru-glenn, 8 weeks ago

Oh, I see this bug says "local file listing" issue, so sorry for the noise, I should probably have opened a new bug report, since I had a "server file listing" issue.

Note: See TracTickets for help on using tickets.