Created attachment 372994 [details] Problem Report On Mac OS 10.14 Mojave, GnuCash shows the splash screen, then crashes. Problem report log attached.
Additionally: - After running FinanceQuote Update, GnuCash does launch from the Terminal (without arguments) - GnuCash still crashes when launching from Finder - Font size is extremely large in the UI when it does launch
Another user reported on IRC that simply placing GnuCash in the Dock was sufficient to prevent the same crash. Please try that.
Ensuring that Gnucash is kept in the Dock worked for me—amazing! Thank you for that hint, John! That said, whatever the source of that issue is should be rooted out, as that oughtn’t be a requirement. The only clue that I could add is that after docking Gnucash, the common “could not get a lock” prompt came up. Once I selected open anyway, Gnucash completed the launch. Perhaps not being in the Dock somehow interferes with cases when the file lock can’t be obtained? did give the usual Here are just a few more comments in my attempt—prior to John’s hint—to troubleshoot the issue. Attempting Max’s solution of running FinanceQuote Update didn’t work for me. That did seem promising though because Gnucash was crashing right at the point when the splash screen references “Finance:Quote”. Will attach a screenshot subsequently. I only installed 3.3-1 this morning, and, then, it launched fine. With good hopes, I trashed 3.2 and 3.1, as I was still using 3.1 due to crashing with 3.2 and unresolved issues. Being in an update mode, I noticed that Apple also had a system update, “Security Update Developer Beta 10.13.6”, which I then installed. Unfortunately, after rebooting, Gnucash would no longer launch, crashing at the point referenced above. I tried numerous re-installations, even of previous versions, to no avail. Attempting to launch from Terminal to no avail.
Created attachment 373001 [details] Checking Finance::Quote crash point
This has been reported upstream as https://gitlab.gnome.org/GNOME/gtk/issues/1312.
*** Bug 796889 has been marked as a duplicate of this bug. ***
*** Bug 796902 has been marked as a duplicate of this bug. ***
*** Bug 796901 has been marked as a duplicate of this bug. ***
Placing GNUCash in the Dock did not work for me. Have had to revert to version 3.2.
I've uploaded https://sourceforge.net/projects/gnucash/files/gnucash%20%28stable%29/3.3/Gnucash-Intel-3.3-2.dmg/download which includes Gtk patches that should fix the problem. Please test.
I downloaded and tested this file. The problem persists. Also, it does not say that it is v3.2.2 only that it is 3.3.
Hmm. I downloaded and installed the new version and in my (unscientific) tests it has seemed more stable. The earlier build would typically crash for me if I opened it, did other things in other apps for some time, and then returned to GnuCash and tried to do something. It is unfortunate that the About GnuCash display was seemingly not updated to reflect the newer version or the more recent build date, but at least for me I am seeing better behavior.
I misspoke. The bug that is not fixed is the one that has the cursor selecting one line low in every window (very annoying) unless the window is resized. I have not (yet) seen the crash as before.
(In reply to Ira Fuchs from comment #11) > ... Also, it does not say that it is v3.2.2 only that it is 3.3. That's because it's 3.3. We're using only two digits for version numbers now. (In reply to Tim Q from comment #12) > > It is unfortunate that the About GnuCash display was seemingly not updated > to reflect the newer version or the more recent build date, but at least for > me I am seeing better behavior. Why is it unfortunate? It's the same release (3.3), just rebundled with a new build of Gtk+. We've changed from using the build date (which isn't very useful) to the commit sha and date (which is, it tells you what the state of the GnuCash code is).
Look at this from the user's perspective, not the developer's. I get that no GC code has changed although I would argue that the dependency list of GC including versions _is_ part of the GC codebase, and that _has_ changed to adopt the later GTK build to fix this problem for GC users. From the user's point of view something has certainly changed that affects the GC user experience for the better. You (correctly) publicized a new download and (correctly) urged people to test it because it would resolve users' problems, in this case because _only_ its dependencies changed, but changed very importantly. I then downloaded it and installed it and saw improvement. Yet once I've installed the new version I (as a user) using the very natural About display cannot distinguish between the old download and the new one. That, to me, seems unfortunate.
First off, no, I haven't publicized anything yet. I made a new bundle with the Gtk+ changes and asked you guys to test it to verify that it fixes two bugs the other being bug 796867. Once I have confirmation that the Gtk+ patches fix the Mojave crashes then I can publicize it... though you seem to be of the opinion that I shouldn't. Consider that Linux and BSD package managers along with Fink and MacPorts on MacOS distribute GnuCash as a package containing only GnuCash. All of the dependencies are provided as separate packages; we provide all-in-one bundles only for MacOS and Windows, and this Gtk+ change affects only MacOS. We're not going to generate a new release with a new GnuCash version number just for MacOS, that would confuse the heck out of everyone.
The crash problem has been resolved. Thank you for that! However now the font size on all the screens has gone haywire.
1. Commenting on this bug, asking us to download and test the new bundle, is what I meant by publicizing. 2. Nowhere did I say the new bundle shouldn't be widely announced. Not sure where that came from. 2. I appreciate the complexities of building and supporting software across multi-platforms. All the more reason for users and developers to have a convenient, reliable way to identify just what software a user is running. That's all I was saying. Having said all that, I really do appreciate the new bundle you created once the Gtk fix was available, and GC has remained up for me consistently since I installed the new one.
Please clarify: 1) Will an official patch be released, or is the .dmg link from comment #10 meant for public consumption? 2) Does the 3.3-2 patch fix all the crashes in mac os 10.13.6 as well? Thanks! (In reply to John Ralls from comment #10) > I've uploaded > https://sourceforge.net/projects/gnucash/files/gnucash%20%28stable%29/3.3/ > Gnucash-Intel-3.3-2.dmg/download which includes Gtk patches that should fix > the problem. Please test.
The dmg in comment 10 is presently for testing. If you find that it solves your crashing problem you'll probably want to keep using it regardless of its "official" status. "Patch" doesn't make sense in this context. No, it's not likely to fix all crashes. That would be somewhat miraculous. I hope that if fixes the crashes in gtk_monitor_quartz_get_workarea reported in this bug and those in cairo_surface_set_device_scale reported in bug 796867.
*** Bug 796943 has been marked as a duplicate of this bug. ***
I was getting crashes about once a week, but haven't had a crash in the 2 weeks since I installed the build in comment 10. So it seems to have been fixed. macOS Mojave 10.14.1
(In reply to John Ralls from comment #2) > Another user reported on IRC that simply placing GnuCash in the Dock was > sufficient to prevent the same crash. Please try that. I use GnuCash 3.3 on two instances of OSX Mojave, both keeping crashing on startup. Even reinstalling wouldn't fix it -- only reboot would. Having said that, your "keep in dock" works wonders for me. Thanks a lot!
*** Bug 796790 has been marked as a duplicate of this bug. ***
The MacOS bundle for GnuCash 3.4 is built with gtk-3.24.2 patched to correct https://gitlab.gnome.org/GNOME/gtk/issues/1517 and https://gitlab.gnome.org/GNOME/gtk/issues/1518. Please test it.
This crash is due to Gtk bugs that have been fixed. The fixed Gtk will be included in GnuCash 3.5.
