Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1147973 - gvfsd-trash is preventing autofs mounts from being expired when fs perms are o-rx
gvfsd-trash is preventing autofs mounts from being expired when fs perms are ...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gvfs (Show other bugs)
7.0
x86_64 Linux
medium Severity medium
: rc
: ---
Assigned To: Ondrej Holy
Desktop QE
:
Depends On:
Blocks: 1075802 1133060
  Show dependency treegraph
 
Reported: 2014-09-30 08:50 EDT by Ondrej Holy
Modified: 2015-11-19 04:26 EST (History)
12 users (show)

See Also:
Fixed In Version: gvfs-1.22.4-1.el7
Doc Type: Bug Fix
Doc Text:
Previously, the GNOME Desktop Virtual File System (GVFS) trash implementation did not take access permissions into consideration when creating file monitors for mount points. Consequently, file monitors were polling files without read access permissions, preventing AutoFS mount points from expiring as they normally would when not in use for some time. With this update, the trash implementation no longer creates file monitors to monitor files without read access permissions. As a result, AutoFS mount points can now freely expire.
Story Points: ---
Clone Of: 998061
Environment:
Last Closed: 2015-11-19 04:26:26 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 737371 None None None Never
Red Hat Knowledge Base (Solution) 473033 None None None Never
Red Hat Product Errata RHBA-2015:2106 normal SHIPPED_LIVE desktop core libraries bug fix and enhancement update 2015-11-19 04:34:35 EST

  None (edit)
Comment 6 errata-xmlrpc 2015-11-19 04:26:26 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2106.html

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