Bug 1879722

Summary: dconf is being affected by umask
Product: Red Hat Enterprise Linux 8 Reporter: Brandon Clark <brclark>
Component: dconfAssignee: Marek Kašík <mkasik>
Status: CLOSED ERRATA QA Contact: Jiri Prajzner <jprajzne>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.2CC: alanm, amike, ayadav, brclark, casantos, jkoten, jprajzne, jwright, mbliss, mkolbas, sbarcomb, tpelka
Target Milestone: rcKeywords: Triaged
Target Release: 8.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: dconf-0.28.0-4.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-18 15:49:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Brandon Clark 2020-09-16 20:17:51 UTC
Description of problem:
A fix to resolve behaviour where umask was changing permissions for dconf files was implemented in RHEL 7 and offered to upstream GNOME for inclusion. This fix was not implemented into upstream and, as such, was not included in RHEL 8. I've attached the RHEL 7 BZ and upstream issues to the listing.

Version-Release number of selected component (if applicable):
dconf-0.28.0-3.el8.x86_64

How reproducible:
Consistently.

Steps to Reproduce:
1. Set umask of file in /etc/dconf/db/distro.d/ to 0027
2. Reload GDM


Actual results:
dconf files are affected.

Expected results:
dconf files not affected by umask.

Comment 9 errata-xmlrpc 2021-05-18 15:49:45 UTC
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 (dconf bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2021:1848