Bug 1570569 - dconf database corrupted with no error messages
Summary: dconf database corrupted with no error messages
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dconf
Version: 7.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Marek Kašík
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1626369 1626370 1626372
TreeView+ depends on / blocked
 
Reported: 2018-04-23 09:12 UTC by Alejandro Coma
Modified: 2018-10-30 10:27 UTC (History)
6 users (show)

Fixed In Version: dconf-0.28.0-4.el7
Doc Type: Bug Fix
Doc Text:
Previously, the dconf-update utility ignored custom dconf configuration files in the /etc/dconf/db/*.d/ directories if the modification time of the directories did not change. As a consequence, the dconf configuration system did not load keys from custom files under these rare circumstances. With this update, dconf-update now checks file modification time. As a result, dconf correctly loads keys from all custom configuration files.
Clone Of:
: 1626369 1626370 1626372 (view as bug list)
Environment:
Last Closed: 2018-10-30 10:26:03 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:3140 0 None None None 2018-10-30 10:27:15 UTC

Description Alejandro Coma 2018-04-23 09:12:00 UTC
Description of problem:
On a system with a few customizations, dconf database (binary) has been corrupted and we got no error messages. The only symptom is that the customization is not being applied.

Version-Release number of selected component (if applicable):
RHEL7.3
gnome 3.14

How reproducible:
Could not reproduce the issue.

Steps to Reproduce:
(If the gnome customizations are not being applied, to identify dconf database corruption):
1. dconf dump produces empty output
2. any gsettings set command do not change the configuration 
3. no errors can be found on the log files

Actual results:
Customized values are not being applied, no dconf/gsettings command is being applied, the corrupted database keeps untouched.


Expected results:
This (database corruption) should be detected and reflected in the logs.
dconf Database sanity checks should be done.
dconf Database should be rebuilt if corruption is detected.

Additional info:
The system was customized with the following values:

# cat /etc/dconf/db/local.d/00-screensaver 
[org/gnome/desktop/session]
idle-delay=uint32 0
[org/gnome/desktop/screensaver]
lock-enabled=false
lock-delay=uint32 0

# cat /etc/dconf/db/local.d/locks/screensaver 
/org/gnome/desktop/session/idle-delay
/org/gnome/desktop/screensaver/lock-enabled
/org/gnome/desktop/screensaver/lock-delay

Comment 44 errata-xmlrpc 2018-10-30 10:26:03 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, 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/RHSA-2018:3140


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