GNOME Bugzilla – Bug 654812
editor doesn't show overridden keys
Last modified: 2015-02-22 12:24:08 UTC
I have confirmed this using Fedora 15 and dconf 0.7.5-1 and on Ubuntu 11.10 using dconf 0.7.5-3. Here's the Fedora example: 1.Ensure gsettings is using the default overriden value gsettings reset org.gnome.desktop.background picture-uri gsettings get org.gnome.desktop.background picture-uri 'file:///usr/share/backgrounds/lovelock/default-stripes/lovelock.xml' 2. Open dconf-editor and browse to org.gnome.desktop.background Result is 'file:///usr/share/themes/Adwaita/backgrounds/stripes.jpg' Result should be 'file:///usr/share/backgrounds/lovelock/default-stripes/lovelock.xml'
I can confirm it on Sabayon with dconf 0.8.0 and 0.9.0. If I put a .gschema.override in a proper place with contents, for example: [org.gnome.desktop.background] picture-uri='file:///this/that/there.png' then compile schemas, it works: it's visible for applications and GNOME itself. But dconf-editor and the dconf utility doesn't see the change: * dconf-editor displays the default value (as in the comment above), * dconf read ... displays no value. Similar for boolean values. What's more, here's what dconf lists: $ dconf list /org/gnome/desktop/ (dconf:6891): GLib-WARNING **: XDG_RUNTIME_DIR variable not set. Falling back to XDG cache dir. session/ ^^^^^^^^^^ the "background" directory is not listed. Another example. I have: [org.gnome.FileRoller.UI] view-toolbar=false after I modify the value in dconf-editor: $ dconf read /org/gnome/file-roller/ui/view-toolbar (dconf:6997): GLib-WARNING **: XDG_RUNTIME_DIR variable not set. Falling back to XDG cache dir. false if I reset it in dconf-editor to default value, it's marked in dconf-editor as checked (selected), NOT unselected, and: $ dconf read /org/gnome/file-roller/ui/view-toolbar (dconf:7025): GLib-WARNING **: XDG_RUNTIME_DIR variable not set. Falling back to XDG cache dir. ^^^^ no true/false output (and FileRoller starts without toolbar, as expected, and after I start and close FileRoller, it seems to be "modified" because "false" is displayed correctly).
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
*** Bug 694772 has been marked as a duplicate of this bug. ***
[moving dconf>editor tickets to dconf-editor product. See bug 744791]