[precise] .gvfs fuse mount is not functional after logout and subsequent login

[Jakob Unterwurzacher]

Looks like bug 212789 is back, at least the symptoms are the same.

When I log out, the .gvfs entry stays in /etc/mtab (checked by logging into a console as root).
This seems to be a stale entry, though, as it is not listed in /proc/self/mounts.
Still, when I log back in, any operation on .gvfs gives "Transport endpoint is not connected" (that means non-gnome apps cannot access remote files).

After logout,
# umount --fake (as root)
gets rid of the entry. When logging in again with my user, .gvfs works.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gvfs 1.12.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Sun May 6 18:36:55 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Belfry (es4477)]

Only happens with encrypted homes. My machine is 12.04, amd64.

[Jakob Unterwurzacher (jakobunt)]

I also had an encrypted home. Since I switched to an unencrypted setup the problem is gone. This suggests that ecryptfs is causing it.

[Belfry (es4477)]

A workaround:
1) sudo -i
2) echo session-cleanup-script=/etc/scripts/lightdm-logout.sh>>/etc/lightdm/lightdm.conf
3) mkdir /etc/scripts
4) echo -e '#!/bin/sh\numount $HOME/.gvfs 2>/dev/null\nexit 0'>/etc/scripts/lightdm-logout.sh
5) chmod 755 /etc/scripts/lightdm-logout.sh
6) exit

[Chris Savery (chrissavery)]

I also have encrypted home and had this problem. The workaround appears to work for me. It was preventing me from openign files via sftp mounts with Geany, and now that works ok.

I've been getting all sorts of random crashes on 12.04 so hard to say if something else isn't wrong. It's been very unstable for me.

[Jonathan Reed (jdreed)]

Regarding comment #4, I don't think it's ecryptfs that's causing it, because I'm seeing it periodically on an AFS home directory. This suggests that's more likely to be the usual culprit of "All UI designers assume that $HOME is on a filesystem that supports sockets and FIFOs"