desktop-packages team mailing list archive

[Pedro Villavicencio <pedro@xxxxxxxxxx>]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the stable
release - Oneiric Ocelot. It would help us greatly if you could test
with it so we can work on getting it fixed. You can find out more about
it at http://www.ubuntu.com/download . Thanks again and we appreciate
your help.

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Low

** Changed in: nautilus (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/750435

Title:
  Remote file time stamps not updated during copy-paste

Status in “nautilus” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: nautilus

  (Possibly a Samba bug rather than a Nautilus one)

  When copying a file from a window opened on a remote share (using
  Samba) and then pasting into some other (local) location, if the file
  already exists the usual Cancel/Skip/Replace dialog pops up, but the
  timestamps reported by the dialog are not updated unless the window
  (to the remote share) is locally refreshed beforehand, leading the
  user to possibly Skip when he should Replace (when conducting an
  update, for example).  If the file is Replaced, the timestamps are
  updated once the copy is completed, so at least there are no further
  consequences for this bug.

  To demonstrate, copy a file from a remote location to a local one.  In
  the remote location, edit the file to make some trivial changes and
  save it.  Obtain its properties and note the last modification
  timestamp.  Back in the local location, *without refreshing the
  window*, obtain the file's properties.  Note how the last modification
  timestamp has not been updated.  Copy the file again and paste it
  again in the same local location.  Note how the Cancel/Skip/Replace
  dialog reports identical timestamps.

  This caching effect can also cause "Error while copying: No such file
  or directory" if the remote file has been renamed, moved or deleted
  since the window to the remote share was last refreshed.  Also, any
  application or daemon that watches the remote directory for changes
  will likely fail to detect them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/750435/+subscriptions