I can confirm that this bug also appears when connecting to a Windows file server. However, in retrospect to #9, at file copy no error is thrown, but it silently overrides the alteration and created timestamps with the current time as in #5.
The problem perseveres both with $gvfs-copy --preserve Test.txt smb://server/share/folderX/Y/Z/. and $cp --preserve=timestamp Test.txt /run/user/1000/gvfs/smb-share\:server\,share\=share/folderX/Y/Z/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/336761 Title: gvfs-fuse: not able to set smb timestamps Status in GVFS: Confirmed Status in “gvfs” package in Ubuntu: Triaged Status in “gvfs” package in Fedora: Unknown Status in “gvfs” package in openSUSE: Confirmed Bug description: Binary package hint: gvfs Apparently this bug was supposed to have been fixed as of gvfs 1.1.1. As of 1.1.6-0ubuntu2 on Jaunty I still see the issue. Steps 1. Mount a remote smb fileshare 2. In the terminal cd to the ~/.gvfs/path/to/mount 3. touch -d "some date" foo Result: touch: settings times of `foo': Operation not supported Could this be some sort of configuration problem on the samba side, note copying files to the samba server works fine for keeping proper dates. This may be an Ubuntu specific issue, somehow(?), since upstream claims this issue was corrected in 1.1.1, or else upstream didn't actually fix the problem like they thought. Chris https://bugzilla.redhat.com/show_bug.cgi?id=479199#c28 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/336761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
