Opened 6 years ago

Closed 6 years ago

#9291 closed Bug report (fixed)

Auto Update from 3.7.3 to 3.7.4.1 fails

Reported by: Ken Owned by:
Priority: normal Component: FileZilla Client
Keywords: auto update failure Cc:
Component version: Operating system type: Windows
Operating system version: Windows NT 6.1 (build 7601, Service Pack 1)

Description

Opening the client software I was notified that there is an update available.
I clicked the button to install the update and was walked through a series of popups. The client seems to download a file, but in the end I am notified:

Status: Connection established, sending HTTP request
Command: GET http://downloads.sourceforge.net/filezilla/FileZilla_3.7.4.1_win32-setup.exe HTTP/1.1
Error: Disconnected from server: ECONNABORTED - Connection aborted
Error: Disconnected from server
Error: File transfer failed

Attaching a file of screenshots.
Attaching a trace file from the failed update dialog.
Attaching the log file from the session

Below is the system information where the client is installed.

FileZilla Client


Version: 3.7.3

Build information:

Compiled for: i586-pc-mingw32msvc
Compiled on: x86_64-unknown-linux-gnu
Build date: 2013-08-07
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: 3.1.11
SQLite: 3.7.16.2

Operating system:

Name: Windows NT 6.1 (build 7601, Service Pack 1)
Version: 6.1
Platform: 64 bit system

Attachments (8)

1_Update_Available.png (43.8 KB) - added by Ken 6 years ago.
Screenshot showing that there is an update available
2_Update_Dialog.png (55.5 KB) - added by Ken 6 years ago.
Screenshot showing the update dialog
3_FileSave_Dialog.png (91.4 KB) - added by Ken 6 years ago.
Screenshot showing the file save dialog
4_Failed_Update_Dialog.png (76.0 KB) - added by Ken 6 years ago.
Screenshot showing that the update failed
FileZilla_Trace.txt (1.4 KB) - added by Ken 6 years ago.
text listing for the 4_Failed_Update_Dialog.png file
filezilla.log (6.0 KB) - added by Ken 6 years ago.
Logfile from the session
filezilla_03282014.log (4.6 KB) - added by Ken 6 years ago.
Logfile from the session on 3/28/2014
FileZilla_Trace_03282014.txt (1.4 KB) - added by Ken 6 years ago.
text listing from the live session on 3/28/2014

Download all attachments as: .zip

Change History (13)

Changed 6 years ago by Ken

Attachment: 1_Update_Available.png added

Screenshot showing that there is an update available

Changed 6 years ago by Ken

Attachment: 2_Update_Dialog.png added

Screenshot showing the update dialog

Changed 6 years ago by Ken

Attachment: 3_FileSave_Dialog.png added

Screenshot showing the file save dialog

Changed 6 years ago by Ken

Attachment: 4_Failed_Update_Dialog.png added

Screenshot showing that the update failed

Changed 6 years ago by Ken

Attachment: FileZilla_Trace.txt added

text listing for the 4_Failed_Update_Dialog.png file

Changed 6 years ago by Ken

Attachment: filezilla.log added

Logfile from the session

comment:1 Changed 6 years ago by Tim Kosse

Status: newmoreinfo

Does the problem still occur?

Changed 6 years ago by Ken

Attachment: filezilla_03282014.log added

Logfile from the session on 3/28/2014

Changed 6 years ago by Ken

text listing from the live session on 3/28/2014

comment:2 Changed 6 years ago by Ken

Yes the problem still occurs - I have not updated my client version since reporting this bug. Additionally, I attached two log files from today's attempt to upgrade: filezilla_03282014.log and FileZilla_Trace_03282014.txt

comment:3 Changed 6 years ago by Tim Kosse

Can you fetch the file from the log using your web browser? Namely http://downloads.sourceforge.net/filezilla/FileZilla_3.8.0_win32-setup.exe

comment:4 Changed 6 years ago by Ken

That link works fine from a browser - successfully connected to and downloaded to my machine.

comment:5 Changed 6 years ago by Ken

Resolution: fixed
Status: moreinfoclosed

Opened filezilla client today and was prompted to upgrade to 3.8.0

I followed the prompt and the file saved successfully and launched the update process.

It would appear that this issue is resolved.

Note: See TracTickets for help on using tickets.