1. Forum
  2. Usenet
  3. COMP.LANG.POSTSCRIPT

  • errors in ghostscript 9.51, but OK with ghostscript 9.50

    From ken@21:1/5 to All on Fri Jun 5 12:04:07 2020
    In article <rbd7eh$6d9$1@adenine.netfront.net>, jszhao@yeah.net says...

    Any help?

    Wihtout seeing the PostScript file ? No I can't really say there's any
    likely way to help.

    If you think you've found a bug my advice would be to report a bug at https://bugs.ghostscript.com remember to attach the file that exhibits
    the error and the command line.

    Ghostscript 9.51 was superseded one week later by Ghostscript 9.52,
    although the differences were minor I'd suggest you should be using that
    rather than 9.51.

    Regards,

    Ken Sharp

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jinsong Zhao@21:1/5 to All on Fri Jun 5 18:40:15 2020
    Hi there,

    I have a postscript file (thesis.ps) generated by dvips. It can be
    convert to PDF file with ghostscript 9.50 using the following command:

    gswin64c -dNOSAFER -dNOPAUSE -dBATCH -sDEVICE=pdfwrite
    -dPDFSETTINGS=/printer -dCompatibilityLevel=1.4 -dMaxSubsetPct=100 -dSubsetFonts=true -dEmbedAllFonts=true -sOutputFile=thesis.pdf thesis.ps

    However, when I update ghostscript to 9.51, error appears:

    Error: /ioerror in --colorimage--
    Operand stack:
    175.032 -169.639 175.032 -159.639 229.531 -159.639
    229.531 -145.88 288.977 -169.639 288.977 -159.639 229.531
    -159.639 229.531 -145.88 131.17 -217.924 121.17 -217.924
    121.17 -317.789 151.165 -317.789 218.84 -288.149 228.84
    -288.149 288.977 -288.149 288.977 -186.77
    Execution stack:
    %interp_exit .runexec2 --nostringval-- colorimage
    --nostringval-- 2 %stopped_push --nostringval-- colorimage
    colorimage false 1 %stopped_push 1990 1 3 %oparray_pop
    1989 1 3 %oparray_pop 1977 1 3 %oparray_pop 1833 1 3
    %oparray_pop --nostringval-- %errorexec_pop .runexec2
    --nostringval-- colorimage --nostringval-- 2 %stopped_push --nostringval-- colorimage 1863 39 7 %oparray_pop
    Dictionary stack:
    --dict:750/1123(ro)(G)-- --dict:1/20(G)-- --dict:150/200(L)-- --dict:653/675(L)-- --dict:71/200(L)-- --dict:176/300(L)-- --dict:139/200(L)--
    Current allocation mode is local
    Last OS error: No such file or directory
    Current file position is 38698441
    GPL Ghostscript 9.51: Unrecoverable error, exit code 1

    Any help? Thanks in advance.

    Best,
    Jinsong

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From ken@21:1/5 to All on Fri Jun 5 13:09:16 2020
    In article <rbdbcm$f5n$1@adenine.netfront.net>, jszhao@yeah.net says...

    On 2020/6/5 19:04, ken wrote:
    In article <rbd7eh$6d9$1@adenine.netfront.net>, jszhao@yeah.net says...

    Any help?

    Wihtout seeing the PostScript file ? No I can't really say there's any likely way to help.

    I don't know how to prepare a minimal work example. I run the above
    command with my thesis with size larger than 30 MB.

    Well, Ghostscript will pause between pages if you don't specify -
    dNOPAUSE, and often will display which page its processing anyway. So
    you should be able to work out which page is causing the problem. You
    could then try printing just that page to PostScript, or at least all
    the pages up to and including that page if hte one page on its own
    doesn't cause a problem.

    If all else fails you can supply the entire file, 30MB isn't that large.


    Ghostscript 9.51 was superseded one week later by Ghostscript 9.52, although the differences were minor I'd suggest you should be using that rather than 9.51.

    I also run the same command with 9.52. The same error message.

    I can't say I'm hugely surprised, it 'looks like' there's a problem with
    the PostScript, though as I say, without seeing the PostScript contents
    I can't really be sure.



    Ken

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jinsong Zhao@21:1/5 to ken on Fri Jun 5 19:47:31 2020
    On 2020/6/5 19:04, ken wrote:
    In article <rbd7eh$6d9$1@adenine.netfront.net>, jszhao@yeah.net says...

    Any help?

    Wihtout seeing the PostScript file ? No I can't really say there's any
    likely way to help.

    I don't know how to prepare a minimal work example. I run the above
    command with my thesis with size larger than 30 MB.


    If you think you've found a bug my advice would be to report a bug at https://bugs.ghostscript.com remember to attach the file that exhibits
    the error and the command line.

    Ghostscript 9.51 was superseded one week later by Ghostscript 9.52,
    although the differences were minor I'd suggest you should be using that rather than 9.51.

    I also run the same command with 9.52. The same error message.


    Regards,

    Ken Sharp

    Thanks for the help.

    Best,
    Jinsong

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jinsong Zhao@21:1/5 to ken on Fri Jun 5 20:46:08 2020
    On 2020/6/5 19:04, ken wrote:
    In article <rbd7eh$6d9$1@adenine.netfront.net>, jszhao@yeah.net says...

    Any help?

    Wihtout seeing the PostScript file ? No I can't really say there's any
    likely way to help.


    well, I have located the problem. It triggered by a EPS file. After run
    eps2eps on the EPS, now ghostscript 9.51 does not give any error message.

    I just wonder if it's a bug of ghostscript? After all, 9.50 could live
    with the file, and 9.51 could not.

    If you think you've found a bug my advice would be to report a bug at https://bugs.ghostscript.com remember to attach the file that exhibits
    the error and the command line.

    Ghostscript 9.51 was superseded one week later by Ghostscript 9.52,
    although the differences were minor I'd suggest you should be using that rather than 9.51.

    Regards,

    Ken Sharp


    Best,
    Jinsong

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From ken@21:1/5 to All on Fri Jun 5 15:28:39 2020
    In article <rbdeqr$m4s$1@adenine.netfront.net>, jszhao@yeah.net says...

    On 2020/6/5 19:04, ken wrote:
    In article <rbd7eh$6d9$1@adenine.netfront.net>, jszhao@yeah.net says...

    Any help?

    Wihtout seeing the PostScript file ? No I can't really say there's any likely way to help.


    well, I have located the problem. It triggered by a EPS file. After run eps2eps on the EPS, now ghostscript 9.51 does not give any error message.

    I just wonder if it's a bug of ghostscript? After all, 9.50 could live
    with the file, and 9.51 could not.

    Again, without seeing the file, there's no possible way to tell. It
    could equally well be that there was something wrong which was
    previously ignored, and now is not.


    Ken

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Luuk@21:1/5 to ken on Fri Jun 5 18:41:21 2020
    On 5-6-2020 16:28, ken wrote:
    In article <rbdeqr$m4s$1@adenine.netfront.net>, jszhao@yeah.net says...

    On 2020/6/5 19:04, ken wrote:
    In article <rbd7eh$6d9$1@adenine.netfront.net>, jszhao@yeah.net says...

    Any help?

    Wihtout seeing the PostScript file ? No I can't really say there's any
    likely way to help.


    well, I have located the problem. It triggered by a EPS file. After run
    eps2eps on the EPS, now ghostscript 9.51 does not give any error message.

    I just wonder if it's a bug of ghostscript? After all, 9.50 could live
    with the file, and 9.51 could not.

    Again, without seeing the file, there's no possible way to tell. It
    could equally well be that there was something wrong which was
    previously ignored, and now is not.


    Ken


    Comparing the eps file before, and after the eps2eps should (or could?) give a clue.

    --
    Luuk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From ken@21:1/5 to All on Fri Jun 5 18:31:20 2020
    In article <5eda75b1$0$13641$e4fe514c@newszilla.xs4all.nl>,
    luuk@invalid.lan says...

    well, I have located the problem. It triggered by a EPS file. After
    run
    eps2eps on the EPS, now ghostscript 9.51 does not give any error message. >>
    I just wonder if it's a bug of ghostscript? After all, 9.50 could live
    with the file, and 9.51 could not.

    Again, without seeing the file, there's no possible way to tell. It
    could equally well be that there was something wrong which was
    previously ignored, and now is not.


    Ken


    Comparing the eps file before, and after the eps2eps should (or could?) give a clue.

    After its been through eps2write (or even epswrite if the version is old enough) ?

    Nope.

    The output EPS will be utterly different from the input EPS.


    Ken

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jinsong Zhao@21:1/5 to ken on Sat Jun 6 09:06:26 2020
    On 2020/6/5 22:28, ken wrote:
    In article <rbdeqr$m4s$1@adenine.netfront.net>, jszhao@yeah.net says...

    On 2020/6/5 19:04, ken wrote:
    In article <rbd7eh$6d9$1@adenine.netfront.net>, jszhao@yeah.net says...

    Any help?

    Wihtout seeing the PostScript file ? No I can't really say there's any
    likely way to help.


    well, I have located the problem. It triggered by a EPS file. After run
    eps2eps on the EPS, now ghostscript 9.51 does not give any error message.

    I just wonder if it's a bug of ghostscript? After all, 9.50 could live
    with the file, and 9.51 could not.

    Again, without seeing the file, there's no possible way to tell. It
    could equally well be that there was something wrong which was
    previously ignored, and now is not.


    I have submit a bug report:

    https://bugs.ghostscript.com/show_bug.cgi?id=702471

    Best,
    Jinsong

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)