Red Hat Bugzilla – Bug 445409
gvfsd-trash triggers autofs automounts whenever a directory is unmounted
Last modified: 2015-03-03 17:32:37 EST
Description of problem:
Please see bug 445060 for a description of the problem. Essentially, the
gvfsd-trash application performs a lookup of /autofs/managed/mountpoint/.Trash
whenever a directory is expired, triggerring a new mount.
Version-Release number of selected component (if applicable):
I'm not sure, reporter is using rawhide.
Steps to Reproduce:
Please see the aforementioned bug.
> Version-Release number of selected component (if applicable):
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
any updates on this? Is there a workaround?
> Is there a workaround?
One possible workaround is to change in /usr/share/gvfs/mounts/trash.mount
'AutoMount=true' line to 'AutoMount=false' (before starting gvfsd).
The problem is that files in /usr/share/gvfs/mounts/ are NOT marked
%config, which looks to me like another bug on its own, so it appears
that such change will be clobbered by updates.
What other side-effects such workaround may have I am really not sure
but without it auto-mounted NFS volumes are unusable (no clean unmount
Changing AutoMount property is not recommended, certain applications using GIO
may rely on availability of basic mounts. Also, .mount files are not config
files, should not be modified in any way and are designed to be replaced on
Please try the following update, containing proposed patch from upstream.
gvfs-0.2.4-5.fc9 has been submitted as an update for Fedora 9
gvfs-0.2.4-5.fc9 (binaries from koji) does not seem to create troubles
for autofs - at least for NFS mounts on one system I looked at.
If .mount files are not configuration then what is the point of their
existence in the first place?
The .mount files are control files for gvfsd daemon to know what backends are
available and how to spawn them. Parameters and syntax might change during
development. As long as the files are outside /etc, you shoudln't touch them.
gvfs-0.2.4-5.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-5693
This fix worked for me, Thanks!
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:
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.