gvfs smb write file error: Success
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.
Related branches
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 |
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)