Re: Lilypond 2.24.3 / iMac Sonoma / GS -dNODISPLAY fatal error

2023-11-28 Thread Eric
Well, that worked. (I can now continue collating the parts of at least the first movement of Robert Fuchs' 4th string quartet (1916) into score past bar 195 where I left my project... ;) ) Thanks much!! On Tue, Nov 28, 2023 at 5:38 AM Eric wrote: > Well, that’s depressing, I thought I had. I’ll

Re: Lilypond 2.24.3 / iMac Sonoma / GS -dNODISPLAY fatal error

2023-11-28 Thread Eric
Well, that’s depressing, I thought I had. I’ll get on that- thanks! On Tue, Nov 28, 2023 at 01:51 Jonas Hahnfeld wrote: > On Tue, 2023-11-28 at 01:33 -0500, Eric wrote: > > Installed 2.24.3 -docs using Macports, used convert-ly on a couple of > > files I'd last worked on in June, and received th

Re: Lilypond 2.24.3 / iMac Sonoma / GS -dNODISPLAY fatal error

2023-11-27 Thread Jonas Hahnfeld via LilyPond user discussion
On Tue, 2023-11-28 at 01:33 -0500, Eric wrote: > Installed 2.24.3 -docs using Macports, used convert-ly on a couple of > files I'd last worked on in June, and received the following (see > attached text file) after trying lilypond on one of those files and > adding the -V flag. I know that several

Re: Lilypond 2.24.3 / iMac Sonoma / GS -dNODISPLAY fatal error

2023-11-27 Thread Werner LEMBERG
> Installed 2.24.3 -docs using Macports, No, you didn't. In the very first line of your log file I can see '2.24.2'. The problem vanishes if you *really* install version 2.24.3 – or if you fix up your system setup so that the correct LilyPond version gets found. Werner

Lilypond 2.24.3 / iMac Sonoma / GS -dNODISPLAY fatal error

2023-11-27 Thread Eric
mode is local Current file position is 117 GPL Ghostscript 10.02.1: Unrecoverable error, exit code 1 warning: `(gs -dNODISPLAY -dNOSAFER -dNOPAUSE -dBATCH -dAutoRotatePages=/None -dPrinted=false /var/folders/g5/yyz_p0mn45b2hxv7bz3991fwgn/T//lilypond-tmp-577829)' failed (256) fatal error: failed files: "robertfuchsquartetno4_i.ly"

Re: arranger.ly with lilypond 2.25 : intlog2 fatal error

2023-08-18 Thread Raphael HARDY
Thank you Jean‌, it works perfectly now   De : "Jean Abou Samra" A : raphaelha...@sfr.fr,lilypond-user@gnu.org Envoyé: jeudi 17 Août 2023 23:53 Objet : Re: arranger.ly with lilypond 2.25 : intlog2 fatal error   pre,code,address { margin: 0px; } h1,h2,h3,h4,h5,h6 { margin-

Re: arranger.ly with lilypond 2.25 : intlog2 fatal error

2023-08-17 Thread Jean Abou Samra
https://github.com/gilles-th/arranger.ly/pull/2/files signature.asc Description: This is a digitally signed message part

arranger.ly with lilypond 2.25 : intlog2 fatal error

2023-08-17 Thread Raphael HARDY
‌Hello! I'm regularly using the arranger.ly library to make scores for children orchestras When trying to use it with lilypond v2.25, I sometimes get fatal error: intlog2 with negative argument: 0 For example using this small code that works as expected on 2.24 and triggers the fatal err

Re: Fatal error messages

2022-02-27 Thread David Wright
On Sun 27 Feb 2022 at 05:35:25 (+), Alasdair McAndrew wrote: > Many thanks - your thought about write access was right on the money. For > reasons I can't determine, the folder in which I'm working had user write > access removed, so its permissions were dr-xr-xr-x instead of drwxr-xr-x as

Re: Fatal error messages

2022-02-26 Thread Alasdair McAndrew
alentin > > Am Samstag, 26. Februar 2022, 01:40:20 CET schrieb Alasdair McAndrew: > > I've been using Lilypond, with Frescobaldi, on Linux happily for ages. But > > today, when I tried to compile a few bars in Frescobaldi, I got the error: > > > > > &g

Re: Fatal error messages

2022-02-26 Thread David Wright
On Sat 26 Feb 2022 at 00:40:20 (+), Alasdair McAndrew wrote: > I've been using Lilypond, with Frescobaldi, on Linux happily for ages. > But today, when I tried to compile a few bars in Frescobaldi, I got > the error: > > fatal error: cannot create temp file: my_musi

Re: Fatal error messages

2022-02-26 Thread Valentin Petzel
t the error: > > > fatal error: cannot create temp file: my_music_file.midi. 40227fc: > Permission denied > > > This is a first for me, and I tried running Lilypond on an old file, which > had compiled successfully before - again the same error. But also, when I &g

Fatal error messages

2022-02-25 Thread Alasdair McAndrew
I've been using Lilypond, with Frescobaldi, on Linux happily for ages. But today, when I tried to compile a few bars in Frescobaldi, I got the error: fatal error: cannot create temp file: my_music_file.midi. 40227fc: Permission denied This is a first for me, and I tried running Lil

Re: A fatal error with a new installation

2020-05-24 Thread Pierre Perol-Schneider
on is >> still open in many PDF viewers - they lock the file. Try closing your PDF >> viewer and trying again. >> >> -- >> Phil Holmes >> >> >> >> - Original Message - >> *From:* Alasdair McAndrew >> *To:* lilypond-user

Re: A fatal error with a new installation

2020-05-24 Thread Alasdair McAndrew
drew > *To:* lilypond-user Mailinglist > *Sent:* Sunday, May 24, 2020 1:43 PM > *Subject:* A fatal error with a new installation > > I have just installed Lilypond on Windows 10, following the instructions > to basically download, install, and add its path to the environment &g

Re: A fatal error with a new installation

2020-05-24 Thread Phil Holmes
, May 24, 2020 1:43 PM Subject: A fatal error with a new installation I have just installed Lilypond on Windows 10, following the instructions to basically download, install, and add its path to the environment variable. However, it won't compile; on a simple file; the log finishes

Re: A fatal error with a new installation

2020-05-24 Thread Andrew Bernard
I think it is a ghostscript version mismatch error., Have a search through the list archives about this. I use Linux so I cant comment apart from that, but I think this is commonly seen. Andrew

A fatal error with a new installation

2020-05-24 Thread Alasdair McAndrew
OINTS= 841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -dAutoRotatePages=/None -dPrinted= false -sOutputFile=/Users/amca/Lilypond/Butler_divisions_D_major.pdf -c.setpdfwrite -f./tmp-lilypond-c5ihri)' failed (1) fatal error: failed files: "C:\\Users\

Frescobaldi with LilyPond in WSL (was: Fatal error compiling large project (Win10/2.19.82))

2018-12-20 Thread Urs Liska
Am 19.12.18 um 21:56 schrieb Michael Gerdau: First step would be running Frescobaldi from its Git repository (and at that occasion test if the description is accurate and also works for Windows 10): https://github.com/wbsoft/frescobaldi/wiki/Run-Frescobaldi-3-from-Git-on-Windows Commenting as

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-19 Thread Michael Gerdau
> First step would be running Frescobaldi from its Git repository > (and at that occasion test if the description is accurate and also works > for Windows 10): > https://github.com/wbsoft/frescobaldi/wiki/Run-Frescobaldi-3-from-Git-on-Windows Commenting as I go: These are the discrepancies so fa

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-19 Thread Urs Liska
OK, great. First step would be running Frescobaldi from its Git repository (and at that occasion test if the description is accurate and also works for Windows 10): https://github.com/wbsoft/frescobaldi/wiki/Run-Frescobaldi-3-from-Git-on-Windows Am 19.12.18 um 18:54 schrieb Saul Tobin: I'd b

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-19 Thread Saul Tobin
I'd be happy to help test as well. On Wed, Dec 19, 2018, 9:32 AM Michael Gerdau > > Indeed, it's not a real problem to compose a special command line for > WSL Windows - if we know exactly how it should look like. > > Testing would be a little bit awkward, though > > I‘d be happy to test it. > >

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-19 Thread Michael Gerdau
> Indeed, it's not a real problem to compose a special command line for WSL > Windows - if we know exactly how it should look like. > Testing would be a little bit awkward, though I‘d be happy to test it. Kind regards, Michael ___ lilypond-user mailin

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-19 Thread Urs Liska
Am 19.12.18 um 17:12 schrieb Michael Gerdau: The Windows program "wsl.exe" is the interop program that ties things together. You can call it and pass it a command to be executed within the WSL environment. So, while I can simply say "lilypond" in a WSL shell, under a Windows shell I need to sa

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-19 Thread Michael Gerdau
> The Windows program "wsl.exe" is the interop program that ties things > together. You can call it and pass it a command to be executed within > the WSL environment. > > So, while I can simply say "lilypond" in a WSL shell, under a Windows > shell I need to say "wsl lilypond" to have the same

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-19 Thread David Kastrup
Aaron Hill writes: > On 2018-12-18 9:26 pm, Saul Tobin wrote: >> 1) Is there a technical obstacle or other reason preventing a Windows >> 64-bit build? > > I would presume that GUB can target 64-bit MinGW, I should be surprised, given just when GUB was under active development. It probably is no

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-19 Thread Aaron Hill
On 2018-12-19 3:43 am, Urs Liska wrote: Am 19. Dezember 2018 11:53:26 MEZ schrieb Aaron Hill : But if Frescobaldi needs to have a path to the LilyPond installation, then it can never be made to work with WSL. There is no* path to the WSL file system that a Windows program can access. Instead,

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-19 Thread Michael Gerdau
> How does one launch Linux programs then? Is that some specific "WSL Shell" > that you start and then have a bash or something? And this does mean theWSL > can only be used to do stuff on the Linux command line, no way to use Linux > commands triggered from Windows applications? Yes. As the n

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-19 Thread Urs Liska
Am 19. Dezember 2018 11:53:26 MEZ schrieb Aaron Hill : >On 2018-12-19 2:17 am, Michael Gerdau wrote: >>> Not really. >>> What I *can* say is this: >>> >>> * LilyPond installations are registered in Frescobaldi by pointing > >>> to >>> their executable. >>> * Frescobaldi calculates a path

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-19 Thread Aaron Hill
On 2018-12-19 2:17 am, Michael Gerdau wrote: Not really. What I *can* say is this: * LilyPond installations are registered in Frescobaldi by pointing to their executable. * Frescobaldi calculates a path relative to that executable and adds that to the library path in the LilyPond p

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-19 Thread Michael Gerdau
> Not really. > What I *can* say is this: > > * LilyPond installations are registered in Frescobaldi by pointing to > their executable. > * Frescobaldi calculates a path relative to that executable and adds > that to the library path in the LilyPond process's environment > > I have no

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-19 Thread Urs Liska
Am 19.12.18 um 08:09 schrieb Aaron Hill: On 2018-12-18 10:51 pm, Urs Liska wrote: This UI is populated by running LilyPond with the -dshow-available-fonts option, so it actually displays what LilyPond can really use. Ah, that greatly reduces confusion. However, my point still stands that one

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-18 Thread Aaron Hill
On 2018-12-18 10:51 pm, Urs Liska wrote: This UI is populated by running LilyPond with the -dshow-available-fonts option, so it actually displays what LilyPond can really use. Ah, that greatly reduces confusion. However, my point still stands that one needs to be aware that the fonts availabl

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-18 Thread Urs Liska
Am 19.12.18 um 07:49 schrieb Aaron Hill: On 2018-12-18 10:39 pm, Urs Liska wrote: I have no idea about the WSL, but in general I can't imagine there should be any source of confusion here. Frescobaldi wouldn't need to access anything font-like when it comes to LilyPond… But doesn't Frescobald

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-18 Thread Aaron Hill
On 2018-12-18 10:39 pm, Urs Liska wrote: I have no idea about the WSL, but in general I can't imagine there should be any source of confusion here. Frescobaldi wouldn't need to access anything font-like when it comes to LilyPond… But doesn't Frescobaldi have a UI for enumerating/previewing avai

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-18 Thread Urs Liska
Am 19.12.18 um 07:17 schrieb Aaron Hill: 2) Is it possible to run Lilypond under WSL from Frescobaldi? Possibly; however I do not use Frescobaldi, so I cannot speak from experience.  Theoretically, you should only need to configure Frescobaldi to launch LilyPond as "wsl /path/to/lilypond" so

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-18 Thread Aaron Hill
On 2018-12-18 9:26 pm, Saul Tobin wrote: 1) Is there a technical obstacle or other reason preventing a Windows 64-bit build? I would presume that GUB can target 64-bit MinGW, but I gather that this has not been a priority to deliver. Perhaps one of the developers could speak to this more com

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-18 Thread Saul Tobin
Thanks so much for the confirmation. A couple questions: 1) Is there a technical obstacle or other reason preventing a Windows 64-bit build? 2) Is it possible to run Lilypond under WSL from Frescobaldi? On Tue, Dec 18, 2018 at 8:36 PM Aaron Hill wrote: > On 2018-12-18 7:24 pm, Saul Tobin wrote:

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-18 Thread Aaron Hill
On 2018-12-18 7:24 pm, Saul Tobin wrote: It looks like the Fatal realloc error happens after the score finishes compiling while it's being written to a temporary file. At that point, the Lilypond process is using ~1.8 G of RAM. Is it possible I'm running into a 32 bit size limitation in Guile

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-18 Thread Saul Tobin
t; in combination with any of the others, but when I compile all together it > fails. I am also not using strftime anywhere. > > Saul > > > > On Sun, Dec 16, 2018 at 2:38 PM Ben wrote: > >> On 12/16/2018 5:32 PM, Saul Tobin wrote: >> >> Hi all, >> >&

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-16 Thread Saul Tobin
er it fails. I am also not using strftime anywhere. Saul On Sun, Dec 16, 2018 at 2:38 PM Ben wrote: > On 12/16/2018 5:32 PM, Saul Tobin wrote: > > Hi all, > > I'm getting a fatal error when I compile all of the movements of a large > project on 2.19.82 on Windows 10.

Re: Fatal error compiling large project (Win10/2.19.82)

2018-12-16 Thread Ben
On 12/16/2018 5:32 PM, Saul Tobin wrote: Hi all, I'm getting a fatal error when I compile all of the movements of a large project on 2.19.82 on Windows 10. I can compile the movements individually and in smaller combinations with no problems. There is no Lilypond error in the debug o

Fatal error compiling large project (Win10/2.19.82)

2018-12-16 Thread Saul Tobin
Hi all, I'm getting a fatal error when I compile all of the movements of a large project on 2.19.82 on Windows 10. I can compile the movements individually and in smaller combinations with no problems. There is no Lilypond error in the debug output, just "FATAL: memory error in reallo

Re: fatal error on MetronomeMark font-name override

2015-11-15 Thread Thomas Morley
2015-11-10 19:58 GMT+01:00 Kieren MacMillan : > Hi Abraham, > >> Normally, this should work, but it doesn't seem to for me: >> \override Score.MetronomeMark.font-series = #'medium > > This is what I wanted to do, of course… > But I think that “feature” is part of the [long-standing, and somewhat >

Re: fatal error on MetronomeMark font-name override

2015-11-10 Thread Kieren MacMillan
Hi Abraham, > Normally, this should work, but it doesn't seem to for me: > \override Score.MetronomeMark.font-series = #'medium This is what I wanted to do, of course… But I think that “feature” is part of the [long-standing, and somewhat irritiating] issue around MetronomeMark formatting. Chee

Re: fatal error on MetronomeMark font-name override

2015-11-10 Thread tisimst
ou can always use a \markup: \tempo \markup { \normal-text "Tempo Test" } c''1 Normally, this should work, but it doesn't seem to for me: \override Score.MetronomeMark.font-series = #'medium Best, Abraham -- View this message in context: http://lilypond.106903

Re: fatal error on MetronomeMark font-name override

2015-11-10 Thread tisimst
endEmail.jtp?type=node&node=183356&i=2> > https://lists.gnu.org/mailman/listinfo/lilypond-user > > > -- > If you reply to this email, your message will be added to the discussion > below: > > http://lilypond.1069038.n5.nabble.com/fatal-erro

Re: fatal error on MetronomeMark font-name override

2015-11-10 Thread Jacques Menu
> Le 10 nov. 2015 à 17:53, Kieren MacMillan a > écrit : > > Hi Jacques, > >> Removing Century makes that to work on my Mac. Is this font actually >> installed on your system? > > Yes. And it shows up in the list returned by calling > >lilypond -dshow-available-fonts x Same for me… >

Re: fatal error on MetronomeMark font-name override

2015-11-10 Thread Kieren MacMillan
Hi Jacques, > Removing Century makes that to work on my Mac. Is this font actually > installed on your system? Yes. And it shows up in the list returned by calling lilypond -dshow-available-fonts x Thanks, though. Kieren. Kieren MacMillan, composer ‣ websi

Re: fatal error on MetronomeMark font-name override

2015-11-10 Thread Jacques Menu
Hello Kieren, Removing Century makes that to work on my Mac. Is this font actually installed on your system? JM > Le 10 nov. 2015 à 16:56, Kieren MacMillan a > écrit : > > Hello all, > > In 2.19.30, the snippet > > SNIPPET BEGINS > \version "2.19.30" > > \score { > { \tempo "Tempo

fatal error on MetronomeMark font-name override

2015-11-10 Thread Kieren MacMillan
Hello all, In 2.19.30, the snippet SNIPPET BEGINS \version "2.19.30" \score { { \tempo "Tempo Test" c''1 } \layout { \context { \Score \override MetronomeMark.font-name = #"Century Schoolbook" } } } SNIPPET ENDS leads [on my computer] to the error warn

RE: fatal error

2014-10-15 Thread Mark Stephen Mrotek
-user@gnu.org Subject: Re: fatal error On Wed, Oct 15, 2014 at 4:16 PM, Urs Liska wrote: Can it be that you have the PDF file open in a viewer? On Windows it isn't possible to automatically reload the PDF, it runs into an error at the stage where your run seems to fail. HTH Urs

Re: fatal error

2014-10-15 Thread Abraham Lee
On Wed, Oct 15, 2014 at 4:16 PM, Urs Liska wrote: Can it be that you have the PDF file open in a viewer? On Windows it isn't possible to automatically reload the PDF, it runs into an error at the stage where your run seems to fail. HTH Urs That was my suspicion as well since it's a ghosts

Re: fatal error

2014-10-15 Thread Urs Liska
-dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile=./FanD.pdf -c.setpdfwrite -fFanD.ps)' failed (1) fatal error: failed files: "I:/Personal/Music/FanD.ly" Exited with return code 1. What must be done? Can it be that you have the PDF file open in a viewer? On Windows it isn't p

fatal error

2014-10-15 Thread Mark Stephen Mrotek
File=./FanD.pdf -c.setpdfwrite -fFanD.ps)' failed (1) fatal error: failed files: "I:/Personal/Music/FanD.ly" Exited with return code 1. What must be done? Thank you. Mark ___ lilypond-user mailing list lilypond-user@gnu.org https://

RE: fatal error

2013-07-19 Thread Mark Stephen Mrotek
openlilylib.org Sent: Thursday, July 18, 2013 11:27 PM To: lilypond-user@gnu.org Subject: Re: fatal error I can't test right now, but I think the reason for your problem is the following: When you say #'stencil = ##f it's not that you hide the object but you actually _remove_ its s

RE: fatal error

2013-07-19 Thread Mark Stephen Mrotek
Mr. Long: Thank you for the suggestion. I shall try the command. Mark -Original Message- From: Jim Long [mailto:lilyp...@umpquanet.com] Sent: Thursday, July 18, 2013 10:38 PM To: Mark Stephen Mrotek Cc: lilypond-user@gnu.org Subject: Re: fatal error On Thu, Jul 18, 2013 at 06:16:22PM

Re: fatal error

2013-07-18 Thread ul
arsonmark=ca.rr@gnu.org] On Behalf Of David Kastrup Sent: Thursday, July 18, 2013 5:13 PM To: lilypond-user@gnu.org Subject: Re: fatal error Eluze writes: probably the file is opened somewhere else? Could well be the problem. At any rate, warning: type check for `stencil' failed; value `#t

Re: fatal error

2013-07-18 Thread Jim Long
On Thu, Jul 18, 2013 at 06:16:22PM -0700, Mark Stephen Mrotek wrote: > Mr. Kastrup: > > Thank you for your reply and suggestion. > > I check the input and found three instances of "stencil:" > This one is the one the error message mentions: > \override TupletNumber #'stencil = ##t As the erro

RE: fatal error

2013-07-18 Thread Mark Stephen Mrotek
2013 5:13 PM To: lilypond-user@gnu.org Subject: Re: fatal error Eluze writes: > probably the file is opened somewhere else? Could well be the problem. At any rate, warning: type check for `stencil' failed; value `#t' must be of type `stencil' also points to an input problem. No

Re: fatal error

2013-07-18 Thread David Kastrup
Eluze writes: > probably the file is opened somewhere else? Could well be the problem. At any rate, warning: type check for `stencil' failed; value `#t' must be of type `stencil' also points to an input problem. No idea whether that will cause a fatal error, but even i

Re: fatal error

2013-07-18 Thread Eluze
probably the file is opened somewhere else? Eluze ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

fatal error

2013-07-18 Thread Mark Stephen Mrotek
.. warning: `(gs -q -dNOSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile=./13-2.pdf -c.setpdfwrite -f13-2.ps)' failed (1) fatal error: failed files: "I:/Personal/Music/13-2.ly" Exited

Re: Fatal Error on Launching 2.15.31

2012-03-05 Thread Colin Hall
On Tue, Mar 06, 2012 at 12:16:55AM +0100, Hans Aikema wrote: > On 5-3-2012 23:50, Colin Hall wrote: > >Hi Hans, > > > >On Sat, Mar 03, 2012 at 06:33:49PM +0100, Hans Aikema wrote: > >>It is a known bug presumed to be solved by the yet-to-be-released > >>2.15.32, which previously featured this list

Re: Fatal Error on Launching 2.15.31

2012-03-05 Thread 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 In

Re: Fatal Error on Launching 2.15.31

2012-03-05 Thread Colin Hall
Hi Rembrandt, On Sat, Mar 03, 2012 at 02:34:56PM -0600, Rembrandt Wolpert wrote: > Go into Lilypond.app/Contents/ > > open info.plist with your favourite editor and > > change Line 56: > > Build from Wed Feb 29 14:13:09 2012 > > to: > > Build from Wed Feb 29 14:13:09 2012 > > It

Re: Fatal Error on Launching 2.15.31

2012-03-05 Thread Colin Hall
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 > >ref

Re: Fatal Error on Launching 2.15.31

2012-03-05 Thread Klaus Föhl
Hello, Unpacking MacOS X x86: LilyPond 2.15.31-1 on MacMini Intel Core Duo does not run, only standard Applications icon. Adding the missing after the character sequence including spaces to Info.plist as noted in bug 2338. After reboot the Lilypond icon shows up. Double-clicking on the icon giv

Re: Fatal Error on Launching 2.15.31

2012-03-04 Thread David Kastrup
Rembrandt Wolpert writes: > Go into Lilypond.app/Contents/ > > open info.plist with your favourite editor and > > change Line 56: > > Build from Wed Feb 29 14:13:09 2012 > > to: > > Build from Wed Feb 29 14:13:09 2012 > > It's an error since version 2.15.30, in the bug-reports, but no

Re: Fatal Error on Launching 2.15.31

2012-03-04 Thread Graham Percival
On Sat, Mar 03, 2012 at 02:34:56PM -0600, Rembrandt Wolpert wrote: > It's an error since version 2.15.30, in the bug-reports, but not acted > upon (why? it's so easy?) I don't know. Why didn't you send a patch? - Graham ___ lilypond-user mailing list

Re: Fatal Error on Launching 2.15.31

2012-03-04 Thread Hans Aikema
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

Re: Fatal Error on Launching 2.15.31

2012-03-04 Thread Rembrandt Wolpert
Go into Lilypond.app/Contents/ open info.plist with your favourite editor and change Line 56: Build from Wed Feb 29 14:13:09 2012 to: Build from Wed Feb 29 14:13:09 2012 It's an error since version 2.15.30, in the bug-reports, but not acted upon (why? it's so easy?) Rembrand

Re: Fatal Error on Launching 2.15.31

2012-03-04 Thread Hans Aikema
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:

Re: Fatal Error on Launching 2.15.31

2012-03-04 Thread Hans Aikema
Top-posting as my bottom-posting mails seem to not get through to the list. Is a known bug to be solved in 2.15.32: http://code.google.com/p/lilypond/issues/detail?id=2338&can=7&q=info.plist&colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary Y

Re: Fatal Error on Launching 2.15.31

2012-03-04 Thread Hans Aikema
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:

Re: Fatal Error on Launching 2.15.31

2012-03-04 Thread David Kastrup
Eric writes: > 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

Re: Fatal Error on Launching 2.15.31

2012-03-03 Thread Colin Hall
; proper indenting. What operating system are you using? Have you used > > previous versions of LilyPond without this problem? > > > > Phil Holmes > > > > > > > > - Original Message - > > *From:* Eric > > *To:* lilypond-user@

Re: Fatal Error on Launching 2.15.31

2012-03-03 Thread Eric
ML and won't use > proper indenting. What operating system are you using? Have you used > previous versions of LilyPond without this problem? > > Phil Holmes > > > > - Original Message - > *From:* Eric > *To:* lilypond-user@gnu.org > *Sent:* Saturda

Re: Fatal Error on Launching 2.15.31

2012-03-03 Thread Phil Holmes
Sent: Saturday, March 03, 2012 3:01 PM Subject: Fatal Error on Launching 2.15.31 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

Fatal Error on Launching 2.15.31

2012-03-03 Thread Eric
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: 3/3/12 9:52:59.193 AM [0x0-0x916916].org.lilypond.lilypond: Traceback (most