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?
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 fuse-daemon on /home/osomon/.gvfs type fuse.gvfs- fuse-daemon (rw,nosuid, nodev,user= osomon)
gvfs-
Should I re-open this bug, or should I file a new one?