GNOME Bugzilla – Bug 571839
gconf Type mismatch errors need to give more information
Last modified: 2018-08-17 13:55:43 UTC
Where gconf is going to give a 'Type mismatch' error it should state what gconf item it is trying to parse so you can tell what broke. In my particular case gconf_value_list_to_primitive_list_destructive was giving a Type mismatch: Expected list, got string in an app but it's not obvious which gconf value is broken. Other information: the callers to gconf_value_list_to_primitive_list_destructive mostly seem to have a key which they selected the data from; I'm not sure whether the right thing here is to pass that key down so it can get added to the error, or if some mechanism for mangling the GError as it gets passed back up is better.
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!