Bug 513050 - GvFs - problems to open home directory.
Summary: GvFs - problems to open home directory.
Keywords:
Status: CLOSED DUPLICATE of bug 493565
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 11
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-21 18:57 UTC by virus1057
Modified: 2015-03-03 22:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-22 08:13:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
ps -Al (9.87 KB, text/plain)
2009-07-21 18:57 UTC, virus1057
no flags Details

Description virus1057 2009-07-21 18:57:08 UTC
Created attachment 354555 [details]
ps -Al

Description of problem:

Fedora 11.
Desktop Gnome.

the system appears properly,
but, when I use nautilus, it doesn't open my home directory. It seems that nautilus is still waiting and busy.
I use  the "ls" command in the gnome-terminal, but when I use 'ls -a', the terminal seem to be lock.

I create new user and new home, the problem remains.

I change gnome -> KDE, the problem remains.

I use another FileManger as MC, the problem remains.


Version-Release number of selected component (if applicable):

kernel 2.6.29.5-191.fc11.i686.PAE

gvfs-1.2.3-7.fc11.i586
gvfs-fuse-1.2.3-7.fc11.i586
gvfs-archive-1.2.3-7.fc11.i586
gvfs-obexftp-1.2.3-7.fc11.i586
gvfs-smb-1.2.3-7.fc11.i586
gvfs-gphoto2-1.2.3-7.fc11.i586
glib2-2.20.3-1.fc11.i586
glib-1.2.10-32.fc11.i586



How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
the processes gvfsd, dbus, are active.

Comment 1 virus1057 2009-07-21 19:08:36 UTC
the line :
gvfs-fuse-daemon /home/user/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev,user=user 0 0
is not present in /etc/mtab

Comment 2 Tomáš Bžatek 2009-07-22 08:13:56 UTC

*** This bug has been marked as a duplicate of bug 493565 ***


Note You need to log in before you can comment on or make changes to this bug.