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]
Confirmed since I got the same behaviour.
This is what I got from the command line:
$ ls -la $HOME .gvfs: Noeud final de transport n'est pas connecté
ls: ne peut accéder /home/cors1803/
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]