Re: Fwd: ghostscript fails on pdf generation

2017-06-07 Thread David Wright
On Thu 08 Jun 2017 at 06:08:07 (+0200), N. Andrew Walsh wrote: > Hi David, > > On Thu, Jun 8, 2017 at 2:37 AM, David Wright > wrote: > > > > > Just to clarify, is this > > …lilypond-2.19.61/bin/lilypond > > > > That one ↑ Good. > > or > > …lilypond-2.19.61/lilypond/usr/bin/lilypond > > > > >

Re: Fwd: ghostscript fails on pdf generation

2017-06-07 Thread N. Andrew Walsh
Hi David, On Thu, Jun 8, 2017 at 2:37 AM, David Wright wrote: > > Just to clarify, is this > …lilypond-2.19.61/bin/lilypond > That one ↑ or > …lilypond-2.19.61/lilypond/usr/bin/lilypond > > > > Maybe if it is only calling "lilypond" (i.e. without an absolute path > to > > > the executable) the

Re: Fwd: ghostscript fails on pdf generation

2017-06-07 Thread David Wright
On Wed 07 Jun 2017 at 17:50:52 (+0200), N. Andrew Walsh wrote: > On Wed, Jun 7, 2017 at 4:02 PM, Urs Liska wrote: > > > How exactly is LilyPond registered in Frescobaldi for you? > > > > Absolute path to the binary installed with the package. Just to clarify, is this …lilypond-2.19.61/bin/lilyp

Fwd: ghostscript fails on pdf generation

2017-06-07 Thread N. Andrew Walsh
file to point to PyQt5.QtWebEngineWidgets instead? Cheers, A -- Forwarded message -- From: N. Andrew Walsh Date: Wed, Jun 7, 2017 at 4:30 PM Subject: Re: ghostscript fails on pdf generation To: Urs Liska Hi Urs, On Wed, Jun 7, 2017 at 4:02 PM, Urs Liska wrote: > How exac

Re: ghostscript fails on pdf generation

2017-06-07 Thread Urs Liska
Am 07.06.2017 um 15:54 schrieb N. Andrew Walsh: > Hi List, > > this error has cropped up again for me. I'll summarize briefly: > > compiling a document within frescobaldi (3.0.0) and lilypond-2.19.61 > fails with gs error 256. However, this only fails on my laptop, not my > main machine (which is

Re: ghostscript fails on pdf generation

2017-06-07 Thread N. Andrew Walsh
Hi List, this error has cropped up again for me. I'll summarize briefly: compiling a document within frescobaldi (3.0.0) and lilypond-2.19.61 fails with gs error 256. However, this only fails on my laptop, not my main machine (which is running the same versions). running the failing gs command on

Re: ghostscript fails on pdf generation

2017-02-25 Thread David Wright
On Sat 25 Feb 2017 at 13:06:02 (+0100), N. Andrew Walsh wrote: > Hi List, > > so, I did some digging regarding this error I've been getting with pdf > output (see below). I found this note to lilypond-users from two years ago: > https://lists.gnu.org/archive/html/lilypond-user/2014-01/msg00932.htm

Re: ghostscript fails on pdf generation

2017-02-25 Thread N. Andrew Walsh
Hi List, so, I did some digging regarding this error I've been getting with pdf output (see below). I found this note to lilypond-users from two years ago: https://lists.gnu.org/archive/html/lilypond-user/2014-01/msg00932.html The money line is to comment out the last line of /usr/share/ghostscri

Re: ghostscript fails on pdf generation

2017-02-15 Thread Wols Lists
On 13/02/17 15:23, David Wright wrote: >> It seems daft to me that you need "w" permissions, and I haven't >> > experimented deeply with it, but if I have access to a file, why >> > shouldn't I be able to create a link to it? > Because it's a security risk. Geriatric unixers might wonder why their

Re: ghostscript fails on pdf generation

