gvfs-fuse: not able to set smb timestamps

[Chris Cheney]

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

[Bill (bill-redhat-bugs)]

Description of problem:
I have write permision to the share but I can't set the timestamp on files. This causes gthumb image importer to fail.

Version-Release number of selected component (if applicable):
gvfs-0.2.5-1.fc9.i386

How reproducible:
everytime

Steps to Reproduce:
1. Setup a samba share
2. mount the share via gvfs
3. you can use touch in the .gvfsd directory to verify that you don't have permision to set timestamps.

Actual results:
permission denied
the file is still created

Expected results:
it should create/touch the file with the correct timestamp

Additional info:

[Bill (bill-redhat-bugs)]

Ping?

This is still an issue with latest Fedora 10 Beta.

[Tomáš (tom-redhat-bugs-1)]

(server is running samba-3.0.30-0.fc8)

[Tomáš (tom-redhat-bugs-1)]

Can you please test new F10 packages?

http://koji.fedoraproject.org/koji/buildinfo?buildID=68753

[Bill (bill-redhat-bugs)]

Upgraded to new packages and it didn't fix the problem.

I rebooted to make sure.

Is there any network capture or debug mode I could put gvfs in to give you more information?

[Bug (bug-redhat-bugs)]

This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[Chris Cheney (ccheney)]

This appears to be a related upstream bug number but probably isn't the optimal one.

http://bugzilla.gnome.org/show_bug.cgi?id=559586

[Chris Cheney (ccheney)]

Also fails for cp -a. Tomas Bzatek was able to reproduce this issue and is working on the problem. He hopes to have it done in time for us to be able to have the patch for Jaunty.

[Sebastien Bacher (seb128)]

that's not a new issue not a jaunty blocker

[Bug (bug-redhat-bugs)]

This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[Bill (bill-redhat-bugs)]

This bug is still present is Fedora 12.

[Fedora (fedora-redhat-bugs)]

gvfs-1.4.2-1.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/gvfs-1.4.2-1.fc12

[Fedora (fedora-redhat-bugs)]

gvfs-1.4.2-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.

[FP (fabrice-pardo)]

Also affects ubuntu-10.04 lucid
Seems fixed
Cf https://bugzilla.gnome.org/show_bug.cgi?id=559586 comment 4
 There was a bug in gvfs-fuse-daemon, fixed in commit
 59bea4126cf23c575323c59a4cb1123f7cb44e2b. You should be able to touch the file
 on smb mounts now.
http://ftp.gnome.org/pub/GNOME/sources/gvfs/1.5/gvfs-1.5.2.changes
 commit 2009-11-19, release 1.5.2 2010-01-25

[Norbert (nrbrtx)]

It still does not work on Precise and Samba share:
cp --preserve=timestamp ~/some_file ~/.gvfs/some_share/ still sets current date of file, not original.

[Norbert (nrbrtx)]

These bugs are related to attributes too:
https://bugzilla.gnome.org/show_bug.cgi?id=515777
https://bugzilla.gnome.org/show_bug.cgi?id=527339
They have 4-5 year history and they are not fixed.

[Nrbrtx (nrbrtx-redhat-bugs)]

This bug exists in Fedora 18 with gvfs-1.14.2-2.fc18
.
0. I have a Samba share on QNAP NAS and Fedora 18 LiveCD.
1. I mount it from Nautilus, and go to it in Gnome terminal (cd /run/user/1000/gvfs/smb<tab>).
2.1. I copy /etc/issue file (Dec 20 00:21) to it with
"cp -pr /etc/issue ."
I get an error
"cp: clearing permissions for ‘./issue’: Operation not supported"
2.2. I copy /etc/issue file to it with
"cp /etc/issue . --preserve=timestamp"
file is copied and has todays date.
It is an error.

[Nrbrtx (nrbrtx-redhat-bugs)]

I reported a bug to Gnome bugzilla - https://bugzilla.gnome.org/show_bug.cgi?id=693491.

[Norbert (nrbrtx)]

I reported a bug to Gnome bugzilla - https://bugzilla.gnome.org/show_bug.cgi?id=693491
and added comment to Redhat/Fedora bugzilla - https://bugzilla.redhat.com/show_bug.cgi?id=461505.

[Norko (norko-solko)]

User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0

0. I have a Samba share on QNAP NAS.
1. I mount it from Nautilus, and go to it in Gnome terminal (cd
/run/user/linux/gvfs/smb<tab> on OpenSuSe 12.2 LiveCD Gnome).
2.1. I copy /etc/issue file to it with
"cp -pr /etc/issue ."
I get an error
"cp: clearing permissions for ‘./issue’: Operation not supported"
2.2. I copy /etc/issue file to it with
"cp /etc/issue . --preserve=timestamp"
file is copied and has todays date.

This bug exists in Fedora (gvfs-1.14.2-2.fc18,
https://bugzilla.redhat.com/show_bug.cgi?id=461505), Gentoo
(gnome-base/gvfs-1.12.3) and Ubuntu (gvfs-libs 1.12.1-0ubuntu1.1,
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/336761) and has long time
history.

If I mount share with mount -t cifs (old-style) timestamps are OK.
Please fix this bug.

Reproducible: Always

[Norko (norko-solko)]

This bug is reproducible if I mount Samba-shared folder (Samba server is Ubuntu 12.04), not QNAP's.

[Norbert (nrbrtx)]

This bug is reproducible if I mount Samba-shared folder (Samba server is Ubuntu
12.04), not QNAP's.

[Nrbrtx (nrbrtx-redhat-bugs)]

This bug is reproducible if I mount Samba-shared folder (Samba server is Ubuntu
12.04), not QNAP's.

[Niels van Adrichem (nvanadrichem)]

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/

[Ncutler (ncutler)]

openSUSE 12.2 is out of maintenance and the bug is pending upstream at https://bugzilla.gnome.org/show_bug.cgi?id=693491