Re: Fatal Error on Launching 2.15.31

[Hans Aikema]

On 5-3-2012 23:50, Colin Hall wrote:
> Hi Hans,
>
> On Sat, Mar 03, 2012 at 06:33:49PM +0100, Hans Aikema wrote:
> > On 3-3-2012 16:01, Eric wrote:
> > > This may belong on the developer list- apologies.
> > > Immediately after downloading and expanding 2.15.31 in the version
> > > appropriate for my Macintosh (10.7.3 Intel Duo) I got a crash
> > > reflected in my console with these message:
> > >
> > > ...
> > > Apologies for the dump but not sure what to do with that! Seemed
> > > to deserve a report somewhere - if not here, again apologies, will
> > > forward to if and as I can.
> > > Eric
> > It is a known bug presumed to be solved by the yet-to-be-released
> > 2.15.32, which previously featured this list as "Mac info.plist
> > problem":
> >
> > http://code.google.com/p/lilypond/issues/detail?id=2338
> >
> > You can solve it locally by adding the missing</string>  in
> > info.plist
> I saw this post from you, a few days ago, in which you report seeing Issue 2338 
> with Lilypond on your MacOS X machine.
>
> I encourage you to check out the new development release 2.15.32 which contains 
> a candidate fix for Issue 2338.
>
> Would be great to hear that the new release works ok for you.
>
> Cheers,
> Colin.
Colin,

Already noticed Graham Percival's 'news item' release-commit in git and 
was eagerly awaiting the finishing up by actually releasing 2.15.32.
Just downloaded, unpacked and installed and it works like a charm out of 
the box (Macbook Pro early 2011; Mac OS X Lion 10.7.3 (11DF50))

If there is any kind of automated test-cases that can be run natively 
(no macports) on the Mac, just let me know and I'll be happy to run 
them. As a developer (Java) I'm fine with command line programs / shell 
scripts, it's just that I've had some bad experiences in the past with 
trashing a Mac for recovery to factory defaults (full OS re-install) by 
being to eager to try some macports hacks (including a lilypond 'build 
from scratch'), overwriting crucial system libraries in the process, so 
I tend to avoid that course of action nowadays.
My MacBook is meant as an 'it just works' device (with lilypond as the 
exception where I tend to jump the unstable bandwagon after a tag or 10 
into unstable). I have other systems (VMs; Windows desktop) for the 
experimental stuff.

regards,
Hans