Op donderdag 19 september 2019 15:45:06 CEST schreef Brian M. Sutin: > Thank you. How do I generate a gnucash.trace file? > http://wiki.gnucash.org/wiki/Tracefile
> > Op donderdag 19 september 2019 04:42:36 CEST schreef Brian M. Sutin: > > > I installed 3.7 from flatpak, but then I couldn't find the executable. > > > > There is no "executable" with flatpak. You use the command > > flatpak run org.gnucash.GnuCash > > to start the gnucash flatpak > > > > > So, I > > > uninstalled the flatpak, downloaded the source and compiled it. I also > > > deleted every single .XXX file in my home directory that had 'gnucash' > > > in > > > the title. Oddly, even with all initialization files deleted, gnucash > > > 3.7 > > > still finds by Gnucash accounts file, and complains that it is locked. > > > Second, it still crashes. > > > > > > Question 1: How did Gnucash 3.7 find my previous accounts file and the > > > lock? Where is that information stored? > > > > GnuCash keeps a history of opened files in the gsettings database. On > > linux > > gsettings uses dconf as backend, so you can use dconf-editor to check and > > modify that info. > > > > > Question 2: Now that I have a recent version that core dumps, what do I > > > need to post to spelunk the problem? Or do I post that elsewhere? > > > > If you're about to post core dumps (or backtraces) I think this is better > > done in a bug report than on the mailing list. Mail messages tend to wrap > > lines which make the data hard to process. > > > > Other useful information would be the contents of your gnucash.trace file > > and the output on the console. > > > > Regards, > > > > Geert > > > > > > Thank you, everyone. I think I will wait for the next version to come > > > > out next month and try it out then. If I am going to install it by > > > > hand, I might as well install the latest. > > > > > > > > > Op zaterdag 24 augustus 2019 20:17:50 CEST schreef gnuca...@skewray.com: > > > > > > A year or two ago I was running Ubuntu 16.10. When I upgraded to > > > > > > the > > > > > > next > > > > > > Ubuntu version, Gnucash did some moving and reformatting of my > > > > > > config > > > > > > files. When I ran Gnucash, it would hang up inside any register > > > > > > and > > > > > > crash. I 'solved' the problem by running 2.6.12 in Virtualbox on > > > > > > Ubuntu 16.04, which is what I've been doing ever since. Ubuntu > > > > > > has > > > > > > upgraded a few times, and the issue persists. The current version > > > > > > that still doesn't work is Gnucash 3.4. > > > > > > > > > > > > Is this a known issue? Is ther a previous thread in this list that > > > > > > addresses this? If not, how would I go about starting to debug > > > > > > the > > > > > > issue? > > > > > > > > > > > > Places where config files seem to be: > > > > > > .config/gnucash > > > > > > .gconf/apps/gnucash > > > > > > .gnucash/books/Gnucash > > > > > > .local/share/gnucash/books > > > > > > > > > > > > I don't know which of these is from before the conversion and > > > > > > which > > > > > > are new. The problem might also be in a library, I guess. > > > > > > > > > > A few more bits that were omitted or glossed over in the other > > > > > responses: > > > > > > > > > > .gconf/apps/gnucash predates even gnucash 2.6. If you have no > > > > > intention > > > > > to > > > > > rerun gnucash 2.4, you can safely remove this. > > > > > Of the others > > > > > .gnucash/ is the config directory used by gnucash2.6 > > > > > .config/gnucash and .local/share/gnucash are used by gnucash 3.x > > > > > > > > > > If you have been running gnucash in a VM, and now run gnucash on > > > > > your > > > > > main > > > > > system, obviously it won't find the config data stored in your VM. > > > > > If > > > > > you > > > > > would like gnucash to redo the config data conversion for you, > > > > > you'll > > > > > have to 1. copy everything from .gnucash/ in your VM to .gnucash/ on > > > > > your main system 2. delete .local/share/gnucash and .config/gnucash > > > > > from your main system 3. start gnucash > > > > > > > > > > As others have noted, if that still crashes, we're need more details > > > > > to > > > > > determine the root cause. A trace file would be useful [1] or if you > > > > > know how to use the gdb debugger tool, a backtrace usually holds > > > > > more > > > > > details still. > > > > > > > > > > Regards, > > > > > > > > > > Geert > > > > > > > > > > [1] http://wiki.gnucash.org/wiki/Tracefile > > > > > > > > _______________________________________________ > > > > gnucash-user mailing list > > > > gnucash-user@gnucash.org > > > > To update your subscription preferences or to unsubscribe: > > > > https://lists.gnucash.org/mailman/listinfo/gnucash-user > > > > If you are using Nabble or Gmane, please see > > > > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. > > > > ----- > > > > 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 > > > If you are using Nabble or Gmane, please see > > > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- > > > 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 If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
