Comment 10 for bug 212789

Revision history for this message
Øyvind Stegard (oyvindstegard) wrote :

Here's the very reproducible crash with gvfs-fuse-daemon debug output enabled:

unique: 51, opcode: GETATTR (3), nodeid: 5, insize: 56
unique: 52, opcode: RELEASE (18), nodeid: 5, insize: 64
RELEASE[134851312] flags: 0x8000
unique: 53, opcode: LOOKUP (1), nodeid: 3, insize: 48
LOOKUP /oyvind-home på gandalf/.bashrc

GThread-ERROR **: file /build/buildd/glib2.0-2.16.3/gthread/gthread-posix.c: line 171 (g_mutex_free_posix_impl): error 'Device or resource busy' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...
Aborted

Daemon was started manually as regular user by issuing:
$ /usr/lib/gvfs/gvfs-fuse-daemon -d ~/.gvfs

The mount works fine from within Nautilus itself. Again, triggered by listing the root directory of the mount using Firefox open file dialog through ~/.gvfs. It can also by triggered by the open file dialog of any other Gnome app, it seems. I crashed it using gedit as well (I know gedit can open smb:// natively, but that's beside the point).

Note that doing:
$ ls ~/.gvfs/MOUNTNAME/

works as expected, and the daemon does not crash.