How to: workaround .gvfs transport endpoint is not connected errors

Confirming that a work-around is to manually unmount the ~/.gvfs using:
$ fusermount -u ~/.gvfs

Then close/unmount all opened remote locations in Nautilus and log out and back in, again. This restores the .gvfs-functionality for me.


Works for me in XFCE Thunar too, though I can’t say I ever had this crop up for me under Gnome.

Note: Don’t sudo this command, if you get a permission denied error add your user to the fuse group and try again.

The correct way to add your user to the fuse group is to use the -a(ppend) and -G(roup) switches, giving you:

Warning: Be very careful to include both switches! If you just use the -G switch without the -a switch then the only group you’ll be a member of is the fuse group, which probably isn’t what you want…

If you did accidentally remove yourself from all groups (like I did), then to fix it you’ll need to reboot into a recovery console (you’re not in the sudoers group anymore!) and run the following as root:

The first time you put in your user-account name you are specifying it as the first group your user is a member of (hence the account’s primary group), the rest are the standard Ubuntu groups which you might want to modify as required (i.e. add the vboxusers and any other groups you might be using). You can check the current group membership by running:



Tricksy hobbitses…