Comment 0 for bug 235326

Version: 0.2.4-0ubuntu1

I had great hopes for today's update in hardy-proposed given this changelog entry " Fix fuse locking and file handle life-cycle issues that were causing frequent crashes." Alas even after a reboot, the gvfs-fuse-daemon is still very unstable:

[ 176.775971] gvfs-fuse-daemo[6134]: segfault at 03000004 eip b7cb2de0 esp b49fe6d4 error 4

which leaves this in /home/gdh/

d????????? ? ? ? ? ? .gvfs

Reproducing the crash is easy. Just copy files up and down from a remote smb share. I can never manage more than 3 up+down copies before it crashes. Simply reading files from the remote share is 'quite reliable' - e.g. I can safely unrar gigabytes of data. It's a mix of read/write that's the killer....

This is purely the gvfs-fuse daemon... if I use Nautilus to perform the same work on smb:// locations, it works flawlessly every time.

I've attached the log of refreshing "/home/gdh/.gvfs/plinth on eddie/gdh", deleting an mpeg, copying an mpeg, and then copying/overwriting the same mpeg (it crashed 3MB into the overwrite)

gdh@gdh-home:/usr/lib/gvfs$ fusermount -u /home/gdh/.gvfs
gdh@gdh-home:/usr/lib/gvfs$ /usr/lib/gvfs/gvfs-fuse-daemon -d /home/gdh/.gvfs 2>/tmp/gvfs.log

Please look into this - it makes the fuse daemon useless :(