Comment 105 for bug 634554

1) The solution proposed in comment #76 is not a "workaround," it entirely disables the offending software.
2) The only known workaround is in comment #30, which is to kill -9 all fusermount processes and any related mount processes. You may also, if you wish, kill the gvfs-fuse-daemon, which will prevent a recurrence until the next reboot.
3) The only known solution is to disable or remove gvfs-fuse. The problem with disabling it by the method in comment #76 is that it will be re-enabled (and re-broken) when and if an upgrade occurs. Unfortunately, the Fedora packaging gods decided that Totem depends on gvfs-fuse (even though it doesn't), and therefore anytime you upgrade or reinstall Totem, this bug will be back if you use the comment #76 method.
4) The only "acceptable" solution, therefore, is to remove gvfs-fuse entirely (#yum remove gvfs-fuse). This will also remove Totem from your system. See comment #50. Given the choice between excluding Totem (there are many other video players around) vs. a system that hangs every time anyone using Nautilus logs in, I choose to live without Totem.
5) Removing gvfs-fuse entirely means it will not automatically upgrade if and when this bug is fixed. (The solution has been found but not yet incorporated into Fedora; see comment #68 and comment #70.) Thus, subscribe to this bug for news.

> (In reply to comment #79)
> (In reply to comment #77)
> > (In reply to comment #76)
> > > A workaround until someone applies the fixes...
> > >
> > > mv /usr/libexec/gvfsd /usr/libexec/gvfsd.hangs.see-bugzilla-493565
> > >
> > > ... and live without gvfs for the time being.
> > Please do not post such ideas here in bugzilla. I won't be dealing with bugs
> > reporting completely broken desktop just because someone's suggestion. This is
> > not Ubuntu forums...
>
> This bug is almost a year old and effects 3 of my 4 machines daily. Is there a
> work-a-round that is acceptable?