Thanks for your reply.
Originally, I was using Double Commander (DC) on Fedora Linux which, I believe, might internally use Gnome GVfs 1.54. Once spotted a regression, I've also tried using GVfs directly with Nautilus (Gnome file manager), with the same effect (no timestamp preserved on copying - listing shows the timestamps correctly).
Initially, I was suspecting DC, but then, I was using quite old version from early 2023 (with regression starting in December 2023). Later, I switched to GVfs, as there are similar reports (namely this and that), but there are much older, I from the files history, I see that up until December 2023, it worked fine (with Double Commander). I wasn't also able to find any particular GVfs update done in the time span between the "it works" and "it doesn't" stated.
As a non-GVfs check, I used cadaver, but I don't know, if it is able to preserve timestamps at all.
Today, I've checked also davfs2 which is a regular Linux kernel driver and everything works fine, as the tools such as DC threat is as regular files, not webdav mounted files. However, it could suggest that TC and TotalCmd-Wifi works as expected :-/.
On the Android side, I use Total Command with "send to".
Just to emphasis, I don't state there is any regression in TotalCmd-Wifi, but I just try to find a reason why it stopped working in my case. I will probably focus on checking the commits in GVfs, especially, if there were no related changes in the TC and/or TotalCmd-Wifi around that period.
Originally, I was using Double Commander (DC) on Fedora Linux which, I believe, might internally use Gnome GVfs 1.54. Once spotted a regression, I've also tried using GVfs directly with Nautilus (Gnome file manager), with the same effect (no timestamp preserved on copying - listing shows the timestamps correctly).
Initially, I was suspecting DC, but then, I was using quite old version from early 2023 (with regression starting in December 2023). Later, I switched to GVfs, as there are similar reports (namely this and that), but there are much older, I from the files history, I see that up until December 2023, it worked fine (with Double Commander). I wasn't also able to find any particular GVfs update done in the time span between the "it works" and "it doesn't" stated.
As a non-GVfs check, I used cadaver, but I don't know, if it is able to preserve timestamps at all.
Today, I've checked also davfs2 which is a regular Linux kernel driver and everything works fine, as the tools such as DC threat is as regular files, not webdav mounted files. However, it could suggest that TC and TotalCmd-Wifi works as expected :-/.
On the Android side, I use Total Command with "send to".
Just to emphasis, I don't state there is any regression in TotalCmd-Wifi, but I just try to find a reason why it stopped working in my case. I will probably focus on checking the commits in GVfs, especially, if there were no related changes in the TC and/or TotalCmd-Wifi around that period.
Statistics: Posted by Szpak — 2024-06-04, 19:05 UTC