2017-02-13 Thread David Wright
On Sun 12 Feb 2017 at 21:17:54 (+0100), N. Andrew Walsh wrote: > > > > The import of my post was to raise the question of whether the parts > > of your LP system are incompatible and, if so, whether that was > > brought about by the source of your LP system (which would probably > > affect many peo

Re: ghostscript fails on pdf generation

2017-02-13 Thread David Wright
On Sun 12 Feb 2017 at 21:03:01 (+), Wols Lists wrote: > On 12/02/17 19:59, David Wright wrote: > > In the case cited from June, the OP was using an odd system (eg it > > used # as a *user* prompt) whose tar couldn't create symlinks when > > it unpacked an archive (permissions messages); they ha

Re: ghostscript fails on pdf generation

2017-02-12 Thread Wols Lists
On 12/02/17 19:59, David Wright wrote: > In the case cited from June, the OP was using an odd system (eg it > used # as a *user* prompt) whose tar couldn't create symlinks when > it unpacked an archive (permissions messages); they had to be > created manually. I don't know when it started happenin

Re: ghostscript fails on pdf generation

2017-02-12 Thread N. Andrew Walsh
Hi David, > > The import of my post was to raise the question of whether the parts > of your LP system are incompatible and, if so, whether that was > brought about by the source of your LP system (which would probably > affect many people) or just a problem in your own setup. Well, the best I c

Re: ghostscript fails on pdf generation

2017-02-12 Thread David Wright
On Sun 12 Feb 2017 at 19:38:47 (+0100), N. Andrew Walsh wrote: > > The first example on: > > http://lists.gnu.org/archive/html/lilypond-user/2016-06/msg00123.html > > > > $ ~/lilypond-2.19.42.1/bin/lilypond e.ly > > > > runs this (now newer) script: > > > > #!/bin/sh > > me=`basename $0` > > export

Re: ghostscript fails on pdf generation

2017-02-12 Thread N. Andrew Walsh
Hi David, > > The first example on: > http://lists.gnu.org/archive/html/lilypond-user/2016-06/msg00123.html > > $ ~/lilypond-2.19.42.1/bin/lilypond e.ly > > runs this (now newer) script: > > #!/bin/sh > me=`basename $0` > export LD_LIBRARY_PATH="/home/david/lilypond-2.19.49-1/lilypond/usr/lib" > e

Re: ghostscript fails on pdf generation

2017-02-12 Thread David Wright
On Sun 12 Feb 2017 at 09:15:49 (+0100), N. Andrew Walsh wrote: > > Does this error appear when you run lilypond from the command line or only > > when you run it from Frescobaldi? > This error occurs from the command line as well. It also failed to find the > openlilylib installation, but that's ju

Re: ghostscript fails on pdf generation

2017-02-12 Thread Simon Albrecht
On 12.02.2017 09:15, N. Andrew Walsh wrote: I don't know how to add a search path from the command line. That’s by using the -I command line option, which you might include in an alias as well. Best, Simon ___ lilypond-user mailing list lilypond-u

Re: ghostscript fails on pdf generation

2017-02-12 Thread N. Andrew Walsh
Hi Urs, > > Does this error appear when you run lilypond from the command line or only > when you run it from Frescobaldi? This error occurs from the command line as well. It also failed to find the openlilylib installation, but that's just because I don't know how to add a search path from the

Re: ghostscript fails on pdf generation

2017-02-11 Thread Urs Liska
Am 12. Februar 2017 02:25:42 MEZ schrieb David Wright : >On Sat 11 Feb 2017 at 20:36:33 (+0100), N. Andrew Walsh wrote: >> I realize this isn't strictly an issue with Lily, but pdf output >recently >> started failing. I see the following message in the console output: >> >> Layout output to `/t

Re: ghostscript fails on pdf generation

2017-02-11 Thread David Wright
On Sat 11 Feb 2017 at 20:36:33 (+0100), N. Andrew Walsh wrote: > I realize this isn't strictly an issue with Lily, but pdf output recently > started failing. I see the following message in the console output: > > Layout output to `/tmp/lilypond-CFV9h3'... > Converting to `Reinhold Urmetzer - Lamen

Re: ghostscript fails on pdf generation

2017-02-11 Thread Thomas Morley
2017-02-11 23:40 GMT+01:00 Simon Albrecht : > On 11.02.2017 21:20, N. Andrew Walsh wrote: >> >> Hi Joram, >> >> >> Does it also happen when the file name does not contain spaces? >> >> >> yes, it does. I tried with a renamed file, and got the same error. > > > I think you can report this to the

Re: ghostscript fails on pdf generation

2017-02-11 Thread Simon Albrecht
On 11.02.2017 21:20, N. Andrew Walsh wrote: Hi Joram, Does it also happen when the file name does not contain spaces? yes, it does. I tried with a renamed file, and got the same error. I think you can report this to the bug list. Even if it’s not strictly a LilyPond issue, we might inv

Re: ghostscript fails on pdf generation

2017-02-11 Thread N. Andrew Walsh
Hi Joram, > > Does it also happen when the file name does not contain spaces? > yes, it does. I tried with a renamed file, and got the same error. Cheers, A ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/li

Re: ghostscript fails on pdf generation

2017-02-11 Thread Noeck
Hi Andrew, Am 11.02.2017 um 20:36 schrieb N. Andrew Walsh: > -sOutputFile=Reinhold Urmetzer - Lamento di Achille.pdf Does it also happen when the file name does not contain spaces? The part above from your quoted gs command is likely not working if executed exactly like this. -sOutputFile="Reinho

Re: ghostscript fails on pdf generation

2017-02-11 Thread N. Andrew Walsh
Hi Jean, I have 32GB of RAM. I have never seen that tick over 20% use, for anything, so I don't think it's an issue with memory. Cheers, A On Sat, Feb 11, 2017 at 9:08 PM, Jean Brefort wrote: > Le samedi 11 février 2017 à 20:55 +0100, N. Andrew Walsh a écrit : > > PS- ghostscript on my system

Re: ghostscript fails on pdf generation

2017-02-11 Thread Jean Brefort
Le samedi 11 février 2017 à 20:55 +0100, N. Andrew Walsh a écrit : > PS- ghostscript on my system (gentoo Linux) recently updated: on Jan > 31st to 9.20-r1. Can anybody else check and see if they encounter the > same issue with that version of ghostscript? Trawling back through > old github issues

Re: ghostscript fails on pdf generation

2017-02-11 Thread N. Andrew Walsh
PS- ghostscript on my system (gentoo Linux) recently updated: on Jan 31st to 9.20-r1. Can anybody else check and see if they encounter the same issue with that version of ghostscript? Trawling back through old github issues and forum archives shows a number of times over the years where a ghostscri

ghostscript fails on pdf generation

2017-02-11 Thread N. Andrew Walsh
Hi List, I realize this isn't strictly an issue with Lily, but pdf output recently started failing. I see the following message in the console output: Layout output to `/tmp/lilypond-CFV9h3'... Converting to `Reinhold Urmetzer - Lamento di Achille.pdf'... warning: `(gs -q -dSAFER -dDEVICEWIDTHPOI