Which program asks to open "/etc/dconf/db/local:X" and why cant't it?

I'm setting a fresh Debian 12 bookworm up. I played a little with settings and extensions. While trying to set my compose key —GUI allows to set it as "pause", but it has no effect, while I *can* choose "right-super"— I could have messed up a bit. I downloaded and executed the perl script at , but only in export mode anyway: ./keybindings.pl -e /tmp/keys.csv. I ran it both as root and as user 1000. In both cases I get

dconf-WARNING **: 16:55:41.021: unable to open file '/etc/dconf/db/local:X': L’ouverture du fichier « /etc/dconf/db/local:X » a échoué : échec de open() : Aucun fichier ou dossier de ce type; expect degraded performance

Neither Google nor Bing have any response to the query for "/etc/dconf/db/local:X" (with quotes). dconf itself is just a back-end for configuration settings… According to loginctl, my session is of type Wayland. I currently have

$ ls -l /etc/dconf/db
total 20
drwxr-xr-x 2 root       root       4096 2024-12-30 12:41 ibus.d
drwxr-xr-x 3 root       root       4096 2025-01-13 10:52 local.d
-rw-r--r-- 1 ondelettes ondelettes 5459 2025-01-14 16:56 ibus
-rw-r--r-- 1 ondelettes ondelettes  408 2025-01-14 16:56 local

$ ls -l /etc/dconf/profile
total 8
-rw-r--r-- 1 root root 28 2023-02-13 12:22 ibus
-rw-r--r-- 1 root root 31 2025-01-13 10:39 user

$ chmod a+rxw /etc/dconf/db had no effect on the issue. $ dconf update as user or root returns no error, nor any improvement. If I touch /etc/dconf/db/local:X, I get invalid gvdb header the next time. If I launch gnome-terminal or soffice from command line, I get the same warning message (unable to open file '/etc/dconf/db/local:X'), which is annoying as I work whole day from command line.