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:

sudo usermod -a -G fuse <USER-ACCOUNT-NAME>

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:

usermod -G <USER-ACCOUNT-NAME>,adm,dialout,cdrom,floppy,audio,dip,fuse,video,plugdev,scanner,sambashare,lpadmin,admin <USER-ACCOUNT-NAME>

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:





cat /etc/group | more

Tricksy hobbitses…

4 thoughts on “How to: workaround .gvfs transport endpoint is not connected errors”

  1. Tip: instead of playing with usermod, you can also just edit (as root) the /etc/group file directly and append your username to the appropriate groups.

  2. Why first list the command that WILL delete all your other groups and then mention “oh by the way, this will do this and this”. If someone’s going over this tutorial step by step, that’s exactly what they’re going to do.
    Put the -a version first…

    Anyway, that fixed the issue with thunar for me, so thanks.

    1. You make an excellent point, I have no idea why I put the bad command first – I’ve modified the article accordingly.

      Thanks for your input, and glad it helped.

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.