[GNC-dev] Trouble with gsettings in GC 4.9

[Geert Janssens]

Op maandag 27 december 2021 17:57:17 CET schreef Christian Wehling:
> Hi,
> I have compiled version 4.9 (Ubuntu 20.04) from sourceforge.net and
> have trouble with the "glib-schemas".
> The installation seemed to run without errors, but when I start Gnucash
> I get these outputs:
> [...]
> * 16:48:51  INFO <gnc.gui            > [gnc_load_app_icons] Path 14:
> /usr/local/share/gnucash/icons
> * 16:48:51  INFO <gnc.gui            > [gnc_load_app_icons] Path 15:
> /usr/local/share/icons
> * 16:48:51 ERROR <GLib-GIO           > g_settings_new_full: assertion
> 'schema != NULL' failed
> * 16:48:51  WARN <gnc.app-utils.gsett>
> [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown
> gsettings schema org.gnucash.GnuCash.general
> * 16:48:51 ERROR <gnc.app-utils      > GVariant*
> gnc_gsettings_get_user_value(const gchar*, const gchar*): assertion
> 'G_IS_SETTINGS (settings_ptr)' failed
> [... and so on]
> 
> If I run:
> glib-compile-schemas --strict /usr/local/share/glib-2.0/schemas/
> /usr/local/share/glib-
> 2.0/schemas/org.gnucash.dialogs.business.gschema.xml:3:1  Fehler in
> Zeile 3, Zeichen 1: <schema id='org.gnucash.dialogs.business'> wurde
> bereits angegeben.  --strict was specified; exiting.
> 
> 
> I had installed version 4.7 in the same way and it worked fine.

In 4.9 there should not longer be a file 
/usr/local/share/glib-2.0/schemas/org.gnucash.dialogs.business.gschema.xml

If it's there, that's the reason for the installation failure and subsequent run time error.

In fact there shouldn't be any gschema.xml file in there that starts with 
org.gnucash.<something> where <something> is anything but GnuCash. So you should only 
find files that start with org.gnucash.GnuCash or not with org.gnucash at all (you can have 
gschema.xml files from other applications you build manually).

Please remove all the org.gnucash.****.gschema.xml files from that directory before 
installing 4.9.
Then check if that exact file reappears after running "sudo ninja install". If it does, something 
is wrong with your sources or build directory.

Regards,

Geert