Public bug reported: 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: u...@host:~/.gvfs/someshare on someserver$ echo 100 > ./test u...@host:~/.gvfs/someshare on someserver$ echo 200 >> ./test u...@host:~/.gvfs/someshare on someserver$ echo 300 >> ./test u...@host:~/.gvfs/someshare on someserver$ echo 400 > ./test Expected result: file ./test containing 1 line with "400" Real result: u...@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 ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: gnome gvfs karmic samba smb -- gvfsd-smb: file content messed when using low-level write utilities (echo) https://bugs.launchpad.net/bugs/517028 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
