gvfsd-smb: file content messed when using low-level write utilities (echo)

Bug #517028 reported by potter000
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs
Fix Released
Medium
gvfs (Ubuntu)
Triaged
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gvfs

Configuration:
Ubuntu 9.10 Karmic
GNOME 2.28.0
gvfs 1.4.2 (tried building 1.5.1 - same result)

Steps to reproduce behaviour:
1. Mount a GVFS-SMB share (via smb://someserver/someshare)
2. Open terminal and cd to this share
3. Run commands:
user@host:~/.gvfs/someshare on someserver$ echo 100 > ./test
user@host:~/.gvfs/someshare on someserver$ echo 200 >> ./test
user@host:~/.gvfs/someshare on someserver$ echo 300 >> ./test
user@host:~/.gvfs/someshare on someserver$ echo 400 > ./test
Expected result:
file ./test containing 1 line with "400"
Real result:
user@host:~/.gvfs/someshare on someserver$ cat ./test
400
200
300

Additional information:
Similar behaviour is when using a text editor writing with fopen (e.g. Geany:
http://www.geany.org). When using gedit (which seems to write via
g_file_set_contents), all is OK.
I have already filed a bug to the GNOME team (https://bugzilla.gnome.org/show_bug.cgi?id=608908)
This behaviour is not reproducible with Ubuntu Jaunty (GNOME 2.26, gvfs 1.2.2), all is OK there

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report, but there's no need to open a report on Ubuntu if you already did it on the upstream bug tracker. Linking that report and marking this as triaged, thanks.

Changed in gvfs (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
status: New → Triaged
Changed in gvfs:
status: Unknown → New
Changed in gvfs:
importance: Unknown → Medium
Changed in gvfs:
status: New → Incomplete
Changed in gvfs:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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