> On Dec 7, 2023, at 08:51, Michael Hendry <hendry.mich...@gmail.com> wrote: > > I had entered a few transactions in one of my Gnucash files (File “A”) around > 12:30 (GMT), and left the computer for a few hours. I came back to it around > 16:15, and after watching a Youtube video and checking my email, I went back > to Gnucash and (assuming the autosave would have cleared the way) I used the > File menu to open a different Gnucash file (File “B”). > > I was asked if I wanted to save the current file, and said yes, I was > prompted again and I believe I’d accepted the offer to save before the crash. > > As expected after the crash, the next time I ran Gnucash I was warned about > the lock on file “B”. I opted to open it anyway, and it appears at first > glance to be undamaged. > > This time, I’ve saved the whole crash report, but I’m only including a small > portion of it for expert advice on whether ithe full report would be useful. >
Michael, That file A was already saved and it was loading file B is indicated by the lock file being on file B. I think you got enough in your extract to show me what was going on when it crashed. It's loading everything from file_B.gcm (gnc_main_window_restore_all_windows) and gnc_plugin_page_register_ui_update got called on the run of the event loop that was meant to update the cursor. Figuring out anything past that will take more work, so please open a bug with the crash report attached so that it doesn't get lost. 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.
