Opened 8 years ago

Closed 8 years ago

#11001 closed Bug report (fixed)

fzsftp quit unexpectedly.

Reported by: C Owned by:
Priority: normal Component: FileZilla Client
Keywords: fzsftp quit unexpectedly. Cc:
Component version: 3.22.0 Operating system type: OS X
Operating system version: 10.9.5

Description

Just updated to 3.22.0 and fz client opens as usual but when I try to connect I get this message: "fzsftp quit unexpectedly." and connection fails.

It worked perfectly before.

Attachments (1)

filezilla.log (4.4 KB ) - added by C 8 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 by Tim Kosse, 8 years ago

Status: newmoreinfo

Please set the debug log level to 4 on the debug page in the settings dialog of FileZilla, then attempt to connect to the server and post the resulting log.

comment:2 by C, 8 years ago

Status: moreinfonew

Unfortunately the debug log reporting seems to have a problem too. I quit and restart and the debug level has reverted to zero and no debug file is produced.

comment:3 by Tim Kosse, 8 years ago

Status: newmoreinfo

After setting the debug level don't restart. Set it, then try to connect.

by C, 8 years ago

Attachment: filezilla.log added

comment:4 by C, 8 years ago

Status: moreinfonew

worked this time - log attached.

comment:5 by Tim Kosse, 8 years ago

Looks like fzsftp just dies. This makes no sense at all, its code hasn't change between 3.21.0 and 3.22.0 in any way. The only thing that has changes is the version of Xcode.

Please try this:

Open a Terminal and enter the following command, replace the path, username and host to match your machine:

/Applications/FileZilla.app/Contents/MacOS/fzsftp -v username@…

When it prints a line ending in '@', enter '-1-' (without the quotes), when it prints a line ending in '?', enter '-0-'. Enter your password when prompted.

What's the result?

comment:6 by Tim Kosse, 8 years ago

Status: newmoreinfo

comment:8 by C, 8 years ago

Status: moreinfonew

Great! Thanks - that fixed it! Well done!

comment:9 by Stefan Norman, 8 years ago

+1 Had the same problem. Test build fixed it. Thanks!

comment:10 by Tim Kosse, 8 years ago

Resolution: fixed
Status: newclosed

Fixed in 3.22.1

Note: See TracTickets for help on using tickets.