Opened 7 weeks ago

Closed 6 weeks ago

#12365 closed Bug report (fixed)

New version of FileZilla does not preserve file timestamps

Reported by: Opticote Owned by:
Priority: high Component: FileZilla Client
Keywords: Timestamp Cc:
Component version: 3.52.0.5 Operating system type: Windows
Operating system version: Windows 10 20.H2

Description

After installing the latest version of FileZilla client, the file timestamp data is no longer preserved on the transferred files. Verified that the option is still set in the transfer options.

Change History (5)

comment:1 by yausername, 7 weeks ago

Have the same problem.
Just updated to 3.52.0.5 and this stopped working for me too. Was working fine before this.
I'm *downloading* files and it's not preserving the timestamp on the downloaded files now.
Running windows 10 too.

Microsoft Windows [Version 10.0.14393]

OS Name: Microsoft Windows 10 Enterprise 2016 LTSB
OS Version: 10.0.14393 N/A Build 14393

Processor(s): 1 Processor(s) Installed.

[01]: Intel64 Family 6 Model 69 Stepping 1 GenuineIntel ~756 Mhz

comment:2 by yausername, 7 weeks ago

Enabling debug log level 3 shows that it's failing with "Could not set modification time." I'll attach full logs if safe to do so.

Here is an excerpt.

2021-01-13 13:31:39 9356 2 Command: get "myfile" "
myshare.myserver.com\billing$\t\myfile"
2021-01-13 13:31:40 9356 2 Command: remote:/reports/myfile => local:
myshare.myserver.com\billing$\t\myfile
2021-01-13 13:31:40 9356 2 Trace: CSftpFileTransferOpData::ParseResponse() in state 4
2021-01-13 13:31:40 9356 2 Trace: Could not set modification time

comment:3 by ABCdatos, 6 weeks ago

Same here at 3.52.0.5 win64.
After downgrading to 3.52.0 it still fails.
After downgrading to 3.51.0 it works fine.

comment:4 by Opticote, 6 weeks ago

Same here - downgrading to 3.51.0 solves the problem

comment:5 by Tim Kosse, 6 weeks ago

Resolution: fixed
Status: newclosed

Please update to 3.52.2

Note: See TracTickets for help on using tickets.