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):
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
Customized values are not being applied, no dconf/gsettings command is being applied, the corrupted database keeps untouched.
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.
The system was customized with the following values:
# cat /etc/dconf/db/local.d/00-screensaver
# cat /etc/dconf/db/local.d/locks/screensaver
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.