https://bugs.kde.org/show_bug.cgi?id=356651
Bug ID: 356651
Summary: Moving files onto a smb network share sets the files'
access/modify times to the current date/time.
Product: dolphin
Version: 15.08.3
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Files moved from the local machine onto a smb network share use the current
date/time to set the file's access and modify time, rather than using the times
the file started with. Mounting a smb network share through fstab and using mv
in a terminal keeps the file's original access and modify time.
Reproducible: Always
Steps to Reproduce:
1. Open two Dolphin windows, one in a local btrfs directory, another on a smb
share accessed by going to Network and using Add Network Folder, then browsing
to that new network folder underNetwork.
2. Select a file(s) in a local btrfs directory, and drag onto the dolphin
window showing the smb share.
3. Choose "Move here" when asked.
Actual Results:
The file on the smb network share shows the current date/time as the access and
modify times.
Expected Results:
The file on the smb network share should show the file's original access and
modify times, as the mv command does when moving to a smb mount.
Up to date arch. Note I am NOT talking about the change time, just
access/modify. I could expect this behavior if copying, because there's no way
to give an equivalent to cp's "--preserve" option. Moving from a local
directory to a local directory, in separate dolphin windows, leaves the times
alone, working as I'd expect. Moving from the smb share to a local directory
sets the modify time to the current date/time, but sets a corrupt access time -
I'm getting "2106-02-07 06:28:15.000000000 +0000". Yes, 2106 is not a typo.
And, no, 06:28:15 is not even the time of day it should be, even ignoring the
date.
--
You are receiving this mail because:
You are watching all bug changes.
