Comment 2 for bug 1535421

This was quite a strange one to track down, but in the short of it, ~/.config/dconf needs to be bind-mounted into the container. When xchat would read gconf settings, they would always return null even though it just set the key. This is due to how gconf settings are written and read.

When writing a key, it goes over dbus. In our case, since we have the dbus session bride, the host ~/.config/dconf/user backend would get updated. However, when reading a key, it tries to read directly from the file and since the backend was not bind-mounted, the container's backend did not have any info in it.

At any rate, the fix is to bind-mount the ~/.config/dconf directory.