glib-compile-schemas doesn't compile relocatable schemas

Bug #1281580 reported by Attila Hammer
This bug affects 13 people
Affects Status Importance Assigned to Milestone
glib2.0 (Ubuntu)

Bug Description

Dear Developers,

I am using the Ubuntu 14.04 development release with the GNOME Shell 3.10 and, because my wife is using this system as well, I defined some settings in a gschema.override file.
Everything is working right, except applying settings related to custom key-bindings.

I added following lines my gschema.override file:
custom-keybindings = ['/org/gnome/settings-daemon/plugins/media-keys/custom-keybinding/custom0']

name = 'Launch Gedit'
command = 'gedit'
binding = '<Super>g'

I put my gschema.override file in the '/usr/share/glib-2.0/schemas' directory. After I added these lines, I ran 'glib-compile-schemas /usr/share/glib2.0/schemas' and no error was reported.
For testing purposes I created a new user, logged out, and logged in with the new user. In the best case, the custom key-binding were applied automatically, but this has not happened. Other defined key-bindings were applied correctly.
In the gnome-control-center's key-bindings tab, the table containing custom shortcuts is empty, containing one row with empty columns.

Running 'gsettings list-recursively' shows, the name, command, and binding key pairs contain empty ('') values.

If I manually run following commands, the custom key-binding is created correctly:
gsettings set name "Launch Gedit"
gsettings set command "gedit"
gsettings set binding "<Super>g"

Am I doing anything wrong when I want to add a custom key-bindings in my schema file, or is 'glib-compile-schemas' really not applying this part from the schema file?


ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libglib2.0-bin 2.39.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
Uname: Linux 3.13.0-8-generic i686
ApportVersion: 2.13.2-0ubuntu4
Architecture: i386
CurrentDesktop: GNOME
Date: Tue Feb 18 13:58:37 2014
InstallationDate: Installed on 2013-12-13 (67 days ago)
InstallationMedia: BeLin 3.02 i386
SourcePackage: glib2.0
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Attila Hammer (hammera) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in glib2.0 (Ubuntu):
status: New → Confirmed
starbroken (starbroken)
summary: - Glib-compile-schemas utility possible doesn't compibiling right
- relocatable schemas
+ glib-compile-schemas doesn't compile relocatable schemas
Revision history for this message
starbroken (starbroken) wrote :

I have the same problem.

All entries in my gschema.override file, that affect relocatable schemas, are ignored.
All other entries are applied.

description: updated
Revision history for this message
Michael Zaugg (AOI) (it-oas) wrote :

Here is an explantion how to do it in dconf:

Changed in glib:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
ksamak (ksamak) wrote :

We at hypra make accessibility features, and a configuration package suite, mate-accessibility.
This bug is seriously jeopardising any attempt at a clean default set of relocatable schemas, and forces us to configure each impaired user machine by hand, or remotely.
We use compiz, and are currently engaged in re-introducing it in debian (
We aim at introducing the mate-accessibility packages in debian, and flow it into ubuntu as soon as possible. For now, this option is unfortunately closed to us.

please consider fixing this. thank you for reading

Revision history for this message
PJSingh5000 (pjsingh5000) wrote :

Experiencing this issue on Ubuntu 16.04 x64.

To recreate...

$ gsettings get org.compiz.expo:/org/compiz/profiles/unity/plugins/expo/ vp-saturation

Note the value is 40.0.

Create a file called /usr/share/glib-2.0/schemas/11_test.gschema.override with the following content:
    vp-saturation = '10.0'

Note that a relocatable schema was specified in the above file.

$ glib-compile-schemas /usr/share/glib-2.0/schemas/

$ gsettings get org.compiz.expo:/org/compiz/profiles/unity/plugins/expo/ vp-saturation

Note that the vp-saturation value is still 40, and has not been updated.

Revision history for this message
Victor Engmark (victor-engmark) wrote :
Revision history for this message
Leo Jiménez (leojimenezcr) wrote :

I have the same problem compiling relocatable schemas on override files on Ubuntu MATE 16.04.

Manual configuration with 'gsettings set ...' work correctly.

Changed in glib:
status: Confirmed → Expired
Revision history for this message
Lorenzo (lollo93) wrote :

It is possible that this bug is open from 2014 and no one fixed the bug?

I've been last couple of days trying to create a gschema.override file with relocatable schemas and now I understands that there is a bug unfixed.

I'm on Debian 9.5

Revision history for this message
Rudra Saraswat (rs2009) wrote :

I can confirm that this issue is still present in Ubuntu 20.04.1 Focal Fossa.

Revision history for this message
David Hedlund (g-public) wrote (last edit ):

Still an issue in Ubuntu MATE 23.04. I filed the MATE counterpart for this bug at

To list all relocatable-schemas: $ gsettings list-relocatable-schemas

With that said, should we change the title to include which types of relocatable schemas that are not compiled by glib-compile-schemas?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.