desktop-packages team mailing list archive

[Gaëtan Duchaussois <212789@xxxxxxxxxxxxxxxxxx>]

I have the same behaviour as osomon, pretty annoying. is there any
chance to get it fixed?

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