After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 745947 - order of gsettings overrides seems to have been reversed
order of gsettings overrides seems to have been reversed
Status: RESOLVED DUPLICATE of bug 668234
Product: dconf-editor
Classification: Other
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: dconf-editor maintainer(s)
dconf-editor maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-03-10 07:50 UTC by darkxst
Modified: 2015-03-13 00:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description darkxst 2015-03-10 07:50:22 UTC 
This behaviour seems to have reversed recently. It used to be as mentioned in the glib-compile-schemas man page

" By convention, vendor override files begin with nn_ where nn is a number from 00 to 99. Higher numbered files have higher priority (eg: if the same override is made in a file numbered 10 and then again in a file numbered 20, the override from 20 will take precedence). "

However current 10_ seems to take higher priority than 20_
Comment 1 darkxst 2015-03-10 07:55:15 UTC 
we override org.gnome.desktop.background in 20_ubuntu-gnome-default-settings.gschema.override but are gettings the settings from 10_desktop-base.gschema.override instead
Comment 2 Matthias Clasen 2015-03-10 17:54:58 UTC 
sounds like a testcase waiting to be written
Comment 3 Allison Karlitskaya (desrt) 2015-03-10 18:55:17 UTC 
are you sure?

it seems to work for me...

desrt@humber:~/override-test$ head -n 10 *
==> 10_first.gschema.override <==
[org.gtk.test.basic-types]
test-string="this is from 10"

==> 20_second.gschema.override <==
[org.gtk.test.basic-types]
test-string="this is from 20"

==> org.gtk.test.gschema.xml <==
<schemalist>
  <schema id="org.gtk.test.basic-types" path="/tests/basic-types/">
    <key name="test-string" type="s">
      <default>"a string, it seems"</default>
    </key>
  </schema>
</schemalist>
desrt@humber:~/override-test$ glib-compile-schemas .  # debian jessie
desrt@humber:~/override-test$ gsettings --schemadir . get org.gtk.test.basic-types test-string
'this is from 20'
desrt@humber:~/override-test$ ~/code/glib/gio/glib-compile-schemas . # git
desrt@humber:~/override-test$ gsettings --schemadir . get org.gtk.test.basic-types test-string
'this is from 20'
desrt@humber:~/override-test$
Comment 4 darkxst 2015-03-10 22:07:44 UTC 
actually, this seems to be a bug in dconf-editor and the way it generates the default values. (atleast with version 0.22 in Ubuntu, I will check with 3.15.91)
Comment 5 darkxst 2015-03-10 23:30:22 UTC 
so:
gsettings works as expected
dconf-editor under jhbuild works
dconf-editor under Ubuntu vivid is broken
Comment 6 Allison Karlitskaya (desrt) 2015-03-13 00:55:56 UTC 
dconf-editor contains a bunch of schema-parsing logic from before GSettings was able to provide all of the information that it needed via the GSettingsSchema APIs.

See bug 668234 for the correct fix to this problem.

*** This bug has been marked as a duplicate of bug 668234 ***