[GNC] GnuCash 5.16 Release - Crash on Splash Screen

[John Ralls]

Looks like guile-3.0.11 uses a couple of functions that aren’t available in 10.13 and the compiler didn’t catch it. I’ve re-bundled GnuCash 5.16 with guile 3.0.10 (that’s what was in 5.15) and tested it on an old 2011 MacBookAir that’s stuck at 10.13.

145358b2d28228d0a4d249c8150364c52c5808e5c35be9ebbec427c2098933aa  Gnucash-Intel-5.16-2.dmg
https://sourceforge.net/projects/gnucash/files/gnucash (stable)/5.16/Gnucash-Intel-5.16-2.dmg/download <https://sourceforge.net/projects/gnucash/files/gnucash%20(stable)/5.16/Gnucash-Intel-5.16-2.dmg/download>
https://github.com/Gnucash/gnucash/releases/download/5.16/Gnucash-Intel-5.16-2.dmg

Regards,
John Ralls

> On Jun 29, 2026, at 02:03, G R Hewitt <hewittgr at gmail.com> wrote:
> 
> Hello,
> 
> MacPro 2010, 5.1, High Sierra 10.13.6
> Currently running Gnucash Version: 5.12
> Build ID: 5.12+(2025-06-28)
> Finance::Quote: 1.56
> 
> Gnucash  5.16 just displays the splash screen briefly and then I get the
> 'Gnucash quit unexpectedly' message, the crash reason is below.
> ===========
> Crashed Thread:        0  Dispatch queue: com.apple.main-thread
> 
> Exception Type:        EXC_CRASH (SIGABRT)
> Exception Codes:       0x0000000000000000, 0x0000000000000000
> Exception Note:        EXC_CORPSE_NOTIFY
> 
> Termination Reason:    DYLD, [0x4] Symbol missing
> 
> Dyld Error Message:
>  Symbol not found: _pthread_jit_write_protect_np
>  Referenced from: /Applications/Gnucash
> 2.app/Contents/MacOS/../Resources/lib/libguile-3.0.1.dylib
>  Expected in: /usr/lib/libSystem.B.dylib
> 
> =============
> 
> If the above is not enough I can send the full readout, but it is a lot.
> Help resolving this error is appreciated, thanks in advance.
> 
> GH
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at 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.