My gsettings database has many entries that are duplicated or triplicated. Some are "normal" single entries.
$ gsettings --schemadir /usr/share/glib-2.0/schemas list-recursively | grep button-power
org.gnome.settings-daemon.plugins.power button-power 'interactive'
org.gnome.settings-daemon.plugins.power button-power 'interactive'
$ gsettings list-recursively | grep sudoku-difficulty
org.gnome.sudoku print-multiple-sudoku-difficulty 'easy'
$ gsettings list-recursively | grep print-wrap-mode
org.gnome.gedit.preferences.print print-wrap-mode 'word'
org.gnome.gedit.preferences.print print-wrap-mode 'word'
org.gnome.gedit.preferences.print print-wrap-mode 'word'
dconf dump and dconf load are not effective
The utility dconf dump doesn't show duplicate entries:
$ dconf dump /org/gnome/settings-daemon/plugins/power/
[/]
idle-dim=false
lid-close-battery-action='nothing'
critical-battery-action='shutdown'
lid-close-ac-action='nothing'
Running dconf dump of single entries to file and import same file using dconf load doesn't get rid of duplicate entries:
$ gsettings list-recursively | grep lid-close-battery
org.gnome.settings-daemon.plugins.power lid-close-battery-action 'nothing'
org.gnome.settings-daemon.plugins.power lid-close-battery-action 'nothing'
$ dconf dump /org/gnome/settings-daemon/plugins/power/ > dconf-lid-battery.txt
$ dconf load /org/gnome/settings-daemon/plugins/power/ < dconf-lid-battery.txt
$ gsettings list-recursively | grep lid-close-battery
org.gnome.settings-daemon.plugins.power lid-close-battery-action 'nothing'
org.gnome.settings-daemon.plugins.power lid-close-battery-action 'nothing'
Might be a bug?
Appears to be a bug:
Based on bug reports it could be these three areas:
$ gsettings get org.freedesktop.ibus.general dconf-preserve-name-prefixes
['/desktop/ibus/engine/pinyin', '/desktop/ibus/engine/bopomofo', '/desktop/ibus/engine/hangul']
Replies to comments
Here are file and directory names of /etc/dconf:
$ tree /etc/dconf/
/etc/dconf/
├── db
│ ├── ibus
│ └── ibus.d
│ └── 00-upstream-settings
└── profile
└── ibus
3 directories, 3 files
Two of three files are dated from 2016 (Ubuntu 16.04 development time):
-rw-r--r-- 1 root root 3163 Oct 1 16:51 /etc/dconf/db/ibus
-rw-r--r-- 1 root root 1978 Jan 19 2016 00-upstream-settings
-rw-r--r-- 1 root root 28 Jan 19 2016 /etc/dconf/profile/ibus
gsettings/ dconf database entry. Do you have a link to such a function?gsettings reset <key-path>;-) oh and I think I might have found your problem: you probably have 2 schema definitions.resetsimply resets to installation default. It doesn't delete or remove the key-pair. After running forlid-close-battery-actionabove it changed the key fromnothingtosuspend. I will search for how I might have 2 or 3 schemas setup though./etc/dconf/profile/contents for active databases. (2)Use DBus monitor or d-feet to monitor replies dconf daemon while a gsettings query (if duplication exists in data passed). (3) dconf dump to backup user settings, logout, switch to console, login root (or superuser with sudo), move dconf user-db & system-db if there one to backup them also/usr/share/glib-2.0/schemas/gschemas.compiled, runglib-compile-schemas /usr/share/glib-2.0/schemasto compile new schema, logout then login through GUI & dconf load settings