[GNC] GnuCash 2.6.12 aborts (core dump) on Ubuntu 16 "hash table assertion failed"

[GWB]

Just figured it out.  The gnucash data file loads more quickly when it
is located on the C: drive itself, instead of being on a shared folder
elsewhere.  So I moved the .xml file from the VirtualBox shared folder
on Ubuntu 16 to the C: drive in the Windows 7 VM.  The reports also
load more quickly.

I don't expect it to load the file too quickly.  The uncompressed xml
is about 61 megs.  That's quite a bit of data.  I don't know what kind
of cache file would speed that up, but this is good enough.

I will stick with the uncompressed xml for now.  From the
documentation, it's easier to replay transactions with the xml, and
more difficult with the sqlite3 format.  I can always go back to an
earlier version from a snapshot if the xml replay fails or does not
rollback.

It also appears that the sqlite3 format is becoming ubiquitous, and
even web browsers appear to be using it.  But it might not be as
robust as the postgresql files I've used.  postgresql has a good way
of rolling back through a transaction history within the DB itself,
but I'm not sure how to do that with sqlite3.  So the xml text file,
uncompressed, with autosave every 5 minutes, and save the log files is
what I will do (and with zfs snapshots on top of that).

Let's just call that the "super paranoid" setting to avoid data loss
(also with off site backup).

The developers here have done great work, thank you all.  It now looks
as if FreeBSD 10 has GnuCash 3.7:

https://www.freebsd.org/cgi/ports.cgi?query=gnucash&stype=all

Is there enough interest in running GnuCash on a BSD system to try
this?  I have at least one server I can use to try it out.  I'm happy
to be a guinea pig for that effort.  Otherwise I'll stick with the
Windows version for now; that seems to be the largest percentage of
the user base.

Gordon





On Tue, Sep 17, 2019 at 5:01 PM GWB <gwb at 2realms.com> wrote:
>
> OK; Outstanding, this works like a charm.  On Windows 7 Pro (64 bit)
> the GnuCash installation created:
>
> C:\Users\$USER\.gnucash
>
> There is also:
>
> C:\Users\$USER\.AppData\Local... \LocalLow ...\Roaming
>
> When I copy the files from the linux installation at:
>
> $user/.gnucash to C:\Users\$USER\.gnucash, it does indeed find the
> Saved Report Configurations.
>
> My assumption is that Windows 8 and 10 probably will set up the
> .gnucash config directory in:
>
> C:\Users\$USER\.AppData\Roaming, or Local, because 8 and 10 seem to
> behave that way (I don't know why).
>
> I can confirm that the flatpak migrates:
>
> $user/.gnucash
>
> to:
>
> ~/.var/app/org.gnucash.GnuCash
>
> It does the migration when installing the flatpak by:
>
> flatpak-install or.gnucash.GnuGash (or, depending on the type of
> shell, just flatpak-install gnucash)
>
> The flatpak has some distinct advantages.  One drawback is that
> libraries are not dynamic, static or even linked, but appear to be
> "bundled" into the installed app binary itself.  But that's also the
> advantage, when linked libraries on linux machines are not found, or
> are incompatible.  Larger installed binary, fewer dependency problems.
>
> FreeBSD and linux have cross-compilers for each other, so I might try
> the flatpak again when I have FreeBSD 10 or Ubuntu 18 installed.
> Again, the flatpak looks and works fine.  Only the window
> configuration (so far) is the problem with the flatpak.
>
> Is there an advantage to using GnuCash 3 on Windows 8 or 10?  Windows
> 7 is showing it's age, and it's taking some time to load reports, open
> files, etc.
>
> Mange Tak,
>
> Gordon
>
>
> On Tue, Sep 17, 2019 at 3:33 AM Geert Janssens
> <geert.gnucash at kobaltwit.be> wrote:
> >
> > Op maandag 16 september 2019 05:30:16 CEST schreef John Ralls:
> > > Gordon,
> > >
> > > GnuCash files are completely portable between operating systems. See
> > > https://wiki.gnucash.org/wiki/Backup for the details of which files need to
> > > be copied.
> > >
> > > The code to upgrade the saved reports and similar stuff kicks is driven by
> > > the location of the files, so copy your 2.6 config files to the 2.6
> > > locations (generally $HOME/.gnucash). Make sure the new locations
> > > ($HOME/.config/gnucash on Linux, $HOME/AppData/Roaming/GnuCash on Windows)
> > > don't exist; if they do GnuCash will decide that the config is already
> > > migrated. Start up GnuCash and everything should properly migrate.
> > >
> > > That said, flatpak installs are a bit problematic for migration. They're
> > > seriously sandboxed and I'm not sure that we've figured out everything
> > > needed to work around the sandboxing.
> >
> > We don't have to do anything special wrt to the sandbox as it won't affect the
> > migration logic (just tested).
> >
> > The flatpak version of gnucash will still search for the old configuration in
> > $HOME/.gnucash (that is, not sandboxed)
> > It will migrate this to locations inside the sandbox though. So make sure the
> > following locations don't exist if you want the migration to be triggered:
> > $HOME/.var/app/org.gnucash.GnuCash/data/gnucash
> > $HOME/.var/app/org.gnucash.GnuCash/config/gnucash
> >
> > Regards,
> >
> > Geert
> >
> >