Bug 1541448

Summary:	dconf read broken
Product:	[Fedora] Fedora	Reporter:	jniederm
Component:	dconf	Assignee:	Matthias Clasen <mclasen>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	27	CC:	mclasen, rhughes
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-15 03:16:39 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 jniederm 2018-02-02 15:19:46 UTC

Description of problem:
* If `-d` option used, it always return nothing
* If `-d` omitted it returns a value only when default value is not used.
That means it is not possible to:
* get effective value when default is selected
* get value of default when custom value is selected

Version-Release number of selected component (if applicable):
dconf-0.26.1-1.fc27.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Run following command:

```
$ dconf reset /org/gnome/calculator/base
$ dconf read /org/gnome/calculator/base
$ dconf read -d /org/gnome/calculator/base
$ dconf write /org/gnome/calculator/base 12
$ dconf read /org/gnome/calculator/base
12
$ dconf read -d /org/gnome/calculator/base
```

Actual results:
see above

Expected results:
it is possible to independently read effective and default value no matter what the current setting is

Additional info:

Comment 1 jniederm 2018-03-15 03:16:39 UTC

Not a bug. The confusion was cause by mixing dconf default value (one layer of dconf database) and gsettings default value (defined in gsettings schema documents).