I think you might be missing some of the steps you were asked to perform, so here they are:

(1) Run Gnucash while telling it to save a trace file. This file lists all the actions of the program. This is done with the command (on MacOS):

/Applications/Gnucash.app/Contents/MacOS/Gnucash --debug

This will run Gnucash, presumably until it crashes, while writing a trace file in the directory specified by the environment variable TMPDIR on your system.

(2) To make the trace file more accessible, you copy it to your user directory. To be sure it's in this location, perform the following two commands:

cd

cp $TMPDIR/gnucash.trace .

(3) Now that you have this tracefile, you want to provide it to the folks on the mailing list who can interpret such things. Since it's likely a very long file, it is not a good idea to copy and paste it's contents into a message. Instead, when you reply to the mailing list, you attach the file to the message, usually by dragging and dropping the file in Outlook, or using the "Attach File" button, etc.


Hopefully, if you do these things, someone will be able to figure out where your installation is going wrong.
_______________________________________________
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.

Reply via email to