Symlinks on remote filesystems are not threated as links with gvfs. Reading is fine, the link's target file's content is given, but wrting to the symlink self destroys the link and creates a regular file with the link's name and with the new content ( the original file is not touched ) Reproducible: Always Steps to Reproduce: 1.echo "test" > testing.txt 2.ln -s testing.txt symlinktest 3.ls -lah symlinktest lrwxrwxrwx 1 bayi bayi 11 júl 29 02.39 symlinktest -> testing.txt 4. (conenct to localhost over ssh with gvfs) 5. ls .gvfs/.../home/bayi/symlinktest -la -rwx------ 1 bayi bayi 5 júl 29 02.38 .gvfs/.../home/bayi/symlinktest* 6. echo "test2" > .gvfs/.../home/bayi/symlinktest 7 cat testing.txt test 8. cat symlinktest test2 9 ls -lah symlinktest -rwxrwxrwx 1 bayi bayi 6 júl 29 02.41 symlinktest* Actual Results: The file "symlinktest" is not a symlink anymore on the local file system, they are two seperate files now. Expected Results: Symlinks should be kept after writing to them and the original file should be updated.
that sounds like an upstream bug.
(In reply to comment #1) > that sounds like an upstream bug. > i posted the bug on gnome bugzilla too ( 2009.05.30 ). I still got no answer there. Nobody else noticed this bug ?
please post the URL here, and don't change the severity. It's not a crash nor something that will make you loose data (at least not directly), so for us it's not major, thanks (it should probably be for upstream though).
sorry about the severity setting ( the bug was open for days in my browser and as i posted the comment it also changed it back ) here is the URL of the bug@gnome: http://bugzilla.gnome.org/show_bug.cgi?id=584348
I am not sure if we can do much here or should we close this as UPSTREAM :-/
i think we could close this bug here, as this is an upstream bug.
true. Please reopen when there is a solution upstream. We will either try to patch the problem or bump the package to a fixed version.