gvfs don't stay connected "locally" after gnome session is restarted

Bug #214628 reported by FredBezies on 2008-04-09
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gvfs

I hoped this is not a known bug.

I'm seeing a strange behavior of gvfs.

When I start a Gnome session after my ubuntu is freshly booted, gvfs is working without any problem. But if I close an open a new session, gvfs is not working anymore, telling me if I type df -h in a console :

"$ df -h
[good datas]
df: `/home/fred/.gvfs': Noeud final de transport n'est pas connecté"

df `/home/fred/.gvfs': Final transport node is not connected ("simple translation" of error message)

My uname :

"$ uname -a
Linux fred-laptop 2.6.24-15-generic #1 SMP Mon Apr 7 16:37:53 UTC 2008 x86_64 GNU/Linux"

I'm using an up-to-date (at least until I made this bug report) ubuntu Hardy Heron AMD 64 bits.

Confirmed since I got the same behaviour.

This is what I got from the command line:

$ ls -la $HOME
ls: ne peut accéder /home/cors1803/.gvfs: Noeud final de transport n'est pas connecté
total 340
drwxr-x--- 55 cors1803 cors1803 4096 2008-04-10 15:40 .
drwxr-xr-x 3 root root 4096 2008-03-27 10:28 ..
-rw-r----- 1 cors1803 cors1803 452 2008-03-26 14:47 .bash_aliases
-rw------- 1 cors1803 cors1803 18395 2008-04-10 15:41 .bash_history
-rw-r----- 1 cors1803 cors1803 220 2008-03-27 10:28 .bash_logout
-rw-r----- 1 cors1803 cors1803 2322 2008-03-27 12:54 .bashrc
[some valid entries here]
d????????? ? ? ? ? ? .gvfs
[some more valid entries]

Changed in gvfs:
status: New → Confirmed
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in gvfs:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: Confirmed → Invalid
Anakin Starkiller (sunrider) wrote :

Same problem here.
The line in /etc/mtab may be responsible for this issue :
gvfs-fuse-daemon ~/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev 0 0

Laurent Dinclaux (dreadlox) wrote :

Same here

No gvfs-fuse-daemon line in my /etc/mtab

fabse (fabian-aly) wrote :

I got the same behaviour here...

the line:
gvfs-fuse-daemon on /home/fabian/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=fabian)

was missing in my mtab

I added the line:

gvfs-fuse-daemon on /home/fabian/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=fabian)

to my fstab

I deleted ~/.gvfs/ and rebooted.

That fixed it for me...

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers