Description of problem:
As an end user, if I run "df", I see the following:
df: `/root/.gvfs': Permission denied
If I run df as root, I see the following:
df: `/root/.gvfs': Transport endpoint is not connected
I am not logged in as root, but I did login to GNOME as root once. Since then,
the above appears. This may not be a coreutils issue, but a gvfs one.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Login to GNOME as root
2. Logout and login to GNOME as end-user
3. run df
df: `/root/.gvfs': Permission denied
An ls -al /root | grep gvfs shows the following:
ls: cannot access /root/.gvfs: Transport endpoint is not connected
d????????? ? ? ? ? ? .gvfs
I mounted a CIFS volume as root. Now all of my users see both the
"/home/[username]/.gvfs: Transport endpoint is not connected" and the
"/root/.gvfs: Permission denied" messages when they run df. Unmounting the
volume doesn't make the warnings stop.
FWIW, my root account doesn't show any warning messages from df. It does show a
line beginning with "gvfs-fuse-daemon", though.
Also, the mounted volume icon that used to show up on my users' desktops with
F-8 doesn't show up with F-9. The volume is mounted and readable by the users
from the command line. Is that another manifestation of the same bug or
Here's a transcript from a user after the CIFS volume was mounted (by root).
$ /sbin/restorecon -r -v .
/sbin/restorecon: error while labeling .: Transport endpoint is not connected
$ rm -fr .gvfs
rm: cannot remove '.gvfs': Transport endpoint is not connected
This appears to be a gvfs bug, not a coreutils bug. I'm on an x86_64 box.
Brian, what's your platform?
One more piece of information. Doing a restorecon inside /root shows this:
[root@localhost -]# /sbin/restorecon -r -v .
/sbin/restorecon reset ./.gvfs context
/sbin/restorecon set context ./.gvfs->system_u:object_r:admin_home_t:s0
failed:'Operation not supported'
So that reset looks wrong, in the first place, and even trying it brings
restorecon to a halt. At the very least, it looks like gvfs information needs
to be added to the default SELinux policy. That's probably a separate issue
from the original bug, but I thought I'd mention it just in case.
Thanks for report, reassigning to gvfs (other distributions have similar reports
assigned to it e.g. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476280 ,
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/212789) . Issue with
restorecon should probably be reported to policycoreutils separately.
Note a gvfs issue. This is the way fuse handles permissions on its mounts.
I unmounted these:
gvfs-fuse-daemon on /home/dmobrien/.gvfs type fuse.gvfs-fuse-daemon
gvfs-fuse-daemon on /root/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev)
and the error went away.
Fuse should play well with others and not do this crap.
I see this problem too. It has been reported upstream and fixed, a patch is
available - please see:
It would be nice to have this patch added to the fedora package.
The "Permission denied" error messages are by design due to FUSE security
restrictions and it's conceptually difficult to avoid them.
The issue with persistent fuse mounts after logout should be fixed in upstream
and included in updated gvfs-0.2.4-1 package.
gvfs-0.2.4-1.fc9 has been submitted as an update for Fedora 9
gvfs-0.2.4-1.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update gvfs'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-5124
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
*** Bug 479816 has been marked as a duplicate of this bug. ***
This bug still occurs in Fedora 12. Logged in as root, du -sh in a user directory:
du: cannot access `.gvfs': Permission denied
This silly bug is still not fixed, it occurs in Fedora 13 too.
I rarely use X, but when running vncserver the results of munin's df plugin disappear.
2010/07/05-03:30:04  Error output from df_inode:
2010/07/05-03:30:04  df: `/home/andy/.gvfs': Permission denied
2010/07/05-03:30:04  Error executing df. Exit code 256
When I stop vncserver, the df results appear again, with gaps.
The presence of an empty .gvfs file should NOT affect the output of df!
Seems I have to choose between vncserver or munin disk usage stats, or stop vnc before */5!
(In reply to comment #15)
> This silly bug is still not fixed, it occurs in Fedora 13 too.
> I rarely use X, but when running vncserver the results of munin's df plugin
> /var/log/munin/munin-node.log :
> 2010/07/05-03:30:04  Error output from df_inode:
> 2010/07/05-03:30:04  df: `/home/andy/.gvfs': Permission denied
> 2010/07/05-03:30:04  Error executing df. Exit code 256
> When I stop vncserver, the df results appear again, with gaps.
> The presence of an empty .gvfs file should NOT affect the output of df!
> Seems I have to choose between vncserver or munin disk usage stats, or stop vnc
> before */5!
Please see comment 8 and comment 9. Applications should handle inaccessible mounts gracefully. This is not a problem of gvfs.
Also, the ~/.gvfs directory is a mountpoint, even if it appears empty, there might be other processes binded to it.