[opensuse] ghostscript + gv / epstopdf problems after recent update
Hi, I'm on LEAP 15.0, and a recent update of ghostscript (gs) to version 9.25 broke some functionality in the interplay between gv / epstopdf and ghostscript. The attached simple eps file displays find in gs, but loading it in gv, or trying to convert it to pdf reports the error listed below. Maybe it's some incompatibility between the new version of gs, and gv / epstopdf which call gs, but I'm not sure how to test this on my system. Any suggestions will be much appreciated. Boris Error: /nocurrentpoint in --currentpoint--GPL Ghostscript 9.25: Unrecoverable error, exit code 1 Operand stack: Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1999 1 3 %oparray_pop 1998 1 3 %oparray_pop --nostringval-- 1982 1 3 %oparray_pop 1868 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- Dictionary stack: --dict:965/1684(ro)(G)-- --dict:0/20(G)-- --dict:82/200(L)-- --dict:12/20(L)-- Current allocation mode is local Current file position is 661
Hello, In the Message; Subject : [opensuse] ghostscript + gv / epstopdf problems after recent update Message-ID : <CABkVZH1Nx-xHpLCdfxmK7djCRgVFduUaio-G8pnJLNB2B_bsew@mail.gmail.com> Date & Time: Mon, 5 Nov 2018 11:48:00 +0000 Boris Gaensicke <boris.gaensicke@gmail.com> has written:
Hi,
I'm on LEAP 15.0, and a recent update of ghostscript (gs) to version 9.25 broke some functionality in the interplay between gv / epstopdf and ghostscript.
The attached simple eps file displays find in gs, but loading it in gv, or trying to convert it to pdf reports the error listed below.
Maybe it's some incompatibility between the new version of gs, and gv / epstopdf which call gs, but I'm not sure how to test this on my system. Any suggestions will be much appreciated.
Boris
Error: /nocurrentpoint in --currentpoint--GPL Ghostscript 9.25: Unrecoverable error, exit code 1
Operand stack:
Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1999 1 3 %oparray_pop 1998 1 3 %oparray_pop --nostringval-- 1982 1 3 %oparray_pop 1868 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- Dictionary stack: --dict:965/1684(ro)(G)-- --dict:0/20(G)-- --dict:82/200(L)-- --dict:12/20(L)-- Current allocation mode is local Current file position is 661 [2 test.eps <application/postscript (base64)>]
It's a ghostscript 9.25's bug. So, I'm using self-built ghostscript 9.24 on leap 42.3. Thanks, --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computers. Not with Me!" "No..., with money." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi Masaru, thanks - I downgraded to ghostscript 9.23, and the problem is fixed. Do you know if it is worth reporting this problem to the ghostscript developers? Boris On Mon, 5 Nov 2018 at 12:40, Masaru Nomiya <nomiya@galaxy.dti.ne.jp> wrote:
Hello,
In the Message;
Subject : [opensuse] ghostscript + gv / epstopdf problems after recent update Message-ID : <CABkVZH1Nx-xHpLCdfxmK7djCRgVFduUaio-G8pnJLNB2B_bsew@mail.gmail.com> Date & Time: Mon, 5 Nov 2018 11:48:00 +0000
Boris Gaensicke <boris.gaensicke@gmail.com> has written:
Hi,
I'm on LEAP 15.0, and a recent update of ghostscript (gs) to version 9.25 broke some functionality in the interplay between gv / epstopdf and ghostscript.
The attached simple eps file displays find in gs, but loading it in gv, or trying to convert it to pdf reports the error listed below.
Maybe it's some incompatibility between the new version of gs, and gv / epstopdf which call gs, but I'm not sure how to test this on my system. Any suggestions will be much appreciated.
Boris
Error: /nocurrentpoint in --currentpoint--GPL Ghostscript 9.25: Unrecoverable error, exit code 1
Operand stack:
Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1999 1 3 %oparray_pop 1998 1 3 %oparray_pop --nostringval-- 1982 1 3 %oparray_pop 1868 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- Dictionary stack: --dict:965/1684(ro)(G)-- --dict:0/20(G)-- --dict:82/200(L)-- --dict:12/20(L)-- Current allocation mode is local Current file position is 661 [2 test.eps <application/postscript (base64)>]
It's a ghostscript 9.25's bug.
So, I'm using self-built ghostscript 9.24 on leap 42.3.
Thanks,
--- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computers. Not with Me!" "No..., with money."
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/11/2018 13.46, Boris Gaensicke wrote:
Hi Masaru,
thanks - I downgraded to ghostscript 9.23, and the problem is fixed.
Do you know if it is worth reporting this problem to the ghostscript developers?
If it is a mandatory update, maybe it should be reverted. Thus if it is mandatory update I think that yes, you should report in openSUSE bugzilla. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
On 11/05/2018 06:46 AM, Boris Gaensicke wrote:
Do you know if it is worth reporting this problem to the ghostscript developers?
It's always worth making sure the bug is either reported on the opensuse bugzilla or upstream. The opensuse devs do a good job coordinating bugs with upstream. If it is effecting opensuse, a bug here is valid and the devs handling the bug can give you more guidance on whether further action is needed. If there is already an upstream bug, include the link in the opensuse bug so it can be tracked along with upstream. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, In the Message; Subject : [opensuse] ghostscript + gv / epstopdf problems after recent update Message-ID : <CABkVZH1Nx-xHpLCdfxmK7djCRgVFduUaio-G8pnJLNB2B_bsew@mail.gmail.com> Date & Time: Mon, 5 Nov 2018 11:48:00 +0000 Boris Gaensicke <boris.gaensicke@gmail.com> has written:
Hi,
I'm on LEAP 15.0, and a recent update of ghostscript (gs) to version 9.25 broke some functionality in the interplay between gv / epstopdf and ghostscript.
The attached simple eps file displays find in gs, but loading it in gv, or trying to convert it to pdf reports the error listed below.
Maybe it's some incompatibility between the new version of gs, and gv / epstopdf which call gs, but I'm not sure how to test this on my system. Any suggestions will be much appreciated.
Boris
Error: /nocurrentpoint in --currentpoint--GPL Ghostscript 9.25: Unrecoverable error, exit code 1
Operand stack:
Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1999 1 3 %oparray_pop 1998 1 3 %oparray_pop --nostringval-- 1982 1 3 %oparray_pop 1868 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- Dictionary stack: --dict:965/1684(ro)(G)-- --dict:0/20(G)-- --dict:82/200(L)-- --dict:12/20(L)-- Current allocation mode is local Current file position is 661 [2 test.eps <application/postscript (base64)>]
I found a solution to the problem. I'll upload this to bugzilla. Thanks, --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computers. Not with Me!" "No..., with money." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/06/2018 05:32 AM, Masaru Nomiya wrote:
I found a solution to the problem.
I'll upload this to bugzilla.
It would be nice if you posted a link to the bugzilla bug so those interested could follow the progress and add any additional information they may have. Also, you mail is being sent with html formatting. You should locate the option in your mailer that allows you to send "plain-text" e-mails to this list. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 6 Nov 2018 10:48:49 -0600 "David C. Rankin" <drankinatty@suddenlinkmail.com> wrote:
Also, you mail is being sent with html formatting. You should locate the option in your mailer that allows you to send "plain-text" e-mails to this list.
FWIW, I don't see any HTML formatting nor even an HTML part. Content-Type: text/plain; charset=ISO-2022-JP -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/06/2018 11:07 AM, Dave Howorth wrote:
FWIW, I don't see any HTML formatting nor even an HTML part.
Content-Type: text/plain; charset=ISO-2022-JP
Dave, You are correct sir. It must be a translation issue, because the text seems to come through as 14pt Arial (or something similar). So Masaru, I apologize, it isn't your fault. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
All, this was the first time I used this mailing list, and it's been amazing to see how quick things move. And thanks to Masaru for taking this to bugzilla. Boris -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/11/2018 17.48, David C. Rankin wrote:
Also, you mail is being sent with html formatting. You should locate the option in your mailer that allows you to send "plain-text" e-mails to this list.
It is not html, it is some other thing. Charset perhaps, that Thunderbird renders differently. Yes, that's it. Preferences/Display/Formatting. Fonts for: Latin -> Monospace: Monospace. Fonts for: Japanese -> Monospace: Default (Source Cod. size 16). -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 06/11/2018 19:22, Carlos E. R. wrote:
It is not html, it is some other thing.
https://www.reddit.com/r/answers/comments/uzn7c/why_do_latin_characters_on_c... ...? -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, Křižíkova 148/34, 186-00 Praha 8 - Karlín, Czechia Email: lproven@suse.com - Office telephone: +420 284 241 084 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/06/2018 12:22 PM, Carlos E. R. wrote:
It is not html, it is some other thing.
Charset perhaps, that Thunderbird renders differently.
Yes, that's it.
Preferences/Display/Formatting.
Fonts for: Latin -> Monospace: Monospace. Fonts for: Japanese -> Monospace: Default (Source Cod. size 16).
Brilliant Carlos, thanks I've not encountered a translation issue like that before (that's pushing 15 years of TB use too :) I guess I've been a digital hermit (or the wider push to Unicode/wchar support with all translations is finally coming of age...) -- David C. Rankin, J.D.,P.E.
On 08/11/2018 09.33, David C. Rankin wrote:
On 11/06/2018 12:22 PM, Carlos E. R. wrote:
It is not html, it is some other thing.
Charset perhaps, that Thunderbird renders differently.
Yes, that's it.
Preferences/Display/Formatting.
Fonts for: Latin -> Monospace: Monospace. Fonts for: Japanese -> Monospace: Default (Source Cod. size 16).
Brilliant Carlos, thanks
I've not encountered a translation issue like that before (that's pushing 15 years of TB use too :) I guess I've been a digital hermit (or the wider push to Unicode/wchar support with all translations is finally coming of age...)
Apparently TB supports using a different font for each language description, possibly because there are fonts that do not have letters for some languages. I don't know this moment if we can set a font for all languages in a few clicks, then modify the fonts of some language that fails. Yes, there is a default font, but that doesn't change the current settings of the languages. There is no button to apply defaults to all languages. And there are MANY languages. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Hello, In the Message; Subject : Re: [opensuse] Re: ghostscript + gv / epstopdf problems after recent update Message-ID : <3b7fadbd-2778-3b2a-3250-3c60e85384e0@suddenlinkmail.com> Date & Time: Tue, 6 Nov 2018 10:48:49 -0600 [DCR] == "David C. Rankin" <drankinatty@suddenlinkmail.com> has written: DCR> On 11/06/2018 05:32 AM, Masaru Nomiya wrote: MN>> I found a solution to the problem. MN>> MN>> I'll upload this to bugzilla. DCR> It would be nice if you posted a link to the bugzilla bug so DCR> those interested could follow the progress and add any DCR> additional information they may have. Here, it is. https://bugzilla.novell.com/show_bug.cgi?id=1108027 DCR> Also, you mail is being sent with html formatting. You should DCR> locate the option in your mailer that allows you to send DCR> "plain-text" e-mails to this list. I never use html-format. Just a plain text mail! See, my mail's source. Regards, --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computers. Not with Me!" "No..., with money." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, In the Message; Subject : [opensuse] Re: ghostscript + gv / epstopdf problems after recent update Message-ID : <87in193b08.wl-nomiya@galaxy.dti.ne.jp> Date & Time: Wed, 07 Nov 2018 10:57:27 +0900 Masaru Nomiya <nomiya@galaxy.dti.ne.jp> has written: [...] DCR> It would be nice if you posted a link to the bugzilla bug so DCR> those interested could follow the progress and add any DCR> additional information they may have.
Here, it is.
I've got no response from maintainer, so I convinced misposting my bug report. I reposted it again 3 day ago; https://bugzilla.novell.com/show_bug.cgi?id=1115126&GoAheadAndLogIn=1 BTW, I received the ghostscript-9.26 rc1's release announce mail last night. I got it, and checked source files. I confirmed the important security fixes were applied. So, I made ghostscript-9.26rc1-1.1.arc.rpm & bult & installed. As expected, It works fine. But, no response until now. So, I checked my bug report's status. I found the response; Johannes Meixner 2018-11-09 13:18:23 UTC Cf. https://ghostscript.com/pipermail/gs-devel/2018-November/010126.html and https://ghostscript.com/pipermail/gs-devel/2018-November/010127.html This reply means, in short, 'Wait or Use ghostscript 9.26rc1'. Which on? > Johannes Meinxner In fact, the ghostscript-9.26rc1 is not places within the update repository, now. That is, he won't release the bug fixed ghostscript 9.25! Od cource, I DID claim. Thanks, --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computers. Not with Me!" "No..., with money." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Boris Gaensicke -
Carlos E. R. -
Dave Howorth -
David C. Rankin -
Liam Proven -
Masaru Nomiya