I’m seeing this issue in Natty. It is a fresh install, my home directory is encrypted and it has annoying consequences, such as Déjà-Dup failing to backup my home directory because of ~/.gvfs ("Transport endpoint is not connected"). And since the .gvfs folder cannot be browsed to, I can’t even add it to the list of excluded directories in Déjà-Dup (I figured out how to work around this by manually editing the corresponding GConf key though).
osomon@granuja:~$ LANG=C cd .gvfs bash: cd: .gvfs: Transport endpoint is not connected osomon@granuja:~$ mount | grep gvfs gvfs-fuse-daemon on /home/osomon/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=osomon) Should I re-open this bug, or should I file a new one? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/212789 Title: gvfs fuse mount is not functional after logout and subsequent login Status in GVFS: Fix Released Status in “gvfs” package in Ubuntu: Fix Released Status in “gvfs” source package in Hardy: Fix Released Status in “gvfs” package in Debian: New Bug description: Binary package hint: gvfs GVFS-backed mounts are working perfectly on fresh OS boot. After logout and following login every attempt to access $HOME/.gvfs (i.e. with ls or df) results in 'Transport endpoint is not connected' error message. At the same time $HOME/.gvfs is present in /etc/mtab. Also GVFS-mounts are accessible through FUSE when /usr/lib/gvfs/gvfs-fuse- daemon is called with some other directory as argument. Branch of Ubuntu involved is hardy (with all current updates installed), version of gvfs, gvfs-backends, gvfs-fuse and libgvfscommon0 packages is 0.2.2svn20080403-0ubuntu1. TESTCASE: - log into GNOME - browse a network location using nautilus - verify that the location is fuse mounted under .gvfs - close your session - switch to a vt and look to .gvfs or log again and do that, you should get an error saying that .gvfs is not connected - install the update - try those again, now .gvfs is correctly unmounted on logout, and on next login it's still usuable To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/212789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp