Control: severity -1 normal
Hi Guilhem,
Quoting Guilhem Bonnefille (2021-04-25 20:52:16)
> Package: ghostscript
> Version: 9.27~dfsg-2+deb10u4
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> Initialy, I found the bug by updating from Debian stretch to buster
> (10.9): the printer was working on stretch but no more on buster. The
> device was running on armel. I did tests on i686 and it works.
>
> After investigation, I was able to identify the « smallest » error context.
> The following command:
>
> gs -dPDFDEBUG -dPARANOIDSAFER -dNOPAUSE -dNOINTERPOLATE -dNOMEDIAATTRS
> -dShowAcroForm -sstdout=%stderr -sOutputFile=%stdout -sDEVICE=jpeg
> -sMediaType=Automatic -sOutputType=0 -r600x600 -dMediaPosition=7
> -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=841 -dcupsMediaType=-1
> -dcupsBitsPerColor=8 -dcupsColorOrder=0 -dcupsColorSpace=17 -dcupsInteger0=26
> -scupsPageSizeName=A4 -I/usr/share/cups/fonts -c '< 9.00 9.00 9.00] /Margins[0 0]>>setpagedevice' -f -_ <
> /tmp/ades.cups-pdf >/dev/null
>
> Produces error messages on armel but not on i686:
>
> 8.3 0 0 8.3 0 0 cm
> BT
> Error reading a content stream. The page may be incomplete.
>Output may be incorrect.
> Error: Form stream has unbalanced q/Q operators (too many q's)
>Output may be incorrect.
> Q
> Q
> Error: File did not complete the page properly and may be damaged.
>Output may be incorrect.
> %Resolving: [1 0]
>
> The input is obtained from hp-setup print test page (PS) converted to
> cups-pdf with cupsfilter, which certainly means that gs is not able to
> read a PDF it generates.
Thanks for the bugreport - the details provided is much appreciated!
A key piece is missing, however: Please provide a sample file which -
like you describe - succeeds to be processed by Ghostscript on i686 and
armel/stretch but fails on armel/buster.
Would also be helpful if you could check that same file can be
succesfully parsed by other PostScript parsers - e.g. Evince, xpdf, and
(if you have access to that) Adobe applications.
I am lowering severity: That field reflects the package as a whole not
the specific issue reported, and I don't consider this issue so severe
that Debian would be better off without Ghostscript if it cannot be
solved. Don't worry - it is common to mistake the scope of the severity
field :-)
Kind regards,
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
