Master - saving to xml broken
geert.gnucash at kobaltwit.be
Fri Dec 2 11:43:49 EST 2016
Op vrijdag 2 december 2016 17:38:52 CET schreef Geert Janssens:
> Op vrijdag 2 december 2016 17:20:13 CET schreef Geert Janssens:
> > Here's my scenario:
> > - start gnucash
> > - create new file
> > - go through the assistant, simply by clicking forward everywhere
> > - save the file
> > - add one vendor
> > - save the file
> > - restart gnucash
> > => error as described earlier
> > Checking my data file, it does indeed have the vendor stored twice. I'm
> > currently doing a full clean rebuild of gnucash master (freshly checked
> > out
> > from github). I'll report my findings when the build finishes.
> > Geert
> Ok, clean rebuild of current master. Things are even worse. Same steps as
> After the assistant finishes, I'm offered a save dialog. I'm entering a new
> file name (of a non-existent file). A second dialog window pops up telling
> me the file is already open and asks whether I want to save over it. At the
> same time this message is printed in the logs:
> * 17:30:49 WARN <gnc.backend> [GncXmlBackend::session_begin()] Might
> clobber, no force
> I tell gnucash to overwrite and the save dialog closes. The window title is
> changed to *Double.gnucash (I chose "Double" as file name).
> This suggests the file is not saved yet. Looking on the file system it's not
> there indeed. But the lock files are.
> Closing gnucash it asks me again whether I want to save the file. I'm
> telling it to save. Immediately a second dialog pops up warning me the
> changes of the last x minutes will be lost if I close without saving.
> I chose again to save, the same dialog appears again and will continue to do
> so until I choose to close without saving. At that point gnucash segfaults.
> There's no file on my file system with the name Double.gnucash.
> There is also no other version of gnucash or its libraries on the path.
And I should have mentioned that when I run the exact same steps with a build
of maint I still have on my system, it works as expected.
This maint is in a completely separate directory tree, not on the path or
library paths, so interference with the master build should not be possible.
More information about the gnucash-devel