*** This bug is a duplicate of bug 212789 ***
https://bugs.launchpad.net/bugs/212789
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
*** This bug is a duplicate of bug 212789 ***
https://bugs.launchpad.net/bugs/212789
Same here
No gvfs-fuse-daemon line in my /etc/mtab
--
gvfs don't stay connected locally after gnome session is restarted
https://bugs.launchpad.net/bugs/214628
You received this bug notification because
*** This bug is a duplicate of bug 212789 ***
https://bugs.launchpad.net/bugs/212789
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
--
gvfs don't stay connected locally after gnome session is
*** This bug is a duplicate of bug 212789 ***
https://bugs.launchpad.net/bugs/212789
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 (Ubuntu)
Importance: Undecided = Low
Assignee:
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
