gvfs fuse mount is not functional after logout and subsequent login
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs |
Fix Released
|
High
|
|||
gvfs (Debian) |
New
|
Undecided
|
Unassigned | ||
gvfs (Ubuntu) |
Fix Released
|
High
|
Ubuntu Desktop Bugs | ||
Hardy |
Fix Released
|
High
|
Ubuntu Desktop Bugs |
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/
Branch of Ubuntu involved is hardy (with all current updates installed), version of gvfs, gvfs-backends, gvfs-fuse and libgvfscommon0 packages is 0.2.2svn2008040
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
Related branches
Changed in gvfs: | |
status: | Unknown → New |
Changed in gvfs: | |
assignee: | nobody → desktop-bugs |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in gvfs: | |
milestone: | none → ubuntu-8.04.1 |
milestone: | ubuntu-8.04.1 → none |
Changed in gvfs: | |
status: | New → Fix Released |
Changed in gvfs: | |
milestone: | none → ubuntu-8.04.1 |
Changed in gvfs: | |
importance: | Unknown → High |
I noticed that manual unmounting of $HOME/.gvfs before logout resolves the issue. Probably it should be automated somehow?