Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionPavlin Georgiev
2016-03-21 08:25:43 UTC
Description of problem:
dconf and dconf-editor show different results for the same schema.
Version-Release number of selected component (if applicable):
OS: RHEL 7.3 Beta (Maipo)
Name : dconf
Version : 0.22.0
Release : 2.el7
Architecture: x86_64
Name : dconf-editor
Version : 0.22.0
Release : 2.el7
Architecture: x86_64
How reproducible:
Start GNOME session.
Compare the output of dconf-editor, gsettings and dconf for the same scheme.
It is org.gnome.desktop.interface
Steps to Reproduce:
1. Run dconf-editor and search for the following schema: org.gnome.desktop.interface .
2. Make a screenshot.
3. Open the terminal and type: gsettings list-keys org.gnome.desktop.interface .
4. Save the output to a file
5. Open the terminal and type:dconf list "/org/gnome/desktop/interface/"
6. Save the output to a file.
7. Compare the results
Actual results:
See attachments.
Expected results:
dconf and dconf-editor should show the same keys in the same schema.
Additional info:
(In reply to Pavlin Georgiev from comment #0)
> Expected results:
> dconf and dconf-editor should show the same keys in the same schema.
It shouldn't unless you've already changed all keys in the directory and haven't added some other. DConf just stores the values and doesn't read schemas. You can save there even keys which are not in the corresponding schema.
dconf-editor access the schemas so it sees all the keys but this is necessary to allow users to change the values. Maybe the name of the app is misleading here, it should be probably named like gsettings-editor.