To lock down a dconf key, you will need to create a locks subdirectory in the keyfile directory. The files inside this directory contain a list of keys to lock. Just as with the keyfiles, you may add any number of files to this directory. Here is an example of what one might look like:
Before you can lock down a key, you need to set it. This example shows how to lockonce it has been set. At this point, you should have and with the settings that you want to lock down.
Create a directory named /etc/dconf/db/local.d/locks.
Create a file in the /etc/dconf/db/local.d/locks/ directory and list one key per line. For example, create /etc/dconf/db/local.d/locks/00_default-wallpaper:
# prevent changes to the background /org/gnome/desktop/background/picture-uri /org/gnome/desktop/background/picture-options /org/gnome/desktop/background/primary-color /org/gnome/desktop/background/secondary-color
Update the system databases:
# dconf update
As of dconf 0.7.4, lockdown is only supported on a per-key basis for performance reasons; you may not yet lock entire subpaths. There are plans to address this in future releases.
This work is licensed under a.
Got a comment? Spotted an error? Found the instructions unclear? Send feedback about this page.