When I launch meld with sudo, su, gksu or gksudo I have the following output:

(meld:1666): GLib-GIO-CRITICAL **: g_dbus_proxy_new_sync: assertion 'G_IS_DBUS_CONNECTION (connection)' failed (meld:1666): GLib-GIO-CRITICAL **: g_dbus_proxy_get_name_owner: assertion 'G_IS_DBUS_PROXY (proxy)' failed (meld:1666): dconf-WARNING **: failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=745b249ad9024475816761582a9ee2ca --binary-syntax --close-stderr': Child process exited with code 1 

And I am not able to change the settings.
I use geany with sudo without any problem, error or warning, and I am able to change the geany 's settings.

When I launch meld with sudo, su, gksu or gksudo I have the following output:

(meld:1666): GLib-GIO-CRITICAL **: g_dbus_proxy_new_sync: assertion 'G_IS_DBUS_CONNECTION (connection)' failed (meld:1666): GLib-GIO-CRITICAL **: g_dbus_proxy_get_name_owner: assertion 'G_IS_DBUS_PROXY (proxy)' failed (meld:1666): dconf-WARNING **: failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=745b249ad9024475816761582a9ee2ca --binary-syntax --close-stderr': Child process exited with code 1 

And I am not able to change the settings.
In comparison, I use geany with sudo without any problem, error or warning, and I am able to change the geany's settings.

I use:

• meld 3.16.4
• dconf 0.26.0
• glib2 2.50.3