| Summary: | Dconf and dconf-editor show different results for the same schema. | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Pavlin Georgiev <pgeorgie> | ||||||||
| Component: | dconf | Assignee: | Marek Kašík <mkasik> | ||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Desktop QE <desktop-qa-list> | ||||||||
| Severity: | low | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 7.3 | ||||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2016-03-21 10:26:14 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: | |||||||||
| Attachments: |
|
||||||||||
|
Description
Pavlin Georgiev
2016-03-21 08:25:43 UTC
Created attachment 1138481 [details]
Dconf output
Created attachment 1138482 [details]
Dconf-editor output
Created attachment 1138483 [details]
Gsettings output
(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. |