desktop-packages team mailing list archive

[Victor Yap <212789@xxxxxxxxxxxxxxxxxx>]

Leveraging off oyvinst's script (comment #14)...

I worked around this bug by doing a little bit more:

# Quick and dirty hack to unmount ~/.gvfs directory on logout.
if test -d "$HOME/.gvfs" ; then
  for f in "$HOME/.gvfs"
  do
    /bin/fusermount -zu "$HOME/.gvfs/$f" 1>/dev/null 2>&1 || true
  done
  /bin/fusermount -zu "$HOME/.gvfs" 1>/dev/null 2>&1 || true
  rmdir "$HOME/.gvfs"
fi

... the script's written from gut-feeling and I didn't actually go
through the steps to troubleshoot any bugs in its logic... >_> I applied
this for Ubuntu 11.10 ... my quickfix intuition is that the .gvfs folder
should be recreated from scratch on session login for the gvfs magic to
work, even after doing the initial unmount... If someone could instead
point out what command(s) are used to do the magic service's
initialization, we might be able to "restart" it within a session
instead of cycling through "logout -> login".

-- 
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