gvfs-fuse-daemon process not killed on logout and not re-used on login

[Øyvind Stegard]

Binary package hint: gvfs-fuse

I'm getting lots of useless gvfs-fuse-daemon processes hanging around after a few logout/login cycles. Funny thing is that it used to be a problem that this daemon died a little too often, now it's very much the opposite :). Anyways, I *think* it started after the last gvfs-update, but I am not sure of that.

Here's what I've got installed (hardy-proposed enabled):
$ dpkg -l '*gvfs*' | grep ii
ii gvfs 0.2.5-0ubuntu2 userspace virtual filesystem - server
ii gvfs-backends 0.2.5-0ubuntu2 userspace virtual filesystem - backends
ii gvfs-bin 0.2.5-0ubuntu2 userspace virtual filesystem - binaries
ii gvfs-fuse 0.2.5-0ubuntu2 userspace virtual filesystem - fuse server
ii libgvfscommon0 0.2.5-0ubuntu2 userspace virtual filesystem - library

And here's the result after three login/logout cycles:
$ ps -ef | grep gvfs-fuse
oyvind 6511 1 0 03:24 ? 00:00:00 /usr/lib/gvfs//gvfs-fuse-daemon /home/oyvind/.gvfs
oyvind 10685 1 0 04:43 ? 00:00:00 /usr/lib/gvfs//gvfs-fuse-daemon /home/oyvind/.gvfs
oyvind 11139 1 0 04:44 ? 00:00:00 /usr/lib/gvfs//gvfs-fuse-daemon /home/oyvind/.gvfs
oyvind 11770 11336 0 04:52 pts/0 00:00:00 grep gvfs-fuse

The problem happens on two entirely different machines: this laptop and a completely new and clean Ubuntu 8.04.1 install with hardy-proposed enabled and a clean home directory.

[Sebastien Bacher (seb128)]

thank you for your bug report. does downgrading to the hardy-updates version fixes your issue?

[Gert Kulyk (gkulyk)]

I can confirm this. It happened for me with all hardy gvfs releases so far (hardy, hardy-proposed, hardy-updates). While I'm using mostly a single-user environment, and therefore it is not that severe for me, I think on machines that are used by more than one person without rebooting this may cause troubles on the longer run. Any hint how to debug this properly?

[Chris Coulson (chrisccoulson)]

I don't think this is a GVFS problem. This happens with other processes after a user has logged off too, and is reported in bug 236210

[Gert Kulyk (gkulyk)]

For me everything shuts down cleanly except gvfs-fuse-daemon. But you're right, that bug 236210 may be related. See also http://mail.gnome.org/archives/gvfs-list/2008-July/msg00006.html and followups.

[Øyvind Stegard (oyvindstegard)]

Downgrading to:

$ ls -1 *gvfs*.deb
gvfs_0.2.5-0ubuntu1_i386.deb
gvfs-backends_0.2.5-0ubuntu1_i386.deb
gvfs-bin_0.2.5-0ubuntu1_i386.deb
gvfs-fuse_0.2.5-0ubuntu1_i386.deb
libgvfscommon0_0.2.5-0ubuntu1_i386.deb

does not solve the problem of remaining gvfs-fuse-daemon processes after logout. Also, the daemons need to be terminated (kill -9), regular kill does not work. So I guess this problem has crept in someplace else, and that I didn't notice it until recently..

[Gert Kulyk (gkulyk)]

I've been playing around with some patches posted (and now commited to trunk) in gnome-bugzilla. Seems like the patch attached to http://bugzilla.gnome.org/show_bug.cgi?id=543552 (http://bugzilla.gnome.org/attachment.cgi?id=115477) is not only working around a crasher, but also closing gvfs-fuse-daemon on session-logout properly. Can someone else confirm this?

[Sebastien Bacher (seb128)]

bug #235698 is already tracking the issue you listed

[Sebastien Bacher (seb128)]

the issue should be fixed using the current intrepid version and the hardy updates, closing the bug, reopen if you still get the issue though