Opened 9 years ago

Last modified 8 years ago

#5608 new Bug report

resume function does not works if server is not connected

Reported by: willemijns Owned by:
Priority: high Component: FileZilla Client
Keywords: Cc:
Component version: Operating system type:
Operating system version:

Description

win32 version but i think error exist on all OSes.

1) start FZ with 2/3 Mo of the file already on the remote server
on the first screen, i start FZ with "process queue"
the file start at 0 not a 2/3 Mo so resume hasn't work

2) start FZ with 2/3 Mo of the file already on the remote server
on the second screen, i start FZ with "process queue"
the file ask me to resume or not and if i choose resume start at
a 2/3 Mo so resume worked well

"critical" flag is selected coz i was not happy than resume has not worked when i resumed at 95% a file of 4 GB !!!

ps: screenshot files will be added later if i can upload before create the ticket else i will use imageshack

Attachments (2)

resume_does_not_works.PNG (11.6 KB) - added by willemijns 9 years ago.
resume_will_works.PNG (19.6 KB) - added by willemijns 9 years ago.

Download all attachments as: .zip

Change History (3)

Changed 9 years ago by willemijns

Attachment: resume_does_not_works.PNG added

Changed 9 years ago by willemijns

Attachment: resume_will_works.PNG added

comment:1 Changed 8 years ago by Josh Davis

Priority: criticalhigh

Just as a "Me Too", I have this happen every once in a while. It may be related to the remote timestamp not matching, because the file wasn't completed. I'm not 100% sure though.

Considering this isn't a complete failure of the app to run, it shouldn't be "critical", and it shouldn't block new releases. As such, I dropped priority to "High".

Note: See TracTickets for help on using tickets.