Re: [GNC] Problems upgrading to 4.8a
Apologies if this is a duplicate - my ISP's "upgraded" emailer is FUBAR. Yes, that's exactly what I found. I got around it by running Gnucash in an environment in which XDG_DATA_DIRS omitted the /usr/local/share reference. Thanks for the update! On Tue, 29 Nov, 2022 at 3:41 AM, Geert Janssens wrote: To: gnucash-user@gnucash.org; phil wolff A bug (https://bugs.gnucash.org/show_bug.cgi?id=798672) was opened reporting this same issue, which prompted me to look at it again. I think I have found the cause of the issue this time and added a fix to our source code. It should be fixed for gnucash 4.13. If you can build for yourself from source, you could apply this minor change: https://github.com/Gnucash/gnucash/commit/98251d59a6e6940efae2001a1e619c08828c8738 Otherwise, you can monitor the bugs on the Ubuntu bug tracker (which the original poster added to our own bug report mentioned above) and/or poke the package maintainers to apply the fix earlier. Regards, Geert Op dinsdag 11 oktober 2022 21:29:12 CET schreef Phil Wolff: > On 10/10/22 12:14, Geert Janssens wrote: > > > Phil, > > > > > I'm sorry I stopped responding on this thread. I ran out of time and also > out of things to suggest. This is the first time I have ever seen the > situation where dconf-editor and gsettings (cli tool) work fine and gnucash > doesn't. > > > > > So far gsettings issues have always been the result of missing schema files > or an old set being found before the proper ones. > > > > > So the only clue left for now is to figure out exactly which schema folders > gnucash checks. That's why I was looking for a way to print the contents of > variable XDG_DATA_DIRS gnucash sees while starting. > > > > > Do you still have the file > > $HOME/.config/gnucash/config-user.scm > > With the contents to print XDG__DATA_DIRS ? > > Welcome back!! Yes, I still have it. > > > > > If so, can you run gnucash from the command line as follows: > > > > > gnucash --no-file --logto stderr > > > > > And post the result that's printed in the terminal here ? > > I ran it, and got a long dump of error messages (below). The first few lines > confirm that /usr/share/glib-2.0/schemas/gschemas.compiled is not being > read. After some thought, I deleted > /usr/local/share/glib-2.0/schemas/gschemas.compiled and ran the command > again: > > dellbert@dellbert:/usr/local/share/glib-2.0/schemas$ gnucash --nofile > --logto stderr * 16:15:15 WARN > XDG__DATA_DIRS=/usr/share/ubuntu-xorg:/usr/share/gnome:/home/dellbert/.loca > l/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/shar > e/:/usr/share/:/var/lib/snapd/desktop Found Finance::Quote version 1.51. > > Encouraged by this, I tried gnucash from the desktop icon, and it started up > just like it did before the upgrade - splash screen, register page, > scheduled transaction preview, the whole nine yards. > > I created an empty file (touch gschemas.compiled) and tried again - same > successful result. > > > I renamed the schemas folder, created a new one, copied one schema file > (org.gnome.rhythmbox.gschema.xml) from /usr/share/glib-2.0/schemas, > compiled it and ran the test command again. The result was a long dump like > the one below. > > It appears that, unlike the previous version I was running, this version > (4.8a+(2021-09-28)) of gnucash can't tolerate a non-trivial > /usr/local/share/glib-2.0/schemas/gschemas.compiled file. > > Here's the original dump: > > dellbert@dellbert:/usr/local/share/glib-2.0/schemas$ gnucash --nofile > --logto stderr * 16:34:36 ERROR g_settings_new_full: assertion > 'schema != NULL' failed * 16:34:36 WARN > [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown > gsettings schema org.gnucash.GnuCash.general * 16:34:36 ERROR > GVariant* gnc_gsettings_get_user_value(const gchar*, const > gchar*): assertion 'G_IS_SETTINGS (settings_ptr)' failed * 16:34:36 ERROR > g_settings_new_full: assertion 'schema != NULL' failed * > 16:34:36 WARN [gnc_gsettings_get_settings_ptr()] > Ignoring attempt to access unknown gsettings schema org.gnucash.general * > 16:34:36 ERROR GVariant* gnc_gsettings_get_user_value(const > gchar*, const gchar*): assertion 'G_IS_SETTINGS (settings_ptr)' failed * > 16:34:36 ERROR g_settings_new_full: assertion 'schema != NULL' > failed * 16:34:36 WARN > [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown > gsettings schema org.gnucash.GnuCash.general * 16:34:36 ERROR > gdouble gnc_gsettings_get_float(const gchar*, const > gchar*): assertion 'G_IS_SETTINGS (settings_ptr)' failed * 16:34:36 ERROR > g_settings_new_full: assertion 'schema != NULL' failed * > 16:34:36 WARN [gnc_gsettings_get_settings_ptr()] > Ignoring attempt to access unknown gsettings schema > org.gnucash.GnuCash.general * 16:34:36 ERROR gboolean > gnc_gsettings_get_bool(const gchar*, const gchar*): assertion > 'G_IS_SETTINGS (settings_ptr)' failed * 16:34:36 ERROR >
Re: [GNC] Problems upgrading to 4.8a
A bug (https://bugs.gnucash.org/show_bug.cgi?id=798672[1]) was opened reporting this same issue, which prompted me to look at it again. I think I have found the cause of the issue this time and added a fix to our source code. It should be fixed for gnucash 4.13. If you can build for yourself from source, you could apply this minor change: https://github.com/Gnucash/gnucash/commit/ 98251d59a6e6940efae2001a1e619c08828c8738[2] Otherwise, you can monitor the bugs on the Ubuntu bug tracker (which the original poster added to our own bug report mentioned above) and/or poke the package maintainers to apply the fix earlier. Regards, Geert Op dinsdag 11 oktober 2022 21:29:12 CET schreef Phil Wolff: > On 10/10/22 12:14, Geert Janssens wrote: > > > Phil, > > > > > I'm sorry I stopped responding on this thread. I ran out of time and also > out of things to suggest. This is the first time I have ever seen the > situation where dconf-editor and gsettings (cli tool) work fine and gnucash > doesn't. > > > > > So far gsettings issues have always been the result of missing schema files > or an old set being found before the proper ones. > > > > > So the only clue left for now is to figure out exactly which schema folders > gnucash checks. That's why I was looking for a way to print the contents of > variable XDG_DATA_DIRS gnucash sees while starting. > > > > > Do you still have the file > > $HOME/.config/gnucash/config-user.scm > > With the contents to print XDG__DATA_DIRS ? > > Welcome back!! Yes, I still have it. > > > > > If so, can you run gnucash from the command line as follows: > > > > > gnucash --no-file --logto stderr > > > > > And post the result that's printed in the terminal here ? > > I ran it, and got a long dump of error messages (below). The first few lines > confirm that /usr/share/glib-2.0/schemas/gschemas.compiled is not being ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
On 10/10/22 12:14, Geert Janssens wrote: Phil, I'm sorry I stopped responding on this thread. I ran out of time and also out of things to suggest. This is the first time I have ever seen the situation where dconf-editor and gsettings (cli tool) work fine and gnucash doesn't. So far gsettings issues have always been the result of missing schema files or an old set being found before the proper ones. So the only clue left for now is to figure out exactly which schema folders gnucash checks. That's why I was looking for a way to print the contents of variable XDG_DATA_DIRS gnucash sees while starting. Do you still have the file $HOME/.config/gnucash/config-user.scm With the contents to print XDG__DATA_DIRS ? Welcome back!! Yes, I still have it. If so, can you run gnucash from the command line as follows: gnucash --no-file --logto stderr And post the result that's printed in the terminal here ? I ran it, and got a long dump of error messages (below). The first few lines confirm that /usr/share/glib-2.0/schemas/gschemas.compiled is not being read. After some thought, I deleted /usr/local/share/glib-2.0/schemas/gschemas.compiled and ran the command again: [1]dellbert@dellbert:/usr/local/share/glib-2.0/schemas$ gnucash --nofile --logto stderr * 16:15:15 WARN XDG__DATA_DIRS=/usr/share/ubuntu-xorg:/usr/share/gnome:/home/dellbert/. local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/l ocal/share/:/usr/share/:/var/lib/snapd/desktop Found Finance::Quote version 1.51. Encouraged by this, I tried gnucash from the desktop icon, and it started up just like it did before the upgrade - splash screen, register page, scheduled transaction preview, the whole nine yards. I created an empty file (touch gschemas.compiled) and tried again - same successful result. I renamed the schemas folder, created a new one, copied one schema file (org.gnome.rhythmbox.gschema.xml) from /usr/share/glib-2.0/schemas, compiled it and ran the test command again. The result was a long dump like the one below. It appears that, unlike the previous version I was running, this version (4.8a+(2021-09-28)) of gnucash can't tolerate a non-trivial /usr/local/share/glib-2.0/schemas/gschemas.compiled file. Here's the original dump: [2]dellbert@dellbert:/usr/local/share/glib-2.0/schemas$ gnucash --nofile --logto stderr * 16:34:36 ERROR g_settings_new_full: assertion 'schema != NULL' failed * 16:34:36 WARN [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown gsettings schema org.gnucash.GnuCash.general * 16:34:36 ERROR GVariant* gnc_gsettings_get_user_value(const gchar*, const gchar*): assertion 'G_IS_SETTINGS (settings_ptr)' failed * 16:34:36 ERROR g_settings_new_full: assertion 'schema != NULL' failed * 16:34:36 WARN [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown gsettings schema org.gnucash.general * 16:34:36 ERROR GVariant* gnc_gsettings_get_user_value(const gchar*, const gchar*): assertion 'G_IS_SETTINGS (settings_ptr)' failed * 16:34:36 ERROR g_settings_new_full: assertion 'schema != NULL' failed * 16:34:36 WARN [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown gsettings schema org.gnucash.GnuCash.general * 16:34:36 ERROR gdouble gnc_gsettings_get_float(const gchar*, const gchar*): assertion 'G_IS_SETTINGS (settings_ptr)' failed * 16:34:36 ERROR g_settings_new_full: assertion 'schema != NULL' failed * 16:34:36 WARN [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown gsettings schema org.gnucash.GnuCash.general * 16:34:36 ERROR gboolean gnc_gsettings_get_bool(const gchar*, const gchar*): assertion 'G_IS_SETTINGS (settings_ptr)' failed * 16:34:36 ERROR g_settings_new_full: assertion 'schema != NULL' failed * 16:34:36 WARN [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown gsettings schema org.gnucash.GnuCash.general * 16:34:36 ERROR gboolean gnc_gsettings_get_bool(const gchar*, const gchar*): assertion 'G_IS_SETTINGS (settings_ptr)' failed * 16:34:36 ERROR g_settings_new_full: assertion 'schema != NULL' failed * 16:34:36 WARN [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown gsettings schema org.gnucash.GnuCash.general * 16:34:36 ERROR gboolean gnc_gsettings_get_bool(const gchar*, const gchar*): assertion 'G_IS_SETTINGS (settings_ptr)' failed * 16:34:36 WARN [file_retain_type_changed_cb()] no file retention policy was set, assuming conservative policy 'forever' * 16:34:36 ERROR g_settings_new_full: assertion 'schema != NULL' failed * 16:34:36 WARN [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown gsettings schema org.gnucash.GnuCash.general * 16:34:36 ERROR
Re: [GNC] Problems upgrading to 4.8a
Phil, I'm sorry I stopped responding on this thread. I ran out of time and also out of things to suggest. This is the first time I have ever seen the situation where dconf-editor and gsettings (cli tool) work fine and gnucash doesn't. So far gsettings issues have always been the result of missing schema files or an old set being found before the proper ones. So the only clue left for now is to figure out exactly which schema folders gnucash checks. That's why I was looking for a way to print the contents of variable XDG_DATA_DIRS gnucash sees while starting. Do you still have the file $HOME/.config/gnucash/config-user.scm With the contents to print XDG__DATA_DIRS ? If so, can you run gnucash from the command line as follows: gnucash --no-file --logto stderr And post the result that's printed in the terminal here ? Regards, Geert Op maandag 12 september 2022 14:49:18 CEST schreef Phil Wolff: > On 9/11/22 13:02, Geert Janssens wrote: > > Op zaterdag 10 september 2022 19:49:52 CEST schreef Phil Wolff: > > On 9/10/22 08:34, Geert Janssens wrote: > > > > That is really odd and again suggesting your gnucash is not configured as > > > > per default. We'll have to find out where this comes from... > > > > > > > > Can you provide the result of commands > > > > > > > > alias gnucash > > > > type gnucash > > > > ls -l $(type gnucash) > > > > > > > > dellbert@dellbert:~$ alias gnucash > > > > bash: alias: gnucash: not found > > > > dellbert@dellbert:~$ type gnucash > > > > gnucash is /usr/bin/gnucash > > > > dellbert@dellbert:~$ ls -l $(type gnucash) > > > > ls: cannot access 'gnucash': No such file or directory > > > > ls: cannot access 'is': No such file or directory > > > > -rwxr-xr-x 1 root root 142088 Feb 9 2022 /usr/bin/gnucash > > Ok, these were to ensure our basic assumption is correct. You're effectively > running /usr/bin/gnucash and not some alias or link to another location. > > Also can you start gnucash once as follows: > > > > ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
On 9/11/22 13:02, Geert Janssens wrote: Op zaterdag 10 september 2022 19:49:52 CEST schreef Phil Wolff: > On 9/10/22 08:34, Geert Janssens wrote: > That is really odd and again suggesting your gnucash is not configured as > per default. We'll have to find out where this comes from... > > Can you provide the result of commands > > alias gnucash > type gnucash > ls -l $(type gnucash) > > dellbert@dellbert:~$ alias gnucash > bash: alias: gnucash: not found > dellbert@dellbert:~$ type gnucash > gnucash is /usr/bin/gnucash > dellbert@dellbert:~$ ls -l $(type gnucash) > ls: cannot access 'gnucash': No such file or directory > ls: cannot access 'is': No such file or directory > -rwxr-xr-x 1 root root 142088 Feb 9 2022 /usr/bin/gnucash > Ok, these were to ensure our basic assumption is correct. You're effectively running /usr/bin/gnucash and not some alias or link to another location. > Also can you start gnucash once as follows: > > gnucash --log "gnc.app-utils=debug" > > You can leave out the name to your data file. It will reduce the amount of > messages in the trace file. > > After having run, can you filter the trace file for messages coming from > gnc.app-utils and post them here? > > That's a way to find out where gnucash looks for the config-user.scm file... > > Filtering reduced line count from 943 to 815 > I'm sorry about that. I could have asked to filter more aggressively (but it was very late here when I wrote my last mail). This is the info I was looking for: > [gfec_try_load] looking for /etc/gnucash/config * 09:00:08 DEBUG > > > [gfec_try_load] looking for /home/dellbert/.config/gnucash/config-user.scm > * 09:00:08 DEBUG > > > [gfec_try_load] trying to load > /home/dellbert/.config/gnucash/config-user.scm * 09:00:08 DEBUG > > These lines show that the config-user.scm file is found. No idea why this wouldn't print the value of XDG_DATA_DIRS to your gnucash trace file. But if needed we can debug that later. Let's first follow the other possible clue below. > > As these early queries fail, no migration is started. And in general > considering most queries fail, I think no preferences are ever kept across > gnucash restarts. You could experiment with this by setting a preference to > non-default in gnucash. Restart gnucash and check the preference again ? > > I've done that - any changes I make are lost on a restart. > Ok, that confirms gnucash has an issue with finding settings schemas in some way. > And if so can you use the command > > grep org.gnucash.general $(strings ) > > on each of these (replace with the proper path to the > gschemas.compiled file) > > > > A rather long list containing zero occurences of gnucassh > Unfortunately my command was bad (late night...) :( Can you retry with this command: strings ./share/glib-2.0/schemas/gschemas.compiled | grep org.gnucash.general dellbert@dellbert:/usr$ cd /usr/local dellbert@dellbert:/usr/local$ strings ./share/glib-2.0/schemas/gschemas.compiled | grep org.gnucash.general dellbert@dellbert:/usr/local$ And, for good measure, dellbert@dellbert:/usr/local$ cd /usr dellbert@dellbert:/usr$ strings ./share/glib-2.0/schemas/gschemas.compiled | grep org.gnucash.general (())org.gnucash.general.report /org/gnucash/general/report/ org.gnucash.general.report.pdf-export org.gnucash.general org.gnucash.general.report org.gnucash.general.register /org/gnucash/general/ (i)org.gnucash.general.finance-quote /org/gnucash/general/finance-quote/ org.gnucash.general.register /org/gnucash/general/register/ (s(yau))org.gnucash.general.report.pdf-export (s).path/org/gnucash/general/report/pdf-export/ general/org.gnucash.general dellbert@dellbert:/usr$ dellbert@dellbert:/usr$ cd /usr dellbert@dellbert:/usr$ strings ./share/glib-2.0/schemas/gschemas.compiled | grep org.gnucash.GnuCash.general (b)org.gnucash.GnuCash.general.report /org/gnucash/GnuCash/general/report/ org.gnucash.GnuCash.general.report.pdf-export (i)org.gnucash.GnuCash.general.finance-quote /org/gnucash/GnuCash/general/finance-quote/ org.gnucash.GnuCash.general org.gnucash.GnuCash.general.report org.gnucash.GnuCash.general.register /org/gnucash/GnuCash/general/ (i)org.gnucash.GnuCash.general.report.pdf-export (s).path/org/gnucash/GnuCash/general/report/pdf-export/ general/org.gnucash.GnuCash.general org.gnucash.GnuCash.general.register /org/gnucash/GnuCash/general/register/ dellbert@dellbert:/usr$ Incidentally, I have a Scheduled Transaction due today (9/12) that wasn't automatically created. Using Actions/Scheduled
Re: [GNC] Problems upgrading to 4.8a
Op zaterdag 10 september 2022 19:49:52 CEST schreef Phil Wolff: > On 9/10/22 08:34, Geert Janssens wrote: > That is really odd and again suggesting your gnucash is not configured as > per default. We'll have to find out where this comes from... > > Can you provide the result of commands > > alias gnucash > type gnucash > ls -l $(type gnucash) > > dellbert@dellbert:~$ alias gnucash > bash: alias: gnucash: not found > dellbert@dellbert:~$ type gnucash > gnucash is /usr/bin/gnucash > dellbert@dellbert:~$ ls -l $(type gnucash) > ls: cannot access 'gnucash': No such file or directory > ls: cannot access 'is': No such file or directory > -rwxr-xr-x 1 root root 142088 Feb 9 2022 /usr/bin/gnucash > Ok, these were to ensure our basic assumption is correct. You're effectively running /usr/bin/ gnucash and not some alias or link to another location. > Also can you start gnucash once as follows: > > gnucash --log "gnc.app-utils=debug" > > You can leave out the name to your data file. It will reduce the amount of > messages in the trace file. > > After having run, can you filter the trace file for messages coming from > gnc.app-utils and post them here? > > That's a way to find out where gnucash looks for the config-user.scm file... > > Filtering reduced line count from 943 to 815 > I'm sorry about that. I could have asked to filter more aggressively (but it was very late here when I wrote my last mail). This is the info I was looking for: > [gfec_try_load] looking for /etc/gnucash/config * 09:00:08 DEBUG > > > [gfec_try_load] looking for /home/dellbert/.config/gnucash/config-user.scm > * 09:00:08 DEBUG > > > [gfec_try_load] trying to load > /home/dellbert/.config/gnucash/config-user.scm * 09:00:08 DEBUG > > These lines show that the config-user.scm file is found. No idea why this wouldn't print the value of XDG_DATA_DIRS to your gnucash trace file. But if needed we can debug that later. Let's first follow the other possible clue below. > > As these early queries fail, no migration is started. And in general > considering most queries fail, I think no preferences are ever kept across > gnucash restarts. You could experiment with this by setting a preference to > non-default in gnucash. Restart gnucash and check the preference again ? > > I've done that - any changes I make are lost on a restart. > Ok, that confirms gnucash has an issue with finding settings schemas in some way. > And if so can you use the command ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
Op zaterdag 10 september 2022 16:36:03 CEST schreef Phil Wolff: > On 9/9/22 16:14, Geert Janssens wrote: > > Op vrijdag 9 september 2022 22:19:08 CEST schreef Phil Wolff: > > dellbert@dellbert:~$ gsettings get org.gnucash.GnuCash.general.register > > > > double-line-mode true > > > > dellbert@dellbert:~$ > > > > > > > > But when I run gnucash all of my registers are single-line. > > The only explanation I can come up with is that gnucash runs in a different > environment than gsettings. > > > > > How do you start gnucash exactly ? From the command line or from the Ubuntu > menus ? > > I start by clicking on a Desktop icon. If I use the .desktop file from the > package manager installation which contains the line "Exec=gnucash %f," I > get a window titled "Unsaved Book - GnuCash" and I have to use File/Open to > access my data file, so instead I use a copy of the .desktop file with the > modified line "Exec=gnucash > /home/dellbert/Documents/gnucash/Household.db.gnucash" to open the data > file directly. > > > > > > And to test for the most relevant environment variable wrt to settings, can > you add create a file named "config-user.scm" in $HOME/.config/gnucash > > with this contents: > > (use-modules (gnucash utilities)) > (gnc:warn "XDG__DATA_DIRS=" (getenv "XDG_DATA_DIRS")) > > The next time you run gnucash this will add a line at the top of your > gnucash.trace file showing the value of environment variable > "XDG_DATA_DIRS". > > dellbert@dellbert:~$ cat ~/.config/gnucash/config-user.scm > (use-modules (gnucash utilities)) > (gnc:warn "XDG__DATA_DIRS=" (getenv "XDG_DATA_DIRS")) > dellbert@dellbert:~$ cat /tmp/gnucash.trace > cat: /tmp/gnucash.trace: No such file or directory > > < run gnucash > > > dellbert@dellbert:~$ cat /tmp/gnucash.trace > * 11:14:57 ERROR g_settings_new_full: assertion 'schema != NULL' > failed * 11:14:57 WARN > [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown > gsettings schema org.gnucash.GnuCash.general * 11:14:57 ERROR > GVariant* gnc_gsettings_get_user_value(const gchar*, const > gchar*): assertion 'G_IS_SETTINGS (settings_ptr)' failed * 11:14:57 ERROR > g_settings_new_full: assertion 'schema != NULL' failed * > 11:14:57 WARN [gnc_gsettings_get_settings_ptr()] > Ignoring attempt to access unknown gsettings schema org.gnucash.general * > 11:14:57 ERROR GVariant* gnc_gsettings_get_user_value(const > gchar*, const gchar*): assertion 'G_IS_SETTINGS (settings_ptr)' failed > 14:57 WARN [gnc_gsettings_get_settings_ptr()] > Ignoring attempt to access unknown gsettings schema org.gnucash.general > > > * ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
On 9/9/22 16:14, Geert Janssens wrote: Op vrijdag 9 september 2022 22:19:08 CEST schreef Phil Wolff: > dellbert@dellbert:~$ gsettings get org.gnucash.GnuCash.general.register > double-line-mode true > dellbert@dellbert:~$ > > But when I run gnucash all of my registers are single-line. > > The only explanation I can come up with is that gnucash runs in a different environment than gsettings. How do you start gnucash exactly ? From the command line or from the Ubuntu menus ? I start by clicking on a Desktop icon. If I use the .desktop file from the package manager installation which contains the line "Exec=gnucash %f," I get a window titled "Unsaved Book - GnuCash" and I have to use File/Open to access my data file, so instead I use a copy of the .desktop file with the modified line "Exec=gnucash /home/dellbert/Documents/gnucash/Household.db.gnucash" to open the data file directly. And to test for the most relevant environment variable wrt to settings, can you add create a file named "config-user.scm" in $HOME/.config/gnucash with this contents: (use-modules (gnucash utilities)) (gnc:warn "XDG__DATA_DIRS=" (getenv "XDG_DATA_DIRS")) The next time you run gnucash this will add a line at the top of your gnucash.trace file showing the value of environment variable "XDG_DATA_DIRS". dellbert@dellbert:~$ cat ~/.config/gnucash/config-user.scm (use-modules (gnucash utilities)) (gnc:warn "XDG__DATA_DIRS=" (getenv "XDG_DATA_DIRS")) dellbert@dellbert:~$ cat /tmp/gnucash.trace cat: /tmp/gnucash.trace: No such file or directory < run gnucash > dellbert@dellbert:~$ cat /tmp/gnucash.trace * 11:14:57 ERROR g_settings_new_full: assertion 'schema != NULL' failed * 11:14:57 WARN [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown gsettings schema org.gnucash.GnuCash.general * 11:14:57 ERROR GVariant* gnc_gsettings_get_user_value(const gchar*, const gchar*): assertion 'G_IS_SETTINGS (settings_ptr)' failed * 11:14:57 ERROR g_settings_new_full: assertion 'schema != NULL' failed * 11:14:57 WARN [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown gsettings schema org.gnucash.general * 11:14:57 ERROR GVariant* gnc_gsettings_get_user_value(const gchar*, const gchar*): assertion 'G_IS_SETTINGS (settings_ptr)' failed 14:57 WARN [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown gsettings schema org.gnucash.general * I've started gnucash using both .desktop files as described above, with identical results - the line you expected at the top of the file is not there. Is it expected that gnucash is attempting to read both org.gnucash.GnuCash.general and org.gnucash.general? I'd like to know what this is. And can you compare it to what XDG_DATA_DIRS is set to in your terminal ? At login: dellbert@dellbert:~$ echo $XDG_DATA_DIRS /usr/share/ubuntu-xorg:/usr/share/gnome:/home/dellbert/.local/share/fla tpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share/:/us r/share/:/var/lib/snapd/desktop Regards, Geert ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
Op vrijdag 9 september 2022 22:19:08 CEST schreef Phil Wolff: > dellbert@dellbert:~$ gsettings get org.gnucash.GnuCash.general.register > double-line-mode true > dellbert@dellbert:~$ > > But when I run gnucash all of my registers are single-line. > > The only explanation I can come up with is that gnucash runs in a different environment than gsettings. How do you start gnucash exactly ? From the command line or from the Ubuntu menus ? And to test for the most relevant environment variable wrt to settings, can you add create a file named "config-user.scm" in $HOME/.config/gnucash with this contents: (use-modules (gnucash utilities)) (gnc:warn "XDG__DATA_DIRS=" (getenv "XDG_DATA_DIRS")) The next time you run gnucash this will add a line at the top of your gnucash.trace file showing the value of environment variable "XDG_DATA_DIRS". I'd like to know what this is. And can you compare it to what XDG_DATA_DIRS is set to in your terminal ? Regards, Geert ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
On 9/9/22 09:17, Geert Janssens wrote: Weird, my answer got stripped from the mail as it returned from the mailing list... I'll send again below for reference. Geert Op vrijdag 9 september 2022 17:23:36 CEST schreef Phil Wolff: > Schema files should be compiled at install time before gnucash can use them. > That's more or less the answer to your question whether they should be > created at install time. Perhaps this went wrong for some reason. > > > > > Can you run the following command to test this? > > strings /usr/share/glib-2.0/schemas/gschemas.compiled | grep > org.gnucash.general > > > > > Just post the output here. > > > > [1]dellbert@dellbert:/usr/local/share/glib-2.0/schemas$ strings > /usr/share/glib-2.0/schemas/gschemas.compiled | grep org.gnucash.general > (())org.gnucash.general.report > /org/gnucash/general/report/ > org.gnucash.general.report.pdf-export > org.gnucash.general > org.gnucash.general.report > org.gnucash.general.register > /org/gnucash/general/ > (i)org.gnucash.general.finance-quote > /org/gnucash/general/finance-quote/ > org.gnucash.general.register > /org/gnucash/general/register/ > (s(yau))org.gnucash.general.report.pdf-export > (s).path/org/gnucash/general/report/pdf-export/ > general/org.gnucash.general > [2]dellbert@dellbert:/usr/local/share/glib-2.0/schemas$ > The output is slightly different from mine, but that's not abnormal. Another test would be to run gsettings list-schemas | grep org.gnucash.general gsettings is the interface gnucash uses to access the preferences, so contrary to dconf-editor this should use the same code internally as gnucash. dellbert@dellbert:~$ gsettings get org.gnucash.GnuCash.general.register double-line-mode true dellbert@dellbert:~$ But when I run gnucash all of my registers are single-line. Does this command return the org.gnucash.general schema (together with a few others) ? Lastly to verify if compilation was completely successful you can also run sudo glib-compile-schemas --strict /usr/share/glib-2.0/schemas And check the result for errors. If compilation didn't result in any errors you could recheck if gnucash now works without the GSettings warnings in gnucash.trace. Regards, Geert -- What was that about a rising tide lifting all boats? What if you don't have a boat? — Eugene Robinson References 1. mailto:dellbert@dellbert:/usr/local/share/glib-2.0/schemas$ 2. mailto:dellbert@dellbert:/usr/local/share/glib-2.0/schemas$ ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
On 9/9/22 08:34, Geert Janssens wrote: Op vrijdag 9 september 2022 17:23:36 CEST schreef Phil Wolff: > On 9/9/22 07:49, Geert Janssens wrote: > > > Hi Phill, > > > > > I'm trying to remember how everything panned out exactly back when 4.8 was > released. There was a critical issue with the preference migration causing > gnucash to crash on startup in certain situations. This has been fixed in > 4.8a, which is what you have installed. > > > > > It is slightly odd that gnucash itself fails to load these schema files > while dconf-editor sees them just fine. But I don't know the internals of > dconf-editor so perhaps it uses a different method of scanning for schema > files than gnucash does. > > > > > As to your feedback: > > The gschema files you have found are the correct ones and it's good the old > ones are not present anywhere on the system. > > > > > The list of missing gsettings schemas you report is probably not exhaustive. > The warnings will only be emitted when the schema is queried. Not all > preferences are queried at once at startup. > > > > > What we can state is that the source files for these schema definitions are > installed. That the list of gschema files you report. > > It's worth to check if the missing schemas are actually defined in these > source files. For exmple the schema "org.gnucash.general" should be found > in > > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.deprecated.gschema.xml > > Can you verify this ? > > > > > Schema files should be compiled at install time before gnucash can use them. > That's more or less the answer to your question whether they should be > created at install time. Perhaps this went wrong for some reason. > > > > > Can you run the following command to test this? > > strings /usr/share/glib-2.0/schemas/gschemas.compiled | grep > org.gnucash.general > > > > > Just post the output here. > > > > [1]dellbert@dellbert:/usr/local/share/glib-2.0/schemas$ strings > /usr/share/glib-2.0/schemas/gschemas.compiled | grep org.gnucash.general > (())org.gnucash.general.report > /org/gnucash/general/report/ > org.gnucash.general.report.pdf-export > org.gnucash.general > org.gnucash.general.report > org.gnucash.general.register > /org/gnucash/general/ > (i)org.gnucash.general.finance-quote > /org/gnucash/general/finance-quote/ > org.gnucash.general.register > /org/gnucash/general/register/ > (s(yau))org.gnucash.general.report.pdf-export > (s).path/org/gnucash/general/report/pdf-export/ > general/org.gnucash.general > [2]dellbert@dellbert:/usr/local/share/glib-2.0/schemas$ > > The output is slightly different from mine, but that's not abnormal. Another test would be to run gsettings list-schemas | grep org.gnucash.general gsettings is the interface gnucash uses to access the preferences, so contrary to dconf-editor this should use the same code internally as gnucash. Does this command return the org.gnucash.general schema (together with a few others) ? dellbert@dellbert:~$ gsettings list-schemas | grep org.gnucash.general org.gnucash.general org.gnucash.general.finance-quote org.gnucash.general.register org.gnucash.general.report org.gnucash.general.report.pdf-export dellbert@dellbert:~$ Lastly to verify if compilation was completely successful you can also run sudo glib-compile-schemas --strict /usr/share/glib-2.0/schemas And check the result for errors. If compilation didn't result in any errors you could recheck if gnucash now works without the GSettings warnings in gnucash.trace. dellbert@dellbert:~$ sudo glib-compile-schemas --strict /usr/share/glib-2.0/schemas [sudo] password for dellbert: dellbert@dellbert:~$ rm /tmp/gnucash.trace dellbert@dellbert:~$ rm -v /tmp/gnucash.trace rm: cannot remove '/tmp/gnucash.trace': No such file or directory dellbert@dellbert:~$ ll /tmp/gnucash.trace -rw--- 1 dellbert dellbert 294114 Sep 9 11:15 /tmp/gnucash.trace dellbert@dellbert:~$ cat /tmp/gnucash.trace * 11:14:57 ERROR g_settings_new_full: assertion 'schema != NULL' failed * 11:14:57 WARN [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown gsettings schema org.gnucash.GnuCash.general * 11:14:57 ERROR GVariant* gnc_gsettings_get_user_value(const gchar*, const gchar*): assertion 'G_IS_SETTINGS (settings_ptr)' failed * 11:14:57 ERROR g_settings_new_full: assertion 'schema != NULL' failed * 11:14:57 WARN [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown gsettings
Re: [GNC] Problems upgrading to 4.8a
Weird, my answer got stripped from the mail as it returned from the mailing list... I'll send again below for reference. Geert Op vrijdag 9 september 2022 17:23:36 CEST schreef Phil Wolff: > Schema files should be compiled at install time before gnucash can use them. > That's more or less the answer to your question whether they should be > created at install time. Perhaps this went wrong for some reason. > > > > > Can you run the following command to test this? > > strings /usr/share/glib-2.0/schemas/gschemas.compiled | grep > org.gnucash.general > > > > > Just post the output here. > > > > dellbert@dellbert:/usr/local/share/glib-2.0/schemas$ strings > /usr/share/glib-2.0/schemas/gschemas.compiled | grep org.gnucash.general > (())org.gnucash.general.report > /org/gnucash/general/report/ > org.gnucash.general.report.pdf-export > org.gnucash.general > org.gnucash.general.report > org.gnucash.general.register > /org/gnucash/general/ > (i)org.gnucash.general.finance-quote > /org/gnucash/general/finance-quote/ > org.gnucash.general.register > /org/gnucash/general/register/ > (s(yau))org.gnucash.general.report.pdf-export > (s).path/org/gnucash/general/report/pdf-export/ > general/org.gnucash.general > dellbert@dellbert:/usr/local/share/glib-2.0/schemas$ > The output is slightly different from mine, but that's not abnormal. Another test would be to run gsettings list-schemas | grep org.gnucash.general gsettings is the interface gnucash uses to access the preferences, so contrary to dconf-editor this should use the same code internally as gnucash. Does this command return the org.gnucash.general schema (together with a few others) ? Lastly to verify if compilation was completely successful you can also run sudo glib-compile-schemas --strict /usr/share/glib-2.0/schemas And check the result for errors. If compilation didn't result in any errors you could recheck if gnucash now works without the GSettings warnings in gnucash.trace. Regards, Geert ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
Op vrijdag 9 september 2022 17:23:36 CEST schreef Phil Wolff: > On 9/9/22 07:49, Geert Janssens wrote: > > > Hi Phill, > > > > > I'm trying to remember how everything panned out exactly back when 4.8 was > released. There was a critical issue with the preference migration causing > gnucash to crash on startup in certain situations. This has been fixed in > 4.8a, which is what you have installed. > > > > > It is slightly odd that gnucash itself fails to load these schema files > while dconf-editor sees them just fine. But I don't know the internals of > dconf-editor so perhaps it uses a different method of scanning for schema > files than gnucash does. > > > > > As to your feedback: > > The gschema files you have found are the correct ones and it's good the old > ones are not present anywhere on the system. > > > > > The list of missing gsettings schemas you report is probably not exhaustive. > The warnings will only be emitted when the schema is queried. Not all > preferences are queried at once at startup. > > > > > What we can state is that the source files for these schema definitions are > installed. That the list of gschema files you report. > > It's worth to check if the missing schemas are actually defined in these > source files. For exmple the schema "org.gnucash.general" should be found > in > > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.deprecated.gschema.xml > > Can you verify this ? > > > > > Schema files should be compiled at install time before gnucash can use them. > That's more or less the answer to your question whether they should be > created at install time. Perhaps this went wrong for some reason. > > > > > Can you run the following command to test this? > > strings /usr/share/glib-2.0/schemas/gschemas.compiled | grep > org.gnucash.general > > > > > Just post the output here. > > ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
On 9/9/22 07:49, Geert Janssens wrote: Hi Phill, I'm trying to remember how everything panned out exactly back when 4.8 was released. There was a critical issue with the preference migration causing gnucash to crash on startup in certain situations. This has been fixed in 4.8a, which is what you have installed. It is slightly odd that gnucash itself fails to load these schema files while dconf-editor sees them just fine. But I don't know the internals of dconf-editor so perhaps it uses a different method of scanning for schema files than gnucash does. As to your feedback: The gschema files you have found are the correct ones and it's good the old ones are not present anywhere on the system. The list of missing gsettings schemas you report is probably not exhaustive. The warnings will only be emitted when the schema is queried. Not all preferences are queried at once at startup. What we can state is that the source files for these schema definitions are installed. That the list of gschema files you report. It's worth to check if the missing schemas are actually defined in these source files. For exmple the schema "org.gnucash.general" should be found in /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.deprecated.gschema.xml Can you verify this ? Schema files should be compiled at install time before gnucash can use them. That's more or less the answer to your question whether they should be created at install time. Perhaps this went wrong for some reason. Can you run the following command to test this? strings /usr/share/glib-2.0/schemas/gschemas.compiled | grep org.gnucash.general Just post the output here. [1]dellbert@dellbert:/usr/local/share/glib-2.0/schemas$ strings /usr/share/glib-2.0/schemas/gschemas.compiled | grep org.gnucash.general (())org.gnucash.general.report /org/gnucash/general/report/ org.gnucash.general.report.pdf-export org.gnucash.general org.gnucash.general.report org.gnucash.general.register /org/gnucash/general/ (i)org.gnucash.general.finance-quote /org/gnucash/general/finance-quote/ org.gnucash.general.register /org/gnucash/general/register/ (s(yau))org.gnucash.general.report.pdf-export (s).path/org/gnucash/general/report/pdf-export/ general/org.gnucash.general [2]dellbert@dellbert:/usr/local/share/glib-2.0/schemas$ Regards, Geert Op vrijdag 9 september 2022 16:12:46 CEST schreef Phil Wolff: > On 9/8/22 13:28, Geert Janssens wrote: > > Op woensdag 7 september 2022 21:54:17 CEST schreef Phil Wolff: > > Geert ~ > > > > > > > > Before doing anything, I looked at the current trace file. Lots of WARNs > > and > > > > ERRORs like > > > > > > > > * 12:03:55 WARN > > > > [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown > > > > gsettings schema org.gnucash.GnuCash.general * 12:03:55 ERROR > > > > gboolean gnc_gsettings_get_bool(const gchar*, const > > > > gchar*): assertion 'G_IS_SETTINGS (settings_ptr)' failed > > This is probably the core of your problem. For some reason gnucash can't > find the schema definitions for our preferences. If I remember correctly in > most cases this is because it finds another location with the old schemas > (starting with org.gnucash and no extra .GnuCash in the path). The most > common candidate for this would be in /usr/local/share/glib-2.0/schemas/ > > Can you search your system for other such files ? > > > > > Regards, > > > > > Geert > > > > > i repeated the search using "sudo find / -xdev -name > org.gnucash.\*.gschema.xml" and got the same list as appears below this > comment. I then copied all of the org.gnucash files from > /usr/share/glib-2.0/schemas to /usr/local/share/glib-2.0/schema, deleted > /tmp/gnucash.trace (just to be sure), ran gnucash, and looked at the new > trace file. Same story. So I looked in the package manager's record of > files that were originally installed. That list exactly matches the results > of the "find" operation below. > > So I took a look for schema files: > > > > > > > > dellbert@dellbert:~$ sudo find / -xdev -name > > > > org.gnucash.GnuCash\*.gschema.xml > > > > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.business.gsc hema.x > > m > > > > l /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.totd.gschema .xml > > > > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.import.csv.g schema > > .
Re: [GNC] Problems upgrading to 4.8a
Hi Phill, I'm trying to remember how everything panned out exactly back when 4.8 was released. There was a critical issue with the preference migration causing gnucash to crash on startup in certain situations. This has been fixed in 4.8a, which is what you have installed. It is slightly odd that gnucash itself fails to load these schema files while dconf-editor sees them just fine. But I don't know the internals of dconf-editor so perhaps it uses a different method of scanning for schema files than gnucash does. As to your feedback: The gschema files you have found are the correct ones and it's good the old ones are not present anywhere on the system. The list of missing gsettings schemas you report is probably not exhaustive. The warnings will only be emitted when the schema is queried. Not all preferences are queried at once at startup. What we can state is that the source files for these schema definitions are installed. That the list of gschema files you report. It's worth to check if the missing schemas are actually defined in these source files. For exmple the schema "org.gnucash.general" should be found in /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.deprecated.gschema.xml Can you verify this ? Schema files should be compiled at install time before gnucash can use them. That's more or less the answer to your question whether they should be created at install time. Perhaps this went wrong for some reason. Can you run the following command to test this? strings /usr/share/glib-2.0/schemas/gschemas.compiled | grep org.gnucash.general Just post the output here. Regards, Geert Op vrijdag 9 september 2022 16:12:46 CEST schreef Phil Wolff: > On 9/8/22 13:28, Geert Janssens wrote: > > Op woensdag 7 september 2022 21:54:17 CEST schreef Phil Wolff: > > Geert ~ > > > > > > > > Before doing anything, I looked at the current trace file. Lots of WARNs > > and > > > > ERRORs like > > > > > > > > * 12:03:55 WARN > > > > [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown > > > > gsettings schema org.gnucash.GnuCash.general * 12:03:55 ERROR > > > > gboolean gnc_gsettings_get_bool(const gchar*, const > > > > gchar*): assertion 'G_IS_SETTINGS (settings_ptr)' failed > > This is probably the core of your problem. For some reason gnucash can't > find the schema definitions for our preferences. If I remember correctly in > most cases this is because it finds another location with the old schemas > (starting with org.gnucash and no extra .GnuCash in the path). The most > common candidate for this would be in /usr/local/share/glib-2.0/schemas/ > > Can you search your system for other such files ? > ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
On 9/8/22 13:28, Geert Janssens wrote: Op woensdag 7 september 2022 21:54:17 CEST schreef Phil Wolff: > Geert ~ > > Before doing anything, I looked at the current trace file. Lots of WARNs and > ERRORs like > > * 12:03:55 WARN > [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown > gsettings schema org.gnucash.GnuCash.general * 12:03:55 ERROR > gboolean gnc_gsettings_get_bool(const gchar*, const > gchar*): assertion 'G_IS_SETTINGS (settings_ptr)' failed > This is probably the core of your problem. For some reason gnucash can't find the schema definitions for our preferences. If I remember correctly in most cases this is because it finds another location with the old schemas (starting with org.gnucash and no extra .GnuCash in the path). The most common candidate for this would be in /usr/local/share/glib-2.0/schemas/ Can you search your system for other such files ? Regards, Geert i repeated the search using "sudo find / -xdev -name org.gnucash.\*.gschema.xml" and got the same list as appears below this comment. I then copied all of the org.gnucash files from /usr/share/glib-2.0/schemas to /usr/local/share/glib-2.0/schema, deleted /tmp/gnucash.trace (just to be sure), ran gnucash, and looked at the new trace file. Same story. So I looked in the package manager's record of files that were originally installed. That list exactly matches the results of the "find" operation below. > So I took a look for schema files: > > dellbert@dellbert:~$ sudo find / -xdev -name > org.gnucash.GnuCash\*.gschema.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.business.gsc hema.xm > l /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.totd.gschema .xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.import.csv.g schema. > xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.general.finance-quot e.gsche > ma.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.window.pages.gschema .xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.warnings.gschema.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.history.gschema.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.reconcile.gs chema.x > ml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.export.csv.g schema. > xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.gschema.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.deprecated.gschema.x ml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.import.hbci. gschema > .xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.flicker.gsch ema.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.checkprintin g.gsche > ma.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.import.gener ic.gsch > ema.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.commodities. gschema > .xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.sxs.gschema. xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.import.ofx.g schema. > xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.gschema.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.import.qif.g schema.x > ml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.window.pages.account .tree.g > schema.xml dellbert@dellbert:~$ > > I extracted from the trace files all of the lines containing "Ignoring attempt to access unknown gsettings schema" and eliminated the duplicates. Here are the missing schemas: * 06:30:51 WARN [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown gsettings schema org.gnucash.general * 06:30:56 WARN [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown gsettings schema org.gnucash.GnuCash.dialogs.business.bill * 06:30:52 WARN [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown gsettings schema org.gnucash.GnuCash.dialogs.business.invoice * 06:30:51 WARN [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown gsettings schema org.gnucash.GnuCash.dialogs.import.hbci * 06:30:52 WARN [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown gsettings schema org.gnucash.GnuCash.dialogs.open-save * 06:30:56 WARN [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown gsettings schema org.gnucash.GnuCash.dialogs.sxs.since-last-run * 06:30:51 WARN [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown gsettings schema
Re: [GNC] Problems upgrading to 4.8a
Op woensdag 7 september 2022 23:06:50 CEST schreef Phil Wolff: > /org/gnucash/GnuCash/general/prefs-version Use default value is set, Current > value = Default value, Default = 0 > > If it matters, /org/gnucash/general/prefs-version Use default value is not > set, Current value = 308 > Yes, considering gnucash can't find the proper schema files, it will also never change any preference. So the first one (using the new preference paths) is expected to be default still and the second one (using the old preference paths) is expected to be what your previous gnucash version set it to. Regards, Geert ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
Op woensdag 7 september 2022 21:54:17 CEST schreef Phil Wolff: > Geert ~ > > Before doing anything, I looked at the current trace file. Lots of WARNs and > ERRORs like > > * 12:03:55 WARN > [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown > gsettings schema org.gnucash.GnuCash.general * 12:03:55 ERROR > gboolean gnc_gsettings_get_bool(const gchar*, const > gchar*): assertion 'G_IS_SETTINGS (settings_ptr)' failed > This is probably the core of your problem. For some reason gnucash can't find the schema definitions for our preferences. If I remember correctly in most cases this is because it finds another location with the old schemas (starting with org.gnucash and no extra .GnuCash in the path). The most common candidate for this would be in /usr/local/share/glib-2.0/ schemas/ Can you search your system for other such files ? Regards, Geert > So I took a look for schema files: > > dellbert@dellbert:~$ sudo find / -xdev -name > org.gnucash.GnuCash\*.gschema.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.business.gschema.xm > l /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.totd.gschema.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.import.csv.gschema. > xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.general.finance-quote.gsche > ma.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.window.pages.gschema.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.warnings.gschema.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.history.gschema.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.reconcile.gschema.x > ml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.export.csv.gschema. > xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.gschema.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.deprecated.gschema.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.import.hbci.gschema > .xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.flicker.gschema.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.checkprinting.gsche > ma.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.import.generic.gsch > ema.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.commodities.gschema > .xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.sxs.gschema.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.import.ofx.gschema. > xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.gschema.xml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.import.qif.gschema.x > ml > /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.window.pages.account.tree.g > schema.xml dellbert@dellbert:~$ > > > Should there be more? > > Phil ~ > > > > On 9/7/22 11:59, Geert Janssens wrote: > > > Hi Phil, > > Op woensdag 7 september 2022 18:50:16 CEST schreef Phil Wolff: > > > "Backup files" are autogenerated by gnucash and - as the name suggests - ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
/org/gnucash/GnuCash/general/prefs-version Use default value is set, Current value = Default value, Default = 0 If it matters, /org/gnucash/general/prefs-version Use default value is not set, Current value = 308 On 9/7/22 11:59, Geert Janssens wrote: Hi Phil, Op woensdag 7 september 2022 18:50:16 CEST schreef Phil Wolff: > > "Backup files" are autogenerated by gnucash and - as the name suggests - > > contain backups of your accounting data. They are generated in the same > > directory as your "Data file" and have as file name > > > > ..gnucash > > Don't see any of these You may have disabled backup file generation. > > "Saved reports" is a bit of an outlier. It is a single file that contains > > all "Saved report configurations" you have created in gnucash. For > > historical reasons this file is shared by all your "Data files". It is > > found in GNC_DATA_HOME and is called saved-reports- > > 3 files; -2.8, > -2.8~ and -2.8-backup suffixes. If the 2.8 is the GNC version, that means > that my recollection of seeing "1.something" in Synaptic is faulty. > 2.8 is the compatibility version and actually refers to gnucash 3.x (a small historical hiccup). > A few final remarks: > > * You never mentioned this, but normally gnucash would pop up a message when > it has attempted this migration. Did you actually get this message ? > > No. If the migration occurred during the Ubuntu 20.04 -> 22.04 upgrade, I > would not have seen it go by in the torrent generated by the upgrader. If > it showed such a message the first time I ran gnucash after the upgrade, I > missed seeing it. > It should be displayed the first time you run gnucash after the upgrade. So you may have missed it. > > * You mentioned you were migrating from gnucash 1.x. Was that really the > previous version of gnucash you ran on your system, or just that the data > file you now opened was last opened with gnucash 1.x ? Somewhere in the 2.x > series we switched backends for these preferences (from the old GConf to > the newer DConf). Migration between these two backends has been done > somewhere between 2.x and 3.x, but that migration code is no longer present > in gnucash 4.x. So if you really never ran gnucash 2.x and 3.x, this means > all your preferences have been reset to default. In that case you probably > want to go through your preferences again in "Edit->Preferences" to check > if they are still as you want them to be. > > That is what I found late yesterday. I had reported that my Scheduled > Transactions were not being posted, and John Ralls pointed me to the ST > section in Preferences. Sure enough, none of the boxes were checked, and > manually running Actions/Scheduled Transactions/Since Last Run entered all > of the delinquents. However when I called up dconf-editor, I found a folder > /org/gnucash with 7 subfolders, one of which is GnuCash. Oddly, GnuCash > contains 6 subfolders named the same as ones in its parent, and both sets > of folders contain folders /dialogs/scheduled-trans/since-last-run with > binary keys show-file-at-open and show-notify-window-at-file-open that are > enabled. It appears that GConf did get migrated to DConf but gnucash isn't > reading dconf. Considering you were previously on Ubuntu 20.04LTS the most recent gnucash on that system was 3.8b. The 1: in the package version number is a specific packaging prefix. I used to know what it was about. I do know it's not relevant to determine the actual gnucash version. So you're good. And indeed the migration to dconf has already happened by then. Unfortunately you are caught in yet another migration, which happens when upgrading to anything more recent than gnucash 4.6. For compatibility reasons with Gtk and flatpak we were forced to move our dconf settings from /org/gnucash to /org/gnucash/GnuCash That's why you find both trees when looking with dconf-editor. For some reason this migration doesn't seem to have run for your system and hence the preferences are not copied from the old to the new location. I don't know why that failed. This migration is only attempted once by default and failures are logged in the gnucash trace file. Unfortunately if you rerun gnucash after this first attempt, the trace file gets overwritten. You could try to retrigger this migration by manipulating dconf like so: * Open dconf-editor * Navigate to /org/gnucash/GnuCash/general * Select "prefs-version" * In the details that appear, select "Use Default" * Click "Apply" bottom right Next time you start gnucash the preferences migration logic should rerun. You can then check
Re: [GNC] Problems upgrading to 4.8a
Geert ~ Before doing anything, I looked at the current trace file. Lots of WARNs and ERRORs like * 12:03:55 WARN [gnc_gsettings_get_settings_ptr()] Ignoring attempt to access unknown gsettings schema org.gnucash.GnuCash.general * 12:03:55 ERROR gboolean gnc_gsettings_get_bool(const gchar*, const gchar*): assertion 'G_IS_SETTINGS (settings_ptr)' failed So I took a look for schema files: dellbert@dellbert:~$ sudo find / -xdev -name org.gnucash.GnuCash\*.gschema.xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.business.gschem a.xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.totd.gschema.xm l /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.import.csv.gsch ema.xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.general.finance-quote.g schema.xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.window.pages.gschema.xm l /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.warnings.gschema.xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.history.gschema.xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.reconcile.gsche ma.xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.export.csv.gsch ema.xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.gschema.xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.deprecated.gschema.xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.import.hbci.gsc hema.xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.flicker.gschema .xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.checkprinting.g schema.xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.import.generic. gschema.xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.commodities.gsc hema.xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.sxs.gschema.xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.import.ofx.gsch ema.xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.gschema.xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.dialogs.import.qif.gsch ema.xml /usr/share/glib-2.0/schemas/org.gnucash.GnuCash.window.pages.account.tr ee.gschema.xml dellbert@dellbert:~$ Should there be more? Phil ~ On 9/7/22 11:59, Geert Janssens wrote: Hi Phil, Op woensdag 7 september 2022 18:50:16 CEST schreef Phil Wolff: > > "Backup files" are autogenerated by gnucash and - as the name suggests - > > contain backups of your accounting data. They are generated in the same > > directory as your "Data file" and have as file name > > > > ..gnucash > > Don't see any of these You may have disabled backup file generation. > > "Saved reports" is a bit of an outlier. It is a single file that contains > > all "Saved report configurations" you have created in gnucash. For > > historical reasons this file is shared by all your "Data files". It is > > found in GNC_DATA_HOME and is called saved-reports- > > 3 files; -2.8, > -2.8~ and -2.8-backup suffixes. If the 2.8 is the GNC version, that means > that my recollection of seeing "1.something" in Synaptic is faulty. > 2.8 is the compatibility version and actually refers to gnucash 3.x (a small historical hiccup). > A few final remarks: > > * You never mentioned this, but normally gnucash would pop up a message when > it has attempted this migration. Did you actually get this message ? > > No. If the migration occurred during the Ubuntu 20.04 -> 22.04 upgrade, I > would not have seen it go by in the torrent generated by the upgrader. If > it showed such a message the first time I ran gnucash after the upgrade, I > missed seeing it. > It should be displayed the first time you run gnucash after the upgrade. So you may have missed it. > > * You mentioned you were migrating from gnucash 1.x. Was that really the > previous version of gnucash you ran on your system, or just that the data > file you now opened was last opened with gnucash 1.x ? Somewhere in the 2.x > series we switched backends for these preferences (from the old GConf to > the newer DConf). Migration between these two backends has been done > somewhere between 2.x and 3.x, but that migration code is no longer present > in gnucash 4.x. So if you really never ran gnucash 2.x and 3.x, this means > all your preferences have been reset to default. In that case you probably > want to go through your preferences again in "Edit->Preferences" to check > if they are still as you want them to be. > > That is what I found late yesterday. I had reported that my Scheduled > Transactions were not being posted, and John Ralls pointed me to the ST > section in Preferences. Sure enough, none of the boxes were checked, and > manually
Re: [GNC] Problems upgrading to 4.8a
Hi Phil, Op woensdag 7 september 2022 18:50:16 CEST schreef Phil Wolff: > > "Backup files" are autogenerated by gnucash and - as the name suggests - > > contain backups of your accounting data. They are generated in the same > > directory as your "Data file" and have as file name > > > > ..gnucash > > Don't see any of these You may have disabled backup file generation. > > "Saved reports" is a bit of an outlier. It is a single file that contains > > all "Saved report configurations" you have created in gnucash. For > > historical reasons this file is shared by all your "Data files". It is > > found in GNC_DATA_HOME and is called saved-reports- > > 3 files; -2.8, > -2.8~ and -2.8-backup suffixes. If the 2.8 is the GNC version, that means > that my recollection of seeing "1.something" in Synaptic is faulty. > 2.8 is the compatibility version and actually refers to gnucash 3.x (a small historical hiccup). > A few final remarks: > > * You never mentioned this, but normally gnucash would pop up a message when > it has attempted this migration. Did you actually get this message ? > > No. If the migration occurred during the Ubuntu 20.04 -> 22.04 upgrade, I > would not have seen it go by in the torrent generated by the upgrader. If > it showed such a message the first time I ran gnucash after the upgrade, I > missed seeing it. > It should be displayed the first time you run gnucash after the upgrade. So you may have missed it. > > * You mentioned you were migrating from gnucash 1.x. Was that really the > previous version of gnucash you ran on your system, or just that the data > file you now opened was last opened with gnucash 1.x ? Somewhere in the 2.x > series we switched backends for these preferences (from the old GConf to > the newer DConf). Migration between these two backends has been done > somewhere between 2.x and 3.x, but that migration code is no longer present > in gnucash 4.x. So if you really never ran gnucash 2.x and 3.x, this means > all your preferences have been reset to default. In that case you probably > want to go through your preferences again in "Edit->Preferences" to check > if they are still as you want them to be. > > That is what I found late yesterday. I had reported that my Scheduled > Transactions were not being posted, and John Ralls pointed me to the ST > section in Preferences. Sure enough, none of the boxes were checked, and > manually running Actions/Scheduled Transactions/Since Last Run entered all > of the delinquents. However when I called up dconf-editor, I found a folder > /org/gnucash with 7 subfolders, one of which is GnuCash. Oddly, GnuCash > contains 6 subfolders named the same as ones in its parent, and both sets > of folders contain folders /dialogs/scheduled-trans/since-last-run with > binary keys show-file-at-open and show-notify-window-at-file-open that are > enabled. It appears that GConf did get migrated to DConf but gnucash isn't > reading dconf. Considering you were previously on Ubuntu 20.04LTS the most recent gnucash on that system was 3.8b. The 1: in the package version number is a specific packaging prefix. I used to know what it was about. I do know it's not relevant to determine the actual gnucash version. So you're good. And indeed the migration to dconf has already happened by then. ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
Geert ~ On 9/7/22 00:45, Geert Janssens wrote: Phill, "Data files" are the ones containing your actual accounting data. These files normally have file extension ".gnucash". If you have these files from the 1.x period they may also have no extension at all or the ".xacc" extension. This .gnucash file is what I refer to as "data file." "Backup files" are autogenerated by gnucash and - as the name suggests - contain backups of your accounting data. They are generated in the same directory as your "Data file" and have as file name ..gnucash Don't see any of these "Log files" in this context are also auto generated by gnucash and contain a transaction log. That is it logs all changes made to transactions in chronological order between file saves. They can be used to replay such changes on top of a backup file to restore lost data. They are also generated in the same directory as the "Data files" and have as file name ..log Lots of these, dating back to when I migrated from Quicken to GNC "Metadata files" or "state files" contain non-accounting data. That is it will record per "Data file" which windows and tabs you had open last time you were working with that "Data file", it will also remember window positions and sizes, the options for reports that were still open and so on. There is exactly one "Metadata file" per "Data file" and these will be stored in GNC_DATA_HOME/books. The name of such a file will be .gcm Just one, contents as you describe "Saved reports" is a bit of an outlier. It is a single file that contains all "Saved report configurations" you have created in gnucash. For historical reasons this file is shared by all your "Data files". It is found in GNC_DATA_HOME and is called saved-reports- 3 files; -2.8, -2.8~ and -2.8-backup suffixes. If the 2.8 is the GNC version, that means that my recollection of seeing "1.something" in Synaptic is faulty. With those defined, let's turn back to the migration. I'm surprised your DOT_GNUCASH_DIR is empty. GnuCash will only *copy* files during migration, not move. So even in the case of a successful migration, the original files should have still been in DOT_GNUCASH_DIR. I'd expect at least a populated books directory and a saved-reports file, unless you never created custom report configurations. I've never seen anything other than my .gnucash and .log files here, and it's now empty because I moved (mv, not cp) them to ~/Documents/gnucash yesterday. I also quickly checked and found the migration code is slightly dumb in that it will copy *all* files in DOT_GNUCASH_DIR. That will include your data files, backup files and log files if you effectively had stored them. But that leads to a very tricky situation unfortunately: without explicit action, gnucash would continue automatically open your data file from the DOT_GNUCASH_DIR directory while you might believe that after migration the files should be loaded from GNC_DATA_HOME. I think you have more or less solved this by moving the data file (and log and backup files) to $HOME/Documents/gnucash. But I just wanted to point this out to be sure you're not inadvertently get caught by this confusion. As for the .gcm file sizes: these files hold the state of your windows, tabs open reports and so on. I presume you had many more open last time you ran gnucash with the old .gcm files in place. Rerunning gnucash without a .gcm file is like a reset of your state information. It will only open single account hierarchy page and unless you reopened all tabs and reports before closing like you had before that would explain why the old one is much bigger. That's exactly what I saw yesterday by comparing the old and new .gcm files. A few final remarks: * You never mentioned this, but normally gnucash would pop up a message when it has attempted this migration. Did you actually get this message ? No. If the migration occurred during the Ubuntu 20.04 -> 22.04 upgrade, I would not have seen it go by in the torrent generated by the upgrader. If it showed such a message the first time I ran gnucash after the upgrade, I missed seeing it. * You mentioned you were migrating from gnucash 1.x. Was that really the previous version of gnucash you ran on your system, or just that the data file you now opened was last opened with gnucash 1.x ? Somewhere in the 2.x series we switched backends for these preferences (from the old GConf to the newer DConf). Migration between these two backends has been done somewhere between 2.x and 3.x, but that migration code is no longer present in gnucash 4.x. So if you really never ran gnucash 2.x and 3.x,
Re: [GNC] Problems upgrading to 4.8a
Phill, The values you set for GNC_DATA_HOME and GNC_CONFIG_HOME are the defaults when these variables are not set. So there's no need to explicitly set them, only if you want to override the default values. It's normal that there's nothing in GNC_CONFIG_HOME. GnuCash will never write files in that directory itself, but it will look for user generated config files in there (log.conf or config- user.scm currently). Next, I'm not sure we are talking about the same thing really when we refer to "data files". To avoid further confusion I'll define a few things first: "Data files" are the ones containing your actual accounting data. These files normally have file extension ".gnucash". If you have these files from the 1.x period they may also have no extension at all or the ".xacc" extension. "Backup files" are autogenerated by gnucash and - as the name suggests - contain backups of your accounting data. They are generated in the same directory as your "Data file" and have as file name ..gnucash "Log files" in this context are also auto generated by gnucash and contain a transaction log. That is it logs all changes made to transactions in chronological order between file saves. They can be used to replay such changes on top of a backup file to restore lost data. They are also generated in the same directory as the "Data files" and have as file name ..log "Metadata files" or "state files" contain non-accounting data. That is it will record per "Data file" which windows and tabs you had open last time you were working with that "Data file", it will also remember window positions and sizes, the options for reports that were still open and so on. There is exactly one "Metadata file" per "Data file" and these will be stored in GNC_DATA_HOME/books. The name of such a file will be .gcm "Saved reports" is a bit of an outlier. It is a single file that contains all "Saved report configurations" you have created in gnucash. For historical reasons this file is shared by all your "Data files". It is found in GNC_DATA_HOME and is called saved-reports- With those defined, let's turn back to the migration. I'm surprised your DOT_GNUCASH_DIR is empty. GnuCash will only *copy* files during migration, not move. So even in the case of a successful migration, the original files should have still been in DOT_GNUCASH_DIR. I'd expect at least a populated books directory and a saved-reports file, unless you never created custom report configurations. I also quickly checked and found the migration code is slightly dumb in that it will copy *all* files in DOT_GNUCASH_DIR. That will include your data files, backup files and log files if you effectively had stored them. But that leads to a very tricky situation unfortunately: without explicit action, gnucash would continue automatically open your data file from the DOT_GNUCASH_DIR directory while you might believe that after migration the files should be loaded from GNC_DATA_HOME. I think you have more or less solved this by moving the data file (and log and backup files) to $HOME/Documents/gnucash. But I just wanted to point this out to be sure you're not inadvertently get caught by this confusion. As for the .gcm file sizes: these files hold the state of your windows, tabs open reports and so on. I presume you had many more open last time you ran gnucash with the old .gcm files in place. Rerunning gnucash without a .gcm file is like a reset of your state information. It will only open single account hierarchy page and unless you reopened all tabs and reports before closing like you had before that would explain why the old one is much bigger. A few final remarks: * You never mentioned this, but normally gnucash would pop up a message when it has attempted this migration. Did you actually get this message ? * You mentioned you were migrating from gnucash 1.x. Was that really the previous version of gnucash you ran on your system, or just that the data file you now opened was last opened with gnucash 1.x ? Somewhere in the 2.x series we switched backends for these preferences (from the old GConf to the newer DConf). Migration between these two backends has been done somewhere between 2.x and 3.x, but that migration code is no longer present in gnucash 4.x. So if you really never ran gnucash 2.x and 3.x, this means all your preferences have been reset to default. In that case you probably want to go through your preferences again in "Edit->Preferences" to check if they are still as you want them to be. ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
> On Sep 6, 2022, at 5:10 AM, Geert Janssens wrote: > > I agreed with John's suggestion to make the choice conditional on the yelp > version as this entails the least amount of work. But backporting the whole > of my xdg branch to maint is certainly possible as well. I don't think there > are supported versions of yelp on any distro we care about that doesn't know > the "help:" schema. > On reflection I decided that that a small commit-loop aside back porting is the better option and I've done so. It's not the whole thing, just the 5 commits in https://github.com/Gnucash/gnucash-docs/pull/285 and https://github.com/Gnucash/gnucash/pull/1406. Tested on Debian Bullseye (yelp-3.38) and Sid (yelp-42). This will be in tomorrow's nightlies and GnuCash 4.12 to be released on the 25th. Regards, John Ralls ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
John ~ That appears to be the missing piece. Thanks! ~ Phil On 9/6/22 11:12, john wrote: On Sep 6, 2022, at 8:54 AM, Phil Wolff via gnucash-user [1] wrote: A critical problem remains: scheduled transactions are not being entered as they come due. The Scheduled Transaction Editor page contains all of the expected entries, and none of the "Next Occur" dates are older than the day that the version update took place. And it's not just a problem with entries that were there prior to the update; yesterday I created a new entry scheduled for today, and the transaction did not get created. What else can I look at to diagnose this problem? First, run Actions>Scheduled Transactions>Since Last Run. If that runs your scheduled transactions then they're fine and you probably need only enable running Since Last Run when the data file is opened at the top of the Scheduled Transactions page in Preferences. If the SLR doesn't work then look in the trace file (see [2]https://wiki.gnucash.org/wiki/Trace_File) for errors. Regards, John Ralls References 1. mailto:gnucash-user@gnucash.org 2. https://wiki.gnucash.org/wiki/Trace_File ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
> On Sep 6, 2022, at 8:54 AM, Phil Wolff via gnucash-user > wrote: > > A critical problem remains: scheduled transactions are not being > entered as they come due. The Scheduled Transaction Editor page > contains all of the expected entries, and none of the "Next Occur" > dates are older than the day that the version update took place. And > it's not just a problem with entries that were there prior to the > update; yesterday I created a new entry scheduled for today, and the > transaction did not get created. > > What else can I look at to diagnose this problem? First, run Actions>Scheduled Transactions>Since Last Run. If that runs your scheduled transactions then they're fine and you probably need only enable running Since Last Run when the data file is opened at the top of the Scheduled Transactions page in Preferences. If the SLR doesn't work then look in the trace file (see https://wiki.gnucash.org/wiki/Trace_File) for errors. Regards, John Ralls ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
Geert ~ I discovered that the environment variables GNC_DATA_HOME and GNC_CONFIG_HOME were not defined. They are now defined as $HOME/.local/share/gnucash and $HOME/.config/gnucash respectively as indicated at [1]https://wiki.gnucash.org/wiki/Configuration_Diagrams_-_Linux. Both directories were already present; $HOME/.local/share/gnucash was populated, $HOME/.config/gnucash was empty. I moved my data and log files from DOT_GNUCASH_DIR to $HOME/Documents/gnucash. DOT_GNUCASH_DIR is now empty, so apparently the update did in fact migrate the other files to $HOME/.local/share/gnucash in spite of the missing GNC_DATA_HOME definition. As you suggested, I moved GNC_DATA_HOME "out of the way" by renaming $HOME/.local/share/gnucash, and then ran gnucash. As expected, a new $HOME/.local/share/gnucash was created and populated. The only difference I see is in the size of the .gcm file in the books subdirectory -- the original file is much larger than the new one, clearly due to the months of activity represented by the older file. A critical problem remains: scheduled transactions are not being entered as they come due. The Scheduled Transaction Editor page contains all of the expected entries, and none of the "Next Occur" dates are older than the day that the version update took place. And it's not just a problem with entries that were there prior to the update; yesterday I created a new entry scheduled for today, and the transaction did not get created. What else can I look at to diagnose this problem? ~ Phil On 9/6/22 05:20, Geert Janssens wrote: Op maandag 5 september 2022 22:38:55 CEST schreef Phil Wolff via gnucash-user: >David ~ > > [1][2]https://wiki.gnucash.org/wiki/Configuration_Locations#DOT_GNUCASH _DI >R: "When moving from GnuCash 2.6 to 3.x or above, GnuCash will >automatically try to migrate all data from DOT_GNUCASH_DIR to their >respective new locations. After mitgration, GnuCash 3.0 or above should >never use DOT_GNUCASH_DIR again." >For my Linux system, DOT_GNUCASH_DIR is $HOME/.gnucash, and my data >file and all associated *.log files are there. Since my previous >GnuCash version was 1.something, is it reasonable to assume that this >migration was not even attempted? > I didn't want to bring this up earlier. However $HOME/.gnucash has never been the place to store your data files, though older versions of gnucash didn't prevent you from doing so or even suggested that directory by default unfortunately. The DOT_GNUCASH_DIR is meant to be used by gnucash to store internal state, not your accounting data. Having said all that, you can probably continue to work like this though I would recommend to move your actual data files to a more traditional location like $HOME/Documents/gnucash (replace gnucash with anything you like - I have only added it because gnucash creates a lot of log and backup files next to your actual data file and you may want to keep those from cluttering your Documents directory). Now back to your question: gnucash will also attempt to migrate state information for older gnucash books (that information is actually not stored in the book files themselves). It will however only attempt to do so if special directory GNC_DATA_HOME doesn't exist yet. If there was a failure to run the migration that should have been logged in the gnucash trace file that was generated during the first run of the newer gnucash. You can always try to reproduce this by temporarily moving GNC_DATA_HOME out of the way, and run gnucash. Another sidenote (though perhaps that has been the topic of another thread), we generally don't support an upgrade from gnucash 1.something to 4.x. We do support upgrades from 1.6.x->1.8.x->2.0.x->2.2.x->2.4.x->2.6.x->3.x->4.x If you skip all the steps in between, you may have some odd issues during upgrade, though I think your data itself should be fine. Regards, Geert >~ Phil > >On 9/3/22 15:14, David Cousens wrote: > > Phil, > > The installation of the GnuCash help and Tutorial and concepts guide is a > separate download and installation from the installation of the program and > is available under a separate link in the panels on the left on the GNuCash > webpage i.e. [2][3]https://gnucash.org/docs.phtml . They should also be able > to be install ed > from Ubuntu's package manager. Not sure about the scheduled transactions - I > would expect them to be stored in the book but they may be stored in the > user preference information. This wiki > page [3][4]https://wiki.gnucash.org/wiki/Configuration_Locations has > information on where they are stored and you may need to copy them from a >
Re: [GNC] Problems upgrading to 4.8a
Op maandag 5 september 2022 22:38:55 CEST schreef Phil Wolff via gnucash-user: >David ~ > >[1]https://wiki.gnucash.org/wiki/Configuration_Locations#DOT_GNUCASH_DI >R: "When moving from GnuCash 2.6 to 3.x or above, GnuCash will >automatically try to migrate all data from DOT_GNUCASH_DIR to their >respective new locations. After mitgration, GnuCash 3.0 or above should >never use DOT_GNUCASH_DIR again." >For my Linux system, DOT_GNUCASH_DIR is $HOME/.gnucash, and my data >file and all associated *.log files are there. Since my previous >GnuCash version was 1.something, is it reasonable to assume that this >migration was not even attempted? > I didn't want to bring this up earlier. However $HOME/.gnucash has never been the place to store your data files, though older versions of gnucash didn't prevent you from doing so or even suggested that directory by default unfortunately. The DOT_GNUCASH_DIR is meant to be used by gnucash to store internal state, not your accounting data. Having said all that, you can probably continue to work like this though I would recommend to move your actual data files to a more traditional location like $HOME/Documents/gnucash (replace gnucash with anything you like - I have only added it because gnucash creates a lot of log and backup files next to your actual data file and you may want to keep those from cluttering your Documents directory). Now back to your question: gnucash will also attempt to migrate state information for older gnucash books (that information is actually not stored in the book files themselves). It will however only attempt to do so if special directory GNC_DATA_HOME doesn't exist yet. If there was a failure to run the migration that should have been logged in the gnucash trace file that was generated during the first run of the newer gnucash. You can always try to reproduce this by temporarily moving GNC_DATA_HOME out of the way, and run gnucash. Another sidenote (though perhaps that has been the topic of another thread), we generally don't support an upgrade from gnucash 1.something to 4.x. We do support upgrades from 1.6.x->1.8.x->2.0.x->2.2.x->2.4.x->2.6.x->3.x->4.x If you skip all the steps in between, you may have some odd issues during upgrade, though I think your data itself should be fine. Regards, Geert >~ Phil > >On 9/3/22 15:14, David Cousens wrote: > > Phil, > > The installation of the GnuCash help and Tutorial and concepts guide is a > separate download and installation from the installation of the program and > is available under a separate link in the panels on the left on the GNuCash > webpage i.e. [2]https://gnucash.org/docs.phtml . They should also be able > to be install ed > from Ubuntu's package manager. Not sure about the scheduled transactions - I > would expect them to be stored in the book but they may be stored in the > user preference information. This wiki > page [3]https://wiki.gnucash.org/wiki/Configuration_Locations has > information on where they are stored and you may need to copy them from a > backup of your old system. > > David Cousens > > References > >1. https://wiki.gnucash.org/wiki/Configuration_Locations#DOT_GNUCASH_DIR >2. https://gnucash.org/docs.phtml >3. https://wiki.gnucash.org/wiki/Configuration_Locations > ___ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
Op dinsdag 6 september 2022 06:01:00 CEST schreef john: > > On Sep 5, 2022, at 2:01 PM, Frank H. Ellenberger > > wrote: > > > > Hi, > > > > Am 05.09.22 um 22:27 schrieb Geert Janssens: > >> Op maandag 5 september 2022 19:09:06 CEST schreef john: > >>> This is https://bugs.gnucash.org/show_bug.cgi?id=798612 > >>> > >>> I discovered while researching this that yelp v.42 just dropped support > >>> for > >>> the ghelp: scheme. help:gnucash-help and help:gnucash-guide are able to > >>> find the GnuCash docs > >> > >> I'm surprised the help: scheme finds the documentation in the old ghelp > >> locations, but that's good news really. > >> I think we best add this in for gnucash 4.12 then, and conditional on the > >> yelp version. > > > > Why conditional, IIRC help: is defined in yelp for about a decade. > > Because yelp v3.x (and maybe v40 and v41, I didn't have those handy to test) > can't find the GnuCash docs in /usr/share/docs/gnucash-docs with help: so > we have to use ghelp: on distros that are still shipping older versions of > yelp. > The intention is correct however the message is slightly confusing with respect to the directories involved. Officially "ghelp:" looks for documentation books in /usr/share/gnome/help/// "help:" on the other hand will look for books in /usr/share/help/// In both cases we provide the documentation in docbook format (albeit "help:" has a new requirement for the name of the initial page to load - it has to be index.docbook for our purpose). The document Phil pointed at in /usr/share/docs/gnucash-docs(-lang?)/ is where our build scripts will store the html target. This has never been used by yelp. Now to confirm what John said, versions of yelp before v42 (I tested on v41 just now) won't search for our documents in /usr/share/gnome/help/// when you use the "help:" schema. They will only look in /usr/share/help/// It was news to me that yelp v42 does look in both directories (I currently don't have a distro installed with the version of yelp). I agreed with John's suggestion to make the choice conditional on the yelp version as this entails the least amount of work. But backporting the whole of my xdg branch to maint is certainly possible as well. I don't think there are supported versions of yelp on any distro we care about that doesn't know the "help:" schema. Regards, Geert ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
> On Sep 5, 2022, at 2:01 PM, Frank H. Ellenberger > wrote: > > Hi, > > Am 05.09.22 um 22:27 schrieb Geert Janssens: >> Op maandag 5 september 2022 19:09:06 CEST schreef john: >>> This is https://bugs.gnucash.org/show_bug.cgi?id=798612 >>> >>> I discovered while researching this that yelp v.42 just dropped support for >>> the ghelp: scheme. help:gnucash-help and help:gnucash-guide are able to >>> find the GnuCash docs >> I'm surprised the help: scheme finds the documentation in the old ghelp >> locations, >> but that's good news really. >> I think we best add this in for gnucash 4.12 then, and conditional on the >> yelp >> version. > > Why conditional, IIRC help: is defined in yelp for about a decade. Because yelp v3.x (and maybe v40 and v41, I didn't have those handy to test) can't find the GnuCash docs in /usr/share/docs/gnucash-docs with help: so we have to use ghelp: on distros that are still shipping older versions of yelp. Regards, John Ralls ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
Hi David, Am 05.09.22 um 23:26 schrieb David Cousens: This probably indicates the Ubuntu developers haven't solved the problem. They usually only copy the debian packages and for that see Johns mail https://lists.gnucash.org/pipermail/gnucash-user/2022-September/102729.html Regards Frank ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
Hi Geert GnuCash 4.11 on Linux Mint Vanessa (Ubuntu 22.04 based) also gives the same error "Document Not Found The URI ‘ghelp:gnucash-guide’ does not point to a valid page." when opening the tutorial or help manual from the menu. There are no gnucash doc files for yelp in /usr/share/gnome/help and only the html files in /usr/share/doc/gnucash-docs/. This probably indicates the Ubuntu developers haven't solved the problem. I loaded the help fiels from the LM Software Manager. I also have the tarball downloaded so I will try compiling it and experiment a bit when I get a bit of spare time. David Cousens On Mon, 2022-09-05 at 18:03 +0200, Geert Janssens wrote: > Hi Phil, > > My response was not for flatpak. It's how the gnucash-docs build scripts > (written by the > gnucash developers) currently install things. And on Fedora 36 for example > that is still the > case. > > The documentation links you are listing are the html versions of our > documentation and is > not what is presented when invoking "Tutorial" or "Contents" from the GnuCash > menus. > GnuCash will look for the docbook version of the documentation, which at this > point is still > installed in /usr/share/gnome/help/C/gnucash-guide and > /usr/shar/gnome/help/C/gnucash- > help. (Well, pedantically it will ask yelp to look there by means of the > "ghelp:xyz" construct, > but yelp dropped support for that construct in version 42). > > I don't know what the Ubuntu packager for our documentation has decided on. > But if > Ubuntu only ships the html version of the gnucash documentation, I consider > that a bug in > that distribution. There are a few possible ways the Ubuntu packager could > solve this: > * either also patch the gnucash package to look for the html version of the > documentation > * revert the change in yelp that drops support for the "ghelp" search > qualifier. Considering > gnucash is probably the last application in the Gnome ecosystem to still > depend on this, it's > unlikely Ubuntu would go that route. > * backport the patchset from the master branch in the gnucash and gnucash-docs > repositories that rearrange our documentation output to work with yelp's > "help" search > qualifier. That way gnucash will be able to present the documentation again as > you were > used to in Ubuntu 20.04. > > I think the last option would be the most future proof one. > > Regards, > > Geert > > > Op maandag 5 september 2022 17:01:22 CEST schreef Phil Wolff via gnucash-user: > > Geert ~ > > > > Thanks for responding! > > That may be true for a Flatpak installation, but mine is what GNC calls > > "pristine," and I've found the documents at > > - file:///usr/share/doc/gnucash-docs/gnucash-guide-en/index.html > > - file:///usr/share/doc/gnucash-docs/gnucash-help-en/help.html > > > > ~ Phil > > > > On 9/5/22 00:46, Geert Janssens wrote: > > > Hi Phil, > > > > > > Regarding the documentation, it seems like Ubuntu 22.04.1 ships a newer > > > help viewer that's not compatible with where GnuCash stores its guide and > > > manual on disk. This has been fixed for the future GnuCash 5.0 but not > > > for the current 4.x series. > > > > > > As temporary workarounds you could either > > > - browse the documentation online (via the gnucash website) or > > > - load the documentation from the command line using one of these commands > > > > > > yelp /usr/share/gnome/help/C/gnucash-guide/gnucash-guide.xml > > > yelp /usr/share/gnome/help/C/gnucash-help/gnucash-help.xml > > > > > > Regards, > > > > > > Geert > > > > > > Op zondag 4 september 2022 00:14:09 CEST schreef David Cousens: > > > > Phil, > > > > > > > > The installation of the GnuCash help and Tutorial and concepts guide is > > > > a > > > > separate download and installation from the installation of the program > > > > and > > > > is available under a separate link in the panels on the left on the > > > > GNuCash > > > > webpage i.e. https://gnucash.org/docs.phtml . They should also be able > > > > to > ___ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > - > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
Hi, Am 05.09.22 um 22:27 schrieb Geert Janssens: Op maandag 5 september 2022 19:09:06 CEST schreef john: This is https://bugs.gnucash.org/show_bug.cgi?id=798612 I discovered while researching this that yelp v.42 just dropped support for the ghelp: scheme. help:gnucash-help and help:gnucash-guide are able to find the GnuCash docs I'm surprised the help: scheme finds the documentation in the old ghelp locations, but that's good news really. I think we best add this in for gnucash 4.12 then, and conditional on the yelp version. Why conditional, IIRC help: is defined in yelp for about a decade. As "ghelp:" seems to get abandoned in more and more distris, I would prefer to release the whole changeset —inclusive source directory reordering and renaming make targets— in 4.12. Regards, Geert Frank ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
David ~ [1]https://wiki.gnucash.org/wiki/Configuration_Locations#DOT_GNUCASH_DI R: "When moving from GnuCash 2.6 to 3.x or above, GnuCash will automatically try to migrate all data from DOT_GNUCASH_DIR to their respective new locations. After mitgration, GnuCash 3.0 or above should never use DOT_GNUCASH_DIR again." For my Linux system, DOT_GNUCASH_DIR is $HOME/.gnucash, and my data file and all associated *.log files are there. Since my previous GnuCash version was 1.something, is it reasonable to assume that this migration was not even attempted? ~ Phil On 9/3/22 15:14, David Cousens wrote: Phil, The installation of the GnuCash help and Tutorial and concepts guide is a separate download and installation from the installation of the program and is available under a separate link in the panels on the left on the GNuCash webpage i.e. [2]https://gnucash.org/docs.phtml . They should also be able to be install ed from Ubuntu's package manager. Not sure about the scheduled transactions - I would expect them to be stored in the book but they may be stored in the user preference information. This wiki page [3]https://wiki.gnucash.org/wiki/Configuration_Locations has information on where they are stored and you may need to copy them from a backup of your old system. David Cousens References 1. https://wiki.gnucash.org/wiki/Configuration_Locations#DOT_GNUCASH_DIR 2. https://gnucash.org/docs.phtml 3. https://wiki.gnucash.org/wiki/Configuration_Locations ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
Op maandag 5 september 2022 19:09:06 CEST schreef john: > This is https://bugs.gnucash.org/show_bug.cgi?id=798612 > > I discovered while researching this that yelp v.42 just dropped support for > the ghelp: scheme. help:gnucash-help and help:gnucash-guide are able to > find the GnuCash docs I'm surprised the help: scheme finds the documentation in the old ghelp locations, but that's good news really. I think we best add this in for gnucash 4.12 then, and conditional on the yelp version. Regards, Geert ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
This is https://bugs.gnucash.org/show_bug.cgi?id=798612
I discovered while researching this that yelp v.42 just dropped support for the
ghelp: scheme. help:gnucash-help and help:gnucash-guide are able to find the
GnuCash docs so another option for the packager (and BTW I think the one in
question is the Debian packager, Dmitry Smirnov whom I've cc'd ) would be to
apply this:
diff --git a/gnucash/gnome-utils/gnc-gnome-utils.c
b/gnucash/gnome-utils/gnc-gnome-utils.c
index 2c3cfac02..6cfbf3473 100644
--- a/gnucash/gnome-utils/gnc-gnome-utils.c
+++ b/gnucash/gnome-utils/gnc-gnome-utils.c
@@ -277,7 +277,7 @@ gnc_gnome_help_yelp_anchor_fix (GtkWindow *parent, const
char *file_name, const
g_free (help_file);
if (full_path)
-uri = g_strconcat ("ghelp:", full_path, "?", anchor, NULL);
+uri = g_strconcat ("help:", full_path, "?", anchor, NULL);
else
{
gnc_error_dialog (parent, "%s\n%s", _(msg_no_help_found),
_(msg_no_help_reason));
@@ -475,7 +475,7 @@ gnc_gnome_help (GtkWindow *parent, const char *file_name,
const char *anchor)
if (anchor)
uri = gnc_gnome_help_yelp_anchor_fix (parent, file_name, anchor);
else
-uri = g_strconcat ("ghelp:", file_name, NULL);
+uri = g_strconcat ("help:", file_name, NULL);
DEBUG ("Attempting to opening help uri %s", uri);
We could elaborate that by making it conditional on the yelp version and put it
in GnuCash 4.12 that we'll release at the end of the month.
BTW the Gnome 43 runtime also releases in two weeks. IIRC Flathub will force us
to update our current 41 to 42 or 43 for the 4.12 release, meaning that we need
that change for the flatpak build too.
Regards,
John Ralls
> On Sep 5, 2022, at 9:03 AM, Geert Janssens wrote:
>
> Hi Phil,
>
> My response was not for flatpak. It's how the gnucash-docs build scripts
> (written by the
> gnucash developers) currently install things. And on Fedora 36 for example
> that is still the
> case.
>
> The documentation links you are listing are the html versions of our
> documentation and is
> not what is presented when invoking "Tutorial" or "Contents" from the GnuCash
> menus.
> GnuCash will look for the docbook version of the documentation, which at this
> point is still
> installed in /usr/share/gnome/help/C/gnucash-guide and
> /usr/shar/gnome/help/C/gnucash-
> help. (Well, pedantically it will ask yelp to look there by means of the
> "ghelp:xyz" construct,
> but yelp dropped support for that construct in version 42).
>
> I don't know what the Ubuntu packager for our documentation has decided on.
> But if
> Ubuntu only ships the html version of the gnucash documentation, I consider
> that a bug in
> that distribution. There are a few possible ways the Ubuntu packager could
> solve this:
> * either also patch the gnucash package to look for the html version of the
> documentation
> * revert the change in yelp that drops support for the "ghelp" search
> qualifier. Considering
> gnucash is probably the last application in the Gnome ecosystem to still
> depend on this, it's
> unlikely Ubuntu would go that route.
> * backport the patchset from the master branch in the gnucash and
> gnucash-docs
> repositories that rearrange our documentation output to work with yelp's
> "help" search
> qualifier. That way gnucash will be able to present the documentation again
> as you were
> used to in Ubuntu 20.04.
>
> I think the last option would be the most future proof one.
>
> Regards,
>
> Geert
>
>
> Op maandag 5 september 2022 17:01:22 CEST schreef Phil Wolff via gnucash-user:
>> Geert ~
>>
>> Thanks for responding!
>> That may be true for a Flatpak installation, but mine is what GNC calls
>> "pristine," and I've found the documents at
>> - file:///usr/share/doc/gnucash-docs/gnucash-guide-en/index.html
>> - file:///usr/share/doc/gnucash-docs/gnucash-help-en/help.html
>>
>> ~ Phil
>>
>> On 9/5/22 00:46, Geert Janssens wrote:
>>> Hi Phil,
>>>
>>> Regarding the documentation, it seems like Ubuntu 22.04.1 ships a newer
>>> help viewer that's not compatible with where GnuCash stores its guide and
>>> manual on disk. This has been fixed for the future GnuCash 5.0 but not
>>> for the current 4.x series.
>>>
>>> As temporary workarounds you could either
>>> - browse the documentation online (via the gnucash website) or
>>> - load the documentation from the command line using one of these commands
>>>
>>> yelp /usr/share/gnome/help/C/gnucash-guide/gnucash-guide.xml
>>> yelp /usr/share/gnome/help/C/gnucash-help/gnucash-help.xml
>>>
>>> Regards,
>>>
>>> Geert
>>>
>>> Op zondag 4 september 2022 00:14:09 CEST schreef David Cousens:
Phil,
The installation of the GnuCash help and Tutorial and concepts guide is a
separate download and installation from the installation of the program
and
is available under a separate link in the panels on the left on the
GNuCash
webpage i.e.
Re: [GNC] Problems upgrading to 4.8a
Hi Phil, My response was not for flatpak. It's how the gnucash-docs build scripts (written by the gnucash developers) currently install things. And on Fedora 36 for example that is still the case. The documentation links you are listing are the html versions of our documentation and is not what is presented when invoking "Tutorial" or "Contents" from the GnuCash menus. GnuCash will look for the docbook version of the documentation, which at this point is still installed in /usr/share/gnome/help/C/gnucash-guide and /usr/shar/gnome/help/C/gnucash- help. (Well, pedantically it will ask yelp to look there by means of the "ghelp:xyz" construct, but yelp dropped support for that construct in version 42). I don't know what the Ubuntu packager for our documentation has decided on. But if Ubuntu only ships the html version of the gnucash documentation, I consider that a bug in that distribution. There are a few possible ways the Ubuntu packager could solve this: * either also patch the gnucash package to look for the html version of the documentation * revert the change in yelp that drops support for the "ghelp" search qualifier. Considering gnucash is probably the last application in the Gnome ecosystem to still depend on this, it's unlikely Ubuntu would go that route. * backport the patchset from the master branch in the gnucash and gnucash-docs repositories that rearrange our documentation output to work with yelp's "help" search qualifier. That way gnucash will be able to present the documentation again as you were used to in Ubuntu 20.04. I think the last option would be the most future proof one. Regards, Geert Op maandag 5 september 2022 17:01:22 CEST schreef Phil Wolff via gnucash-user: > Geert ~ > > Thanks for responding! > That may be true for a Flatpak installation, but mine is what GNC calls > "pristine," and I've found the documents at > - file:///usr/share/doc/gnucash-docs/gnucash-guide-en/index.html > - file:///usr/share/doc/gnucash-docs/gnucash-help-en/help.html > > ~ Phil > > On 9/5/22 00:46, Geert Janssens wrote: > > Hi Phil, > > > > Regarding the documentation, it seems like Ubuntu 22.04.1 ships a newer > > help viewer that's not compatible with where GnuCash stores its guide and > > manual on disk. This has been fixed for the future GnuCash 5.0 but not > > for the current 4.x series. > > > > As temporary workarounds you could either > > - browse the documentation online (via the gnucash website) or > > - load the documentation from the command line using one of these commands > > > >yelp /usr/share/gnome/help/C/gnucash-guide/gnucash-guide.xml > >yelp /usr/share/gnome/help/C/gnucash-help/gnucash-help.xml > > > > Regards, > > > > Geert > > > > Op zondag 4 september 2022 00:14:09 CEST schreef David Cousens: > >> Phil, > >> > >> The installation of the GnuCash help and Tutorial and concepts guide is a > >> separate download and installation from the installation of the program > >> and > >> is available under a separate link in the panels on the left on the > >> GNuCash > >> webpage i.e. https://gnucash.org/docs.phtml . They should also be able > >> to ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
Geert ~ Thanks for responding! That may be true for a Flatpak installation, but mine is what GNC calls "pristine," and I've found the documents at - file:///usr/share/doc/gnucash-docs/gnucash-guide-en/index.html - file:///usr/share/doc/gnucash-docs/gnucash-help-en/help.html ~ Phil On 9/5/22 00:46, Geert Janssens wrote: Hi Phil, Regarding the documentation, it seems like Ubuntu 22.04.1 ships a newer help viewer that's not compatible with where GnuCash stores its guide and manual on disk. This has been fixed for the future GnuCash 5.0 but not for the current 4.x series. As temporary workarounds you could either - browse the documentation online (via the gnucash website) or - load the documentation from the command line using one of these commands yelp /usr/share/gnome/help/C/gnucash-guide/gnucash-guide.xml yelp /usr/share/gnome/help/C/gnucash-help/gnucash-help.xml Regards, Geert Op zondag 4 september 2022 00:14:09 CEST schreef David Cousens: Phil, The installation of the GnuCash help and Tutorial and concepts guide is a separate download and installation from the installation of the program and is available under a separate link in the panels on the left on the GNuCash webpage i.e. https://gnucash.org/docs.phtml . They should also be able to be installed from Ubuntu's package manager. Not sure about the scheduled transactions - I would expect them to be stored in the book but they may be stored in the user preference information. This wiki page https://wiki.gnucash.org/wiki/Configuration_Locations has information on where they are stored and you may need to copy them from a backup of your old system. David Cousens On Sat, 2022-09-03 at 12:21 -0700, Phil Wolff via gnucash-user wrote: I was running Ubuntu 20.04.4 and whatever GnuCash version was available in that release, and all was well. Then, around the middle of August when 22.04.1 became available, I upgraded and GnuCash was updated to 4.8a. Clicking the desktop icon, which used to present my database page, now opens a largely empty window titled "Unsaved Book - GnuCash." Selecting Tutorial or Contents in the Help menu either does nothing visible or pops up a window saying, "Document Not Found. The URI ‘[1]ghelp:gnucash-guide’ does not point to a valid page." I eventually determined that I could access my data by selecting the "File/Open…" menu item and navigating to the data file in the .gnucash folder of my home directory. Although sub-optimal, this worked for me until September 1 arrived and none of my first-of-the-month scheduled transactions were posted. This suggests that something vital that needed to happen during the move from the older version of GnuCash to 4.8a ... didn't. Anyone have any ideas? Any help will be greatly appreciated! References 1. ghelp:gnucash-guide’ ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All. ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All. ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All. -- What was that about a rising tide lifting all boats? What if you don't have a boat? — Eugene Robinson ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
Hi Phil, Regarding the documentation, it seems like Ubuntu 22.04.1 ships a newer help viewer that's not compatible with where GnuCash stores its guide and manual on disk. This has been fixed for the future GnuCash 5.0 but not for the current 4.x series. As temporary workarounds you could either - browse the documentation online (via the gnucash website) or - load the documentation from the command line using one of these commands yelp /usr/share/gnome/help/C/gnucash-guide/gnucash-guide.xml yelp /usr/share/gnome/help/C/gnucash-help/gnucash-help.xml Regards, Geert Op zondag 4 september 2022 00:14:09 CEST schreef David Cousens: > Phil, > > The installation of the GnuCash help and Tutorial and concepts guide is a > separate download and installation from the installation of the program and > is available under a separate link in the panels on the left on the GNuCash > webpage i.e. https://gnucash.org/docs.phtml . They should also be able to > be installed from Ubuntu's package manager. Not sure about the scheduled > transactions - I would expect them to be stored in the book but they may be > stored in the user preference information. This wiki > page https://wiki.gnucash.org/wiki/Configuration_Locations has information > on where they are stored and you may need to copy them from a backup of > your old system. > > David Cousens > > On Sat, 2022-09-03 at 12:21 -0700, Phil Wolff via gnucash-user wrote: > >I was running Ubuntu 20.04.4 and whatever GnuCash version was available > >in that release, and all was well. Then, around the middle of August > >when 22.04.1 became available, I upgraded and GnuCash was updated to > >4.8a. Clicking the desktop icon, which used to present my database > >page, now opens a largely empty window titled "Unsaved Book - GnuCash." > >Selecting Tutorial or Contents in the Help menu either does nothing > >visible or pops up a window saying, "Document Not Found. The URI > >‘[1]ghelp:gnucash-guide’ does not point to a valid page." I eventually > >determined that I could access my data by selecting the "File/Open…" > >menu item and navigating to the data file in the .gnucash folder of my > >home directory. Although sub-optimal, this worked for me until > >September 1 arrived and none of my first-of-the-month scheduled > >transactions were posted. This suggests that something vital that > >needed to happen during the move from the older version of GnuCash to > >4.8a ... didn't. Anyone have any ideas? Any help will be greatly > >appreciated! > > > > References > > > >1. ghelp:gnucash-guide’ > > ___ > > gnucash-user mailing list > > gnucash-user@gnucash.org > > To update your subscription preferences or to unsubscribe: > > https://lists.gnucash.org/mailman/listinfo/gnucash-user > > - > > Please remember to CC this list on all your replies. > > You can do this by using Reply-To-List or Reply-All. > > ___ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > - > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
David ~ Thanks for the quick response. The package manager did indeed install both guides (each in several languages, in spite of there being only one locale specified in the OS!); apparently the author(s?) of the installers didn't properly configure the dependencies so the executable can't find them. I've now got them bookmarked in my browser. I can't check on the storage locations yet because the wiki is offline again – it took me two days to find it up and running so I could sign up for this list. However, I don't think the scheduled transactions aren't available; the editor shows them all (with the proper "Next Occur" dates, several of which are now in the past). ~ Phil On 9/3/22 15:14, David Cousens wrote: Phil, The installation of the GnuCash help and Tutorial and concepts guide is a separate download and installation from the installation of the program and is available under a separate link in the panels on the left on the GNuCash webpage i.e. [1]https://gnucash.org/docs.phtml . They should also be able to be install ed from Ubuntu's package manager. Not sure about the scheduled transactions - I would expect them to be stored in the book but they may be stored in the user preference information. This wiki page [2]https://wiki.gnucash.org/wiki/Configuration_Locations has information on where they are stored and you may need to copy them from a backup of your old system. David Cousens On Sat, 2022-09-03 at 12:21 -0700, Phil Wolff via gnucash-user wrote: I was running Ubuntu 20.04.4 and whatever GnuCash version was available in that release, and all was well. Then, around the middle of August when 22.04.1 became available, I upgraded and GnuCash was updated to 4.8a. Clicking the desktop icon, which used to present my database page, now opens a largely empty window titled "Unsaved Book - GnuCash." Selecting Tutorial or Contents in the Help menu either does nothing visible or pops up a window saying, "Document Not Found. The URI ‘[1][3]ghelp:gnucash-guide’ does not point to a valid page." I eventually determined that I could access my data by selecting the "File/Open…" menu item and navigating to the data file in the .gnucash folder of my home directory. Although sub-optimal, this worked for me until September 1 arrived and none of my first-of-the-month scheduled transactions were posted. This suggests that something vital that needed to happen during the move from the older version of GnuCash to 4.8a ... didn't. Anyone have any ideas? Any help will be greatly appreciated! References 1. [4]ghelp:gnucash-guide’ ___ gnucash-user mailing list [5]gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: [6]https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All. ___ gnucash-user mailing list [7]gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: [8]https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All. -- What was that about a rising tide lifting all boats? What if you don't have a boat? — Eugene Robinson References 1. https://gnucash.org/docs.phtml 2. https://wiki.gnucash.org/wiki/Configuration_Locations 3. ghelp:gnucash-guide’ 4. ghelp:gnucash-guide’ 5. mailto:gnucash-user@gnucash.org 6. https://lists.gnucash.org/mailman/listinfo/gnucash-user 7. mailto:gnucash-user@gnucash.org 8. https://lists.gnucash.org/mailman/listinfo/gnucash-user ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] Problems upgrading to 4.8a
Phil, The installation of the GnuCash help and Tutorial and concepts guide is a separate download and installation from the installation of the program and is available under a separate link in the panels on the left on the GNuCash webpage i.e. https://gnucash.org/docs.phtml . They should also be able to be installed from Ubuntu's package manager. Not sure about the scheduled transactions - I would expect them to be stored in the book but they may be stored in the user preference information. This wiki page https://wiki.gnucash.org/wiki/Configuration_Locations has information on where they are stored and you may need to copy them from a backup of your old system. David Cousens On Sat, 2022-09-03 at 12:21 -0700, Phil Wolff via gnucash-user wrote: > I was running Ubuntu 20.04.4 and whatever GnuCash version was available > in that release, and all was well. Then, around the middle of August > when 22.04.1 became available, I upgraded and GnuCash was updated to > 4.8a. Clicking the desktop icon, which used to present my database > page, now opens a largely empty window titled "Unsaved Book - GnuCash." > Selecting Tutorial or Contents in the Help menu either does nothing > visible or pops up a window saying, "Document Not Found. The URI > ‘[1]ghelp:gnucash-guide’ does not point to a valid page." I eventually > determined that I could access my data by selecting the "File/Open…" > menu item and navigating to the data file in the .gnucash folder of my > home directory. Although sub-optimal, this worked for me until > September 1 arrived and none of my first-of-the-month scheduled > transactions were posted. This suggests that something vital that > needed to happen during the move from the older version of GnuCash to > 4.8a ... didn't. Anyone have any ideas? Any help will be greatly > appreciated! > > References > > 1. ghelp:gnucash-guide’ > ___ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > - > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
