I wrote a plugin for the wayfire wayland compositor, which uses gsettings to store it’s setting.
g_settings_set_uint(...) is called which results in the G_CALLBACK(…) to be called and dconf-editor / gsettings to reflect those changes.
Although when setting that same property via either gsetting/dconf cli or dconf-editor the G_CALLBACK(…) is not called.
I can only imagine that this is because the compositor the first process in that session, as I have verified the “changed” signal to not be working as well with “ca.desrt.dconf-editor.Settings”
- I verified that the DBUS_SESSION_ADDRESS is already set correctly.
- /usr/lib/dconf-service is already running.
- All the signals are emitted if monitored via dconf watch /
- Glib 2.64.4
I prefer to use gsettings instead of the compositor’s own wf-config and appreciate your suggestions.