GNOME Bugzilla – Bug 657740
gsettings-data-convert crashed with signal 5 in g_settings_set_value()
Last modified: 2018-08-17 13:54:57 UTC
this report has been filed here: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/834575 crashed while logging ".
+ Trace 228275
Thread 1 (Thread 0xb789a930 (LWP 1530))
I don't understand how you can reach gconf-value.c line 734 with src == NULL given that line 731 contains g_return_val_if_fail(src != NULL, NULL); Unless you were building with --disable-debug which will then add "-DG_DISABLE_CHECKS=1 -DG_DISABLE_ASSERT=1" to the CFLAGS. But poking around in the Ubuntu build system doesn't show that happening...(at least it's not in the build logs)
GConf has been deprecated since 2011. GConf is not under active development anymore. Its codebase has been archived: https://gitlab.gnome.org/Archive/gconf/commits/master dconf and gsettings are its successors. See https://developer.gnome.org/gio/stable/ch34.html and https://developer.gnome.org/GSettings/ for porting info. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Feel free to open a task in GNOME Gitlab if the issue described in this task still applies to a recent + supported version of dconf/gsettings. Thanks!