gvfs smb write file error: Success

Bug #490176 reported by Nick
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gvfs
Fix Released
Medium
gvfs (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: gvfs

Client: Ubuntu 9.10
Server: Ubuntu 9.04

On the rare occassion for some reason when gvfs needs to write/copy a file to a Samba share it gives the error 'Success' but the file is never actually written. This has happened to me and a colleague a couple of times but there is no exact procedure that will reproduce the error 100%, it just happens when it happens.

Originally it was discovered by opening a file in gedit over smb, then saving the file, which gedit would then give the error. I thought it was a problem with gedit, but when I copied the problem file to my machine via nautilus, changed it, then copied it back via nautilus, nautilus would then produce the same error.

It seems that when this happens to a file, other files on the exact same samba share in the same directory are perfectly ok. A workaround seems to be unmounting the the smb share from the client machine then reconnecting it again.

Revision history for this message
Nick (nick-hhg) wrote :
Revision history for this message
Nick (nick-hhg) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

Changed in gvfs (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
Revision history for this message
Nick (nick-hhg) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for sending the bug to GNOME

Changed in gvfs (Ubuntu):
status: New → Confirmed
status: Confirmed → Triaged
status: Triaged → Confirmed
status: Confirmed → Triaged
status: Triaged → Confirmed
status: Confirmed → Triaged
Revision history for this message
DrC (drcowsley) wrote :

From 493359 - (duplicate sorry!) Ubuntu accessing a file on a Debian-Samba share:
I have seen this when a file is opened by two clients if one tries to update it while the other is still connected. After the initial problem is reported by OpenOffice a subsequent attempt to drag and drop after saving locally can give the error-success contradiction.

I have also had occasional repair cycles when reopening OOo files hosted on my Debian-samba server which might have something to do with this issue...

Changed in gvfs:
status: Unknown → New
Changed in gvfs:
importance: Unknown → Medium
Changed in gvfs:
status: New → Confirmed
Changed in gvfs:
status: Confirmed → Fix Released
Changed in gvfs (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in gvfs (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gvfs - 1.19.2-0ubuntu1

---------------
gvfs (1.19.2-0ubuntu1) trusty; urgency=low

  * New upstream release.
    - smb: Fix "write file error: Success". (LP: #490176)
    - sftp: unable to append to file when using low-level writing
      (LP: #517033)
    - http: Fix uninitialized GError (LP: #1210852)
  * Adjust libsoup-gnome2.4-dev → libsoup2.4-dev build dependency, as per
    upstream configure.ac.
  * Drop 00upstream_mtp_test_updates.patch, included upstream.
 -- Martin Pitt <email address hidden> Mon, 25 Nov 2013 11:05:01 +0100

Changed in gvfs (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.