The bug got fixed in
https://git.gnome.org/browse/gvfs/commit/?id=6032fe495e7de81cb27438b652644b9bd847641e
** Changed in: gvfs (Ubuntu)
Status: Triaged => Fix Committed
--
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/490176
Title:
gvfs smb write file error: Success
Status in GVFS:
Fix Released
Status in “gvfs” package in Ubuntu:
Fix Committed
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/490176/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
