It would appear not and the problem is likely more than that. Building Glib from git and installing it with LD_LIBRARY_PATH or /etc/ld.so.conf.d/ trickery will allow applications like empathy and evince to run, but the settings are corrupt and (now I'm way out of my depth) probably require a new GConf as well, then you have to repair the damage done by the broken gsettings conversion processes (including things like
Just rebuilding Glib allows the affected applications to run with:
GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
It would appear not and the problem is likely more than that. Building Glib from git and installing it with LD_LIBRARY_PATH or /etc/ld.so.conf.d/ trickery will allow applications like empathy and evince to run, but the settings are corrupt and (now I'm way out of my depth) probably require a new GConf as well, then you have to repair the damage done by the broken gsettings conversion processes (including things like
$ gsettings- data-convert --verbose data-convert: 12168): GLib-GObject- CRITICAL **: gtype.c:2710: You forgot to call g_type_init() data-convert: 12168): GLib-GObject- CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed data-convert: 12168): GLib-GObject- CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
(gsettings-
(gsettings-
(gsettings-
Segmentation fault
Just rebuilding Glib allows the affected applications to run with:
GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
which is better than nothing.
-jh