Bug#425405: Not a bug

[Jonathan Nieder]

Hi,

Jonas Smedegaard wrote:

> I agree that this is unlikely a bug in Ghostscript.
>
> The test PDF provided by Jonathan Nieder _is_ searchable with Evince
> 3.38.2-1.
>
> If same file was not searchable with Evince available in January 2011,
> then the issue might be the encoding of the strings in the PDF, or it
> might be something else that confused that older release of Evince.
>
> But that test file was produced by LibreOffice.  I would expect that a
> file generated by cups-pdf would instead have cups-pdf as creator in the
> metadata.
>
> I therefore suspect that the test PDF file should be ignored for this
> issue, and that the originally reported issue is a different one:
[...]
> For the record: If you suspect that an issue is in Ghostscript then
> please provide the ghostscript command that causes this issue - without
> that the only possible action is to tag it as unreproducible and close
> it, which is not really helpful.

This response is puzzling.  The example that I produced was a simple
postscript file and then a ps2pdf command that invokes ghostscript to
produce this issue.  I don't understand why you're insisting
simultaneously that I should have

- used cups-pdf instead of using ghostscript directly
- used ghostscript directly instead of using a larger pipeline that
  invokes it

since I don't see how those are possible to do at the same time.

[...]
> Ghostscript primarily renders a "painting" and secondarily preserves as
> metadata high-level information like strings of text and color spaces.
>
> One way metadata is lost is if CUPS filters use Postsript as
> intermediary format.  That was the case in the past but the default
> should nowadays use PDF as intermediary format.

This analysis seems spot-on; I think you have correctly described the
issue.

[...]
> This issue is highly likely a duplicate of 847462 - thus merging.

IIUC that bug was fixed by switching to the pdftocairo renderer.
Thanks much, this makes a lot of sense to me.

Sincerely,
Jonathan

Bug#723719: ghostscript: New Upstream Version 9.10 available

[Jonathan Nieder]

Hi,

Didier 'OdyX' Raboud wrote:
> Le lundi, 4 août 2014, 15.19:46 Jonas Smedegaard a écrit :

>> Plan forward
>> 
>>
>>  1a) Release 9.06 to unstable
>>  1b) Prepare 9.14
>>  2) Release 9.10 to unstable when 9.06 is in testing
>
> I think we should rather focus on making 9.09 available in jessie as 
> that's the latest GPL version as I understand this.

Unfortunately, 9.07 is already AGPL.

[...]
> Any upload for Ghostscript >= 9.10 should not be done before ensuring 
> that all reverse dependencies can live with an AGPL Ghostscript.

I've been thinking more about this --- would it make sense to change
the -dev package name so maintainers of reverse dependencies have to
actively check that they've done whatever's needed to make license
compliance easy for users before adopting the new version?

Thanks,
Jonathan


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140827023159.gw20...@google.com

Bug#723719: ghostscript: New Upstream Version 9.10 available

[Jonathan Nieder]

Thomas Weber wrote:
> On Thu, Sep 19, 2013 at 10:13:09AM +0200, Jonas Smedegaard wrote:
>> Quoting Thomas Kempf (2013-09-19 08:45:37)

>>> Upstream released Version 9.10 with significant improvements
>>
>> Packaged has been prepared since some time - awaits newer libcms2, 
>> tracked in bug#701993.
>
> Any chance of getting a newer ghostscript now? I updated lcms2 because I
> wanted a newer ghostscript :)

Neat, thanks.

Ghostscript 9.07 and newer use the AGPL.  I assume that would be fine
for most uses but it's possible some rdeps would need to be updated to
provide a download link so it's probably worth a NEWS.Debian entry.

Regards,
Jonathan


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140410175036.gf3...@google.com

Re: RFC: Move all VCS under a proper alioth team group

[Jonathan Nieder]

Hi,

Didier 'OdyX' Raboud wrote:

> I would like to:
>
> a) create the pkg-printing alioth group (or rename pkg-cups if that's 
>possible)
> b) make its members' list up-to-date
> c) move all packages there (including a routine upload to change VCS-*
>fields of course.)
> d) update the wiki page to be more up-to-date regarding the current
>team membership, concerned packages and eventually (but at a later
>point) a short "printing stack policy", encoding the use of pyppd,
>VCS usages, etc.

Sounds good to me.

Thanks,
Jonathan


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140127160114.gc27...@google.com

Bug#582522: please document D_MAX_BLOCKS_IN_MCU deviation from upstream more clearly

[Jonathan Nieder]

Bastien ROUCARIES wrote:

> Ok see patch

Thank you.  Looks good to me.


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120723221315.GA2926@burratino

Bug#582522: libjpeg8: Please provide variant compiled with #define D_MAX_BLOCKS_IN_MCU 64

[Jonathan Nieder]

retitle 582522 please document D_MAX_BLOCKS_IN_MCU deviation from upstream more 
clearly
# documentation
severity 582522 minor
found 582522 ghostscript/9.05~dfsg-6
quit

Hi Bastien,

Bastien ROUCARIES wrote:

> Now that README.Debian has some comment about the case, time to
> close ?

All the README.Debian says is "Some valid PostScript and PDF files
will fail to parse due to some (old, presumably?) Adobe interpreters
violating the JPEG standard", which is not even true.  (It's
presumably due to the programs generating the invalid JPEGs, which
were neither postscript interpreters nor written by Adobe.  Though no
one seems to have found any examples triggering this.)  Wouldn't it
make sense to make the README reflect what was already discovered in
the history of this report?

Thanks,
Jonathan


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120723202248.GC2985@burratino

Bug#586970: ghostscript: symbol lookup error: /usr/lib/libgs.so.8: undefined symbol: TIFFCleanup

[Jonathan Nieder]

Hi Bastien,

Bastien ROUCARIES wrote:

> Mail bounce so close

Nowadays Kingsley can be reached at kings...@loaner.com.

Hope that helps,
Jonathan


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120723201655.GB2985@burratino

Bug#681843: ghostscript: ps2epsi inserts '\r' (0x0d)

[Jonathan Nieder]

tags 681843 - moreinfo + confirmed
quit

Ryo Furue wrote:

> Please use the attached file, instead.

Thanks much.  It worked this time.


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120717182952.GC14609@burratino

Bug#681843: ghostscript: ps2epsi inserts '\r' (0x0d)

[Jonathan Nieder]

tags 681843 + moreinfo
quit

Hi Ryo,

Ryo Furue wrote:

> /usr/bin/ps2epsi inserts '\r' in place of '\n' between 
> the "%%BoundingBox" and "%%HiResBoundingBox" lines
> and between "%%HiResBoundingBox" and "%%EndComments" lines.
>
> Because of this, gv (a PostScript viewer) cannot determine
> the bounding box of the output from ps2epsi .
>
> To reproduce, use the attached PS file and
>
>   /usr/bin/ps2epsi sample.ps

I get:

$ ps2epsi sample.ps; echo $?
blank page!!
0
$ cat sample.epsi 
save countdictstack mark newpath /showpage {} def /setpagedevice /pop 
load def
%%EndProlog
%%Page 1 1
save countdictstack mark newpath /showpage {} def /setpagedevice /pop 
load def
%%Page 1 1
cleartomark countdictstack exch sub { end } repeat restore
%%Trailer
cleartomark countdictstack exch sub { end } repeat restore
%%EOF

Any idea what I'm doing wrong?

Thanks,
Jonathan


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120717171100.GI3071@burratino

Bug#343901: gs-esp's lx5000 driver runs into infinite loop with mozilla's postscript files

[Jonathan Nieder]

retitle 343901 RFP: pbm2l7k (printer driver for Lexmark printers)
notforwarded 343901
tags 343901 =
reassign 343901 wnpp
affects 343901 = ghostscript cups foomatic-db
quit

Hi,

$ git show -s ghostpdl-9.05~410
commit 9c074dc8
Author: Henry Stiles 
Date:   Tue Aug 16 16:48:01 2011 -0600

Fixes 691820 by removing the device, the authors in the contrib.mak
and source code file (gdevlx50.c) have been sent email the device is
broken.

CLUSTER_UNTESTED

Users of this printer are encouraged to use the pbm2l7k driver instead:

 Package name : lexmark7000linux
 Version  : 990516
 Upstream : OpenPrinting Working Group 

 URL  : http://www.openprinting.org/driver/pbm2l7k/
 License  : GPL-2+
 Description  :
  This is the printer driver for Lexmark 7000 "GDI" printers.
   * Known to work with Lexmark 7000, 7200 and 5700 printers
   * 600x600 dpi Black & White printing
   * Preliminary 600x600 CMY colour printing for 7000, 7200

Hope that helps,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120713190431.GA29798@burratino

Bug#404017: "New driver: Glassjet"

[Jonathan Nieder]

reopen 404017
tags 404017 + upstream
forwarded 404017 http://bugs.ghostscript.com/show_bug.cgi?id=689032
quit
(resending with a real mail client now that gmail seems to be back)

I wrote:

> Did you get a bug number? Did the Ghostscript developers respond?

Found it.  And now I see that the original report had an attachment.
Doh.

Thanks and sorry for the nonsense before,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120417172930.GA22506@burratino

Bug#404017: "New driver: Glassjet"

[Jonathan Nieder]

reopen 404017tags 404017 + upstreamforwarded 
404017 http://bugs.ghostscript.com/show_bug.cgi?id=689032quit
> Did you get a bug number?  Did the Ghostscript developers respond?
Found it! And now I see that the original report had an attachment. Doh.
Thanks and sorry for the nonsense before,Jonathan   
  


--
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/col110-w161919e14c74c0324d35a5c6...@phx.gbl

Bug#404017: new driver for ghostscript

[Jonathan Nieder]

Johannes Feigl wrote:

> Well, i don't think there is a spec fort he Glassjet-Tiff file...

That's fine --- a driver is just as good of a functional spec. :)



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120402215144.GB13969@burratino

Bug#664966: Add an option to disable T3CCITT encoding

[Jonathan Nieder]

Jonas Smedegaard wrote:

> If applied upstream, do you then know the corresponding git commit and 
> issue tracker ID?

My bad.  Yep, this is already upstream:

 commit d6f83dfa81a2073c3d1f67a30aee7e8407e4685a
 Author: Ken Sharp 
 Date:   Mon Mar 19 10:06:10 2012 +

 ps2write - work-around bugs in Brother printer CCITTFaxDecode filter



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120321224658.GB10996@burratino

Bug#664966: Add an option to disable T3CCITT encoding

[Jonathan Nieder]

tags 664966 + upstream
quit

Hi Vincent,

Vincent Bernat wrote:

> cupsfilters 1.0.7 include a fix for Brother printers to workaround a
> bug in the Postscript interpreter:
>
>  - pdftops: Additional workaround for a bug in the PostsSript interpreters
>of Brother printers, calling Ghostscript with special command line
>options (LP: #93).
>
> Unfortunately, this fix relies on a patch in Ghostscript which is not
> applied in Debian. Please, apply it.
[...]
> --- a/base/gdevpdfb.c
> +++ b/base/gdevpdfb.c
> @@ -293,16 +293,18 @@
>   * that would need to be passed.
>   */
>  if (pres) {
> -/*
> - * Always use CCITTFax 2-D for character bitmaps.  It takes less
> - * space to invert the data with Decode than to set BlackIs1.
> - */
> -float d0 = image.Decode[0];
> +if (!pdev->NoT3CCITT) {
> +/*
> + * Always use CCITTFax 2-D for character bitmaps.  It takes less
> + * space to invert the data with Decode than to set BlackIs1.
> + */
> +float d0 = image.Decode[0];
[...]
> --- a/base/gdevpdfx.h
> +++ b/base/gdevpdfx.h
> @@ -704,6 +704,11 @@
>  bool IsDistiller;
>  bool PreserveSMask;
>  bool PreserveTrMode;
> +bool NoT3CCITT; /* A bug in Brother printers causes 
> CCITTFaxDecode
> + * to fail, especially with small 
> amounts of data.
> + * This parameter is present only to 
> allow
> + * ps2write output to work on those 
> pritners.
> + */

This is internal to the PDF-writing driver, so not an ABI change (phew).

Makes sense.  Please report this upstream at
http://bugs.ghostscript.com/ and let us know the bug number so we can
track it.

Thanks,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120321223741.GA10996@burratino

Bug#663902: ghostscript: FTBFS on hurd-i386: extra gs_realloc in symbols file

[Jonathan Nieder]

Jonathan Nieder wrote:
> Pino Toscano wrote:

>> [Date: Thu, 10 Sep 2009 19:59:44 +0200]
>
> Please reset your clock.

Oh, my bad.  Looks like this was just a stuck mail and this
was fixed in 8.71~dfsg-1.

Sorry for the noise,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120314220417.GD31686@burratino

Bug#663902: ghostscript: FTBFS on hurd-i386: extra gs_realloc in symbols file

[Jonathan Nieder]

Hi,

Pino Toscano wrote:

> [Date: Thu, 10 Sep 2009 19:59:44 +0200]

Please reset your clock. :)

[...]
> as shown on [1], ghostscript fails to build on GNU/Hurd, because of a symbol
> specified in the symbols file which is not compiled on GNU/Hurd.
> The reason is basically the implementation of the gs_realloc() function: in
> base/malloc_.h there is:
> [...]
> /* (At least some versions of) Linux don't have a working realloc */
> #ifdef linux
> #  define malloc__need_realloc
> void *gs_realloc(void *, size_t, size_t);
> #else
> #  define gs_realloc(ptr, old_size, new_size) realloc(ptr, new_size)
> #endif

It seems unlikely that ghostscript's assumptions about glibc on Linux
would fail while they would succeed on Hurd, so I would prefer a fix
that just gets rid of the "#ifdef linux" block.

Based on the vcs history, the gs_realloc hack is from 1998 or earlier,
so it might be from "Linux libc" days.

What do you think?

Thanks,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120314220150.GC31686@burratino

Bug#661865: poppler-data/experimental: Conflicts with gs-cjk-resource and cmap-*, which are of priority optional

[Jonathan Nieder]

Package: poppler-data
Version: 0.4.5-3
Severity: important
Justification: §2.5: "optional packages should not conflict with each other"
X-Debbugs-Cc: debian-printing@lists.debian.org

Hi,

I was surprised to find poppler-data taking over from gs-cjk-resource
and the cmap packages.  It might or might not be a good idea (does the
poppler project do a better job of maintaining CMap files than Adobe
does?) but I thought it was worth a bug report since this will require
changing or removing those other packages to reflect their becoming
obsolete.

By the way, if poppler-data is the canonical package to get CMap files
from, I don't think it makes sense for it to "Recommends:
poppler-utils" any more.  Could you lower that to a Suggests?

Thanks for your work and hope that helps,
Jonathan



--
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120302025439.GA31286@burratino

Bug#661764: dangling symlink /usr/share/ghostscript/9.05/Resource/CIDFSubst/DroidSansFallback.ttf

[Jonathan Nieder]

block 661764 by 661863
quit

Jonas Smedegaard wrote:
> On 12-03-01 at 01:44pm, Jonathan Nieder wrote:

>> +++ w/gs/Resource/Init/gs_cidfm.ps
>> @@ -110,7 +110,7 @@ currentdict end def
[...]
>> -  currentsystemparams /GenericResourceDir get (CIDFSubst/) concatstrings
>> +  (/usr/share/fonts/truetype/droid/)
[...]
> Hmm, I will try that - when I locate a CJK PostScript file to test 
> against.

Based on a quick test, it doesn't seem to make anything worse, but the
current state is already broken.  See <http://bugs.debian/661863>.



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120302020646.GE5248@burratino

Bug#661863: ghostscript: CIDFont fallback to DroidSansFallback doesn't happen as advertised

[Jonathan Nieder]

Package: ghostscript
Version: 9.05~dfsg-2

Jonas Smedegaard wrote[1]:

> Hmm, I will try that - when I locate a CJK PostScript file to test 
> against.

Looks like the feature just doesn't work.

When I try to view example 38 here: http://www.tcpdf.org/examples.php
It renders without obvious trouble, whether or not fonts-droid is
installed.

So I purged ttf-sazanami-mincho.  The result:

| $ ghostscript -dSAFER ~/web/example_038.pdf
[...]
| Processing pages 1 through 1.
| Page 1
| Can't find CID font "ArialUnicodeMS".
| Attempting to substitute CID font /Adobe-Japan1 for /ArialUnicodeMS, see 
doc/Use.htm#CIDFontSubstitution.
| Warning: can't process font stream, loading font by the name.
| Can't find the font file /usr/share/fonts/truetype/fonts-japanese-mincho.ttf
| Can't find CID font "ArialUnicodeMS".
| Attempting to substitute CID font /Adobe-Japan1 for /ArialUnicodeMS, see 
doc/Use.htm#CIDFontSubstitution.
| Error reading a content stream. The page may be incomplete.
| File did not complete the page properly and may be damaged.
| Can't find the font file /usr/share/fonts/truetype/fonts-japanese-mincho.ttf
| >>showpage, press  to continue<<

and a blank page.  Next try: purging cmap-adobe-japan1, which
incidentally refreshes the fontconfig cache.  This time I get:

| Processing pages 1 through 1.
| Page 1
| Error reading a content stream. The page may be incomplete.
| File did not complete the page properly and may be damaged.
| >>showpage, press  to continue<<

and a blank page.  I was expecting it to fall back to characters from
DroidSansFallback.

Ideas?
Jonathan

[1] http://bugs.debian.org/661764

| $ dpkg-query -W ghostscript ghostscript-x libgs9 libgs9-common gs-cjk-resource
| ghostscript   9.05~dfsg-2
| ghostscript-x 9.05~dfsg-2
| gs-cjk-resource   1.20100103-3
| libgs99.05~dfsg-2
| libgs9-common 9.05~dfsg-2



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120302015507.GD5248@burratino

Bug#613665: ghostscript: circular dependency with gs-cjk-resource, libgs9

[Jonathan Nieder]

reassign 613665 gs-cjk-resource 1.20100103-2
affects 613665 + ghostscript
quit

Hi Kenshi Muto-san et al,

Bill Allombert wrote:

> There is a circular dependency between ghostscript, gs-cjk-resource and 
> libgs9:
>
> ghostscript :Depends: libgs9 (= 9.01~dfsg-1)
> gs-cjk-resource   :Depends: ghostscript (>= 8.70~dfsg-2.1)
> libgs9:Depends: gs-cjk-resource

In addition, the reason for the versioned dependency by
gs-cjk-resource on ghostscript doesn't seem to be documented anywhere.

What is that dependency meant to accomplish?  I'm particularly worried
since an old version of libgs can still be in use via libraries
linking to it even after ghostscript has been upgraded.  Would a
Breaks: on some appropriate versions of libgs or libgs-common work
instead?

Thanks for keeping the cmap files nicely packaged.

Sincerely,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120302013541.GA6328@burratino

Bug#661764: dangling symlink /usr/share/ghostscript/9.05/Resource/CIDFSubst/DroidSansFallback.ttf

[Jonathan Nieder]

Hi,

Jonas Smedegaard wrote:
> On 12-03-01 at 08:54am, Ian Zimmerman wrote:

>> In general, I think useless dangling symlinks are a bug even if they
>> don't cause tangible harm, just as for example documentation reference
>> to a feature that no longer exists would be a bug.  They impede
>> administrators' (and developers') understanding of the package.
>
> I agree with you that it is a bug (even by Policy IIRC).

Not in policy §10.5 "symbolic links", as least.

Maybe this could be addressed by adding some documentation, e.g. in
README.Debian:

Ghostscript uses the DroidSansFallback font from the fonts-droid
package to substitute for CID-keyed fonts that are not available
(used for East Asian character sets in PDFs).  If disk space is
scarce, remove the fonts-droid package and the glyphs from
missing fonts will be rendered as bullets.

See Use.htm#CIDFontSubstitution from the ghostscript-doc package
for details.

and in the package description:

.
By default, Ghostscript uses a font from the fonts-droid package
to approximate glyphs in PDFs for which the requested CJK
TrueType font is missing.  If the fonts-droid package is not
installed, these glyphs will be rendered as bullets.

Background:

| commit 18a51701
| Author: Chris Liddell 
| Date:   Tue Dec 13 11:46:53 2011 +
|
| Bug 690779: Provide fallback for missing CIDFonts in PDF
|
| Rather than throw an error when a PDF references a CIDFont that is not
| available, we'll now fall back to using DroidSansFallback.ttf, by default.
|
| This gives a reasonable analogue of other PDF consumers' behavior.

What would happen if the symlink were removed and the following patch
applied?

 gs/Resource/Init/gs_cidfm.ps |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git i/gs/Resource/Init/gs_cidfm.ps w/gs/Resource/Init/gs_cidfm.ps
index 3f0a2076..68143909 100644
--- i/gs/Resource/Init/gs_cidfm.ps
+++ w/gs/Resource/Init/gs_cidfm.ps
@@ -110,7 +110,7 @@ currentdict end def
   (/) concatstrings
 }
 {
-  currentsystemparams /GenericResourceDir get (CIDFSubst/) concatstrings
+  (/usr/share/fonts/truetype/droid/)
 } ifelse
   } ifelse
 



--
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120301194412.GB3299@burratino

Bug#661764: dangling symlink /usr/share/ghostscript/9.05/Resource/CIDFSubst/DroidSansFallback.ttf

[Jonathan Nieder]

tags 661764 + moreinfo
quit

Hi Ian,

Ian Zimmerman wrote:

> $ file /usr/share/ghostscript/9.05/Resource/CIDFSubst/DroidSansFallback.ttf
> /usr/share/ghostscript/9.05/Resource/CIDFSubst/DroidSansFallback.ttf: broken 
> symbolic link to `../../../../fonts/truetype/droid/DroidSansFallback.ttf'
[...]
> Versions of packages libgs9-common recommends:
> pn  fonts-droid  

That's why.  I don't see an obvious bug here.  What harm is the broken
symlink causing, and what change would you suggest to avoid it?

Curious,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120301071056.GA1983@burratino

Re: cups ignores duplex setting in postscript files

[Jonathan Nieder]

# regression
severity 497671 important
merge 497671 500732
quit

Hi,

Matti Laakso wrote:

> We're being bit by the same bug. Duplex setting is respected when
> printing from Linux clients, but through samba it gets reset to default
> somewhere along the way.
>
> However, it seems that there may be two separate bugs: At least in our
> case pstops is not the culprit, since bypassing it with
>
> cups options = "document-format=application/vnd.cups-postscript"
>
> does not help. Also, jobs from Linux clients go through pstops as well.
> The problem is in foomatic-rip instead. Its log shows lines of the form
>
> Option: Duplex=DuplexNoTumble --> Correcting numerical/string option to
> Duplex=None (Command line argument)
>
> when printing from Windows clients. Using PCL drivers on Windows works,
> since then also foomatic is bypassed.

Thanks, and sorry for the slow reply.  Well, that's a start.
Cc-ing the foomatic-rip maintainers and samba maintainers; hopefully
they might have more questions to help track this down further.

Till et al: see http://bugs.debian.org/497671 for some analysis.

Hope that helps,
Jonathan


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120214051848.GA9151@burratino

Bug#657817: ghostscript: Provide ps2pdfa

[Jonathan Nieder]

tags 657817 + upstream
quit

Hi,

Liam K Morland wrote:

> Along with the other ps2pdf* scripts, it would be very helpful to have a 
> script to create PDF/A. Attached is an attempt at creating such a 
> script.

Sounds sensible.  Could you request inclusion at 
and send us the bug number so we can track it?

Thanks much,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120129045740.GB16404@burratino

Bug#653061: libgs9 exports symbols conflicting with the same symbols in libjpeg8

[Jonathan Nieder]

Bill Allombert wrote:

> The short answer is that it is not possible.

Alas.  Thanks for checking.

*checks*  Wait, is the long answer that it _is_ possible? :)  The
"mem" field seems to do exactly what I'd want.

> But you can use versionned symbols.

Do you mean that libgs should explicitly override
jpeg_get_small@LIBJPEG_8.0 et al instead of using unversioned symbols?
If so, I'd agree, but I don't think it would help with this crash.

Please feel free to skip the following background[*] unless morbidly
curious.

Thanks much,
Jonathan

[*] In ghostscript, the context object when using libjpeg is
the jpeg_compress_data struct.  The notable fields for us at the moment
are:

typedef struct jpeg_compress_data_s {
...
gs_memory_t *memory;/* heap for library allocations */
...
struct jpeg_compress_struct cinfo;
...
} jpeg_compress_data;

Ghostscript is designed to be _very_ flexible about the environment it
runs in, since one of the target environments is printer firmware and
saving money on processing power or memory in that context is
desirable.  In particular, ghostscript maintains a private heap to
avoid overhead from, for example, unnecessarily maintaining alignment
of strings.

A vtable with memory management routines can be found in the
jpeg_compress_data::memory field.  But the jpeg_compress_struct object
provided by non-ghostscript callers is not part of a larger
jpeg_compress_data, so attempts to downcast and access that field
segfault.

Luckily, libgs's custom allocator support is not part of the public
interface documented in its headers, so we are not too constrained in
solving this.

Possible fixes:

 a) stop using a custom allocator for libgs's jpeg support

 b) set custom allocators in the jpeg_compress_struct::mem field
instead of globally overriding the system-dependent memory manager

 c) use a magic value for jpeg_compress_struct::client_data to
distinguish between ghostscript and non-ghostscript callers to the
memory manager and fall back to the stock libjpeg versions for
non-ghostscript calls

Of these, (b) seems the most appealing, but maybe (a) is a better
choice.



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111229110155.GB29150@elie.Belkin

Re: libjpeg8: Please provide variant compiled with #define D_MAX_BLOCKS_IN_MCU 64

[Jonathan Nieder]

reassign 582522 ghostscript 8.64~dfsg-2
quit

Jonathan Nieder wrote:
> Bill Allombert wrote:

>> Honestly, unless you provide evidence that PS files that include invalid
>> jpeg-encoded data are still in use, I am not going to include two new 
>> packages
>> to support non-standard compliant data in Debian, and in any case, I doubt 
>> the
>> FTP master would let me. 
>
> Makes sense.  Currently ghostscript/README.Debian says:
[...]
> http://www.ghostscript.com/pipermail/gs-code-review/2002-March/002275.html
> tells a slightly different story:
[...]
> So I do not even think that there are old Adobe interpreters involved
> (despite what jpeglib.h says).  Would it be enough to say something
> like this?
[...]
>   If you come across a file triggering either of these
>   conditions, please let us know by reporting a bug against
>   the ghostscript package.

Hence reassigning to ghostscript.  I suggest updating the README.Debian
to clarify this, and perhaps contacting upstream to encourage them to
consider dropping the "#define D_MAX_BLOCKS_IN_MCU 64" hack, too.

Thanks for your help.
Jonathan


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111223233507.GA25158@elie.Belkin

Bug#653061: libgs9 exports symbols conflicting with the same symbols in libjpeg8

[Jonathan Nieder]

Hi,

Jean Brefort wrote:

> Three symbols are concerned:
> jpeg_mem_init, jpeg_mem_term and jpeg_mem_available.
>
> Building an executable using the two libraries might crash. This happens for 
> me
> with gnumeric (from git) when goffice is built with eps support and when I try
> to add a jpeg image inside a sheet.

More details would be useful, including a stacktrace or error messages
if possible.

>From gs/base/sjpegc.c:

  Ghostscript uses a non-public interface to libjpeg in order to
  override the library's default memory manager implementation.

Do you know if libjpeg provides a way to use a custom allocator
without interfering with other modules in the same process image
that might not want to use it?

Thanks,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111223214658.GC21769@elie.Belkin

Bug#608802: ghostscript: version 8.71~dfsg2-6.1 breaks preview-latex-style

[Jonathan Nieder]

reassign 608802 auctex 11.85-1
forcemerge 610714 608802
affects 608802 + ghostscript
quit

Davide G. M. Salvetti wrote:

> I think this bug started to show up with ghostscript 8.71~dfsg2-6.1 and
> has been cured by auctex 11.86-2.1 and 11.86-3, which contained an
> upstream patch designed to deal with latest ghostscript version.

That makes sense.  Marking accordingly.



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2011131742.GA10497@elie.Belkin

Bug#651736: ghostscript: segfault when using cups device for rastering w/ SAFER and Seiko PPD

[Jonathan Nieder]

Hi Ralph,

Ralph A. Smith wrote:

> ghostscript 8.71 segfaults when invoked by CUPS (via the pdftoraster filter)
> to print to a Seiko Smart Label Printer (SLP) using the PPD provided
> by Seiko (at www.siibusinessproducts.com).  The offending ghostscript command
> (with standard input from pstopdf|pdftopdf) is 
>
> /usr/bin/gs -dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH -sDEVICE=cups
>-sstdout=%stderr -sOutputFile=%stdout -I/usr/share/cups/fonts
>-r203x203 -dDEVICEWIDTHPOINTS=236 -dDEVICEHEIGHTPOINTS=68
>-dcupsBitsPerColor=1 -dcupsColorOrder=0 -dcupsColorSpace=3
>-scupsPageSizeName=AddressSmall -c -f -
>
> If the PARANOIDSAFER option is removed, the command succeeds, but it still
> fails with SAFER instead.

I can't reproduce this (I tried on an amd64 mostly-sid system with
ghostscript and libgs8 8.71~dfsg2-9 and cups and libs
1.4.4-7+squeeze1).  Any ideas?

If no other obvious ways to make progress come up, here are some
hints:

 - Please provide a PDF file and exact command line to reproduce it on
   a machine without the SLP driver installed.  (The instructions
   would have to include installing the SLP driver if that's the only
   way to reproduce it.)

 - If you look at "dmesg" output, does it say which DSO segfaulted?

 - Rebuilding ghostscript with DEB_BUILD_OPTIONS='debug nostrip' and
   getting a backtrace by running gs with "gdb --args" as described
   at [1] would also be helpful.

 - Anyone who can reproduce this can take over what I was going to
   try, which is finding the patch that fixed the problem at
   git://git.ghostscript.com/ghostpdl.git using "git bisect".

Hope that helps,
Jonathan

[1] http://wiki.debian.org/HowToGetABacktrace



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111211220158.ga28...@elie.hsd1.il.comcast.net

Bug#414002: Same error ... narrowed down (?)

[Jonathan Nieder]

Hi Andreas,

Andreas Kreienbuehl wrote:

> To be even more crazy, running ``ps2pdf f.ps'' spits out the following.
[...]
> Error: /invalidfileaccess in --run--
> Operand stack:
>(data/matrix.data)   (r)

That sounds like a different bug (because no "..").  You're probably
looking for [1], aka [2].

Hope that helps,
Jonathan

[1] http://bugs.ghostscript.com/show_bug.cgi?id=692602
[2] http://bugs.debian.org/618530



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2016044719.gc5...@elie.hsd1.il.comcast.net

Bug#414002: [gs-common] Retag FTBS

[Jonathan Nieder]

severity 414002 normal
found 414002 ghostscript/8.71~dfsg2-6
quit

Bastien ROUCARIES wrote:

>  texlive-pstricks pdf documentation of pst-geo could not build from
> source. And even viewed.
> But you could regress this bug since we have the already built
> documentation on the tar.bz2

Ah, so you mean the upstream TeXLive pstricks package is another
testcase, rather than that some Debian package such as texlive-extra
is failing to build from source.

Ok, lowering severity.  Do you know what was the intent of the checks
preventing inclusion of files from ../ introduced around 4 years ago
that Ralf Stubner mentioned?  In modern gs, they seem to be enabled
by -dSAFER, despite not having anything to do with the description in
the manpage:

-dSAFER
Disables the "deletefile" and "renamefile" operators
and the ability to open files in any mode other than
read-only.  This strongly recommended for spoolers,
conversion scripts or other sensitive environments
where a badly written or malicious PostScript program
code must be prevented from changing important files.

By contrast with bug#618530, this ".." check kicks in even for "gs -P".
That is:

mkdir subdir
man -t ls >ls.ps

echo '(ls.ps) run' | gs;# displays manpage.
echo '(ls.ps) run' | gs -dSAFER;# fails.
echo '(ls.ps) run' | gs -P -dSAFER; # displays manpage.

cd subdir
echo '(../ls.ps) run' | gs; # displays manpage.
echo '(../ls.ps) run' | gs -dSAFER; # fails.
echo '(../ls.ps) run' | gs -P -dSAFER;  # fails.



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111016092147.ga17...@elie.hsd1.il.comcast.net

Bug#618530: ghostscript: cannot open OutputFile if -dSAFER specified with piped or interactive input

[Jonathan Nieder]

unmerge 618530
# just a regression
severity 618530 important
found 618530 ghostscript/9.04~dfsg-2
tags 618530 + upstream
forwarded 618530 http://bugs.ghostscript.com/show_bug.cgi?id=692602
quit

Jonathan Nieder wrote:

> Confirmed: with version 8.71~dfsg2-6.1 running
>
>   man -t ls >ls.1
>   echo '(ls.ps) run' | ghostscript -dSAFER
>
> fails with /invalidfileaccess, while with 8.71~dfsg2-6 it succeeds

Thanks again.  Let's see what upstream says.



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111016012844.ga21...@elie.hsd1.il.comcast.net

Bug#414002: [gs-common] Retag FTBS

[Jonathan Nieder]

Hi Bastien,

Bastien ROUCARIES wrote:

> severity 414002 serious 
> reassign 414002 ghostscript 
> found 414002 8.71~dfsg2-9
> tags 414002 + confirmed
> tags 412584 + confirmed
> affects 412584 texlive-pstricks
> thanks
>
> I can confirm this bugs. Raise to grave due to FTBFS  texlive-pstricks

Sorry I jumped the gun on merging #414002 with #618530.  Let's see...

 $ wget http://mirror.ctan.org/graphics/pstricks/contrib/pst-geo.zip
 $ unzip pst-geo.zip
 $ mkdir pst-geo/testcase && cd pst-geo/testcase
 $ cat <<\EOF >test.tex
\documentclass[letterpaper,12pt]{article}
\usepackage[english]{babel}
\usepackage{pstricks}
\usepackage{pst-map2dII}
\begin{document}
\psset{xunit=0.70,yunit=0.70, path=../dataII}
\begin{pspicture*}(-9,-4)(10,9)
\WorldMapII[maillage=false,all=true,level=5,borders=false,linewidth=0.01\pslinewidth,linecolor=gray]
\end{pspicture*}
\end{document}
EOF
 $ latex test.tex
 $ dvips test.dvi
 $ gs -dSAFER test.ps

Result:

| GPL Ghostscript 9.04 (2011-08-05)
| Copyright (C) 2011 Artifex Software, Inc.  All rights reserved.
| This software comes with NO WARRANTY: see the file PUBLIC for details.
| Error: /invalidfileaccess in --run--
| Operand stack:
|(../dataII/europe-cil.dat)   (r)
| Execution stack:
|%interp_exit   .runexec2   --nostringval--   --nostringval--   
--nostringval--   2   %stopped_push   --nostringval--   --nostringval--   
--nostringval--   false   1   %stopped_push   1910   1   3   %oparray_pop   
1909   1   3   %oparray_pop   1893   1   3   %oparray_pop   1787   1   3   
%oparray_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval--   
--nostringval--   --nostringval--   2   %stopped_push   --nostringval--   1910  
 1   6   %oparray_pop   --nostringval--
| Dictionary stack:
|--dict:1157/1684(ro)(G)--   --dict:0/20(G)--   --dict:85/200(L)--   
--dict:180/300(L)--   --dict:38/200(L)--   --dict:130/200(L)--
| Current allocation mode is local
| Last OS error: 2
| Current file position is 101753
| GPL Ghostscript 9.04: Unrecoverable error, exit code 1

Arnout Boelens wrote:

> If I move everything from ../dataII to ./data (and remove the
> \psset{path=../dataII}) it works here.

But I do _not_ find that to be the case here.  So I imagine something
has changed, and that the modern incarnation of this bug has the same
cause as bug#618530 after all.

Am I understanding correctly?  What package does this prevent from
building from source?

Thanks,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111016010538.ga3...@elie.hsd1.il.comcast.net

Bug#644670: ghostscript: FTBFS: devlibs error: There is no package matching [liblcms2-dev] and noone provides it

[Jonathan Nieder]

reassign 644670 d-shlibs
quit

Hi Dave,

Dave Anglin wrote:

> Source build of ghostscript fails in sid on hppa-unknown-linux-gnu.

Thanks for reporting it.

> devlibs error: There is no package matching [liblcms2-dev] and noone provides 
> it, please report bug to d-shlibs maintainer

Hence reassigning.  I suspect this might be a variant on bug#636919.

Hope that helps,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111008020306.ga3...@elie.hsd1.il.comcast.net

Bug#641936: Canon Pixma MP210 does not work out of the box (MP220 driver works fine)

[Jonathan Nieder]

Package: foomatic-db-gutenprint
Version: 5.2.6-1
Tags: upstream
Affects: cups

Hi,

Typical amd64 squeeze system.  I have a Canon MP210 scanner/printer.
The scanning support works great out of the box, and the printing
works well, too.

However, the initial setup required some digging online to find the
right driver. In system-config-printer, choosing Add Printer didn't
bring up the right driver right away, and in fact the driver that
works for me calls itself model MULTIPASS-MP220, driver "Canon
MULTIPASS-MP220 Foomatic/gutenprint-ijs-simplified.5.2 [en]
(recommended)". Would it be possible to add an alias with some name
like "MULTIPASS-MP210" or "Pixma MP210"?

Reporting to the foomatic-db-gutenprint package since it seems that
/usr/share/foomatic/db/source/driver/gutenprint-ijs-simplified.5.2.xml
lists the driver used. Please feel free to reassign as appropriate,
and if there's any information I can provide to help, just ask.

Regards,
Jonathan

# lsusb -s001:006
Bus 001 Device 006: ID 04a9:1721 Canon, Inc. MP210 ser
$ dpkg-query -W foomatic-db ijsgutenprint
foomatic-db 20100630-1
ijsgutenprint   5.2.6-1



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110917220700.GA6358@elie

Bug#638277: libgs8 segfault : print jobs (recto/verso) stop after 2nd page

[Jonathan Nieder]

Christophe Alonso wrote:

> So I did the following:
> - cd to some.pdf;
> - pasted your script in a terminal. 
>
> Now I have a really big file (1,4GB) "out" seeming not readable and a
> other file "err" with lot of debug things.

Hm, sounds like it didn't segfault for you, either.  I will think
more.



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110818220757.gl30...@elie.gateway.2wire.net

Bug#638277: libgs8 segfault : print jobs (recto/verso) stop after 2nd page

[Jonathan Nieder]

Hi Christophe,

Christophe Alonso wrote:

> Here is the psc_1200_series.ppd.
> I hope it can help you,

I suspect this is
http://bugs.ghostscript.com/show_bug.cgi?id=690101 but I was not
able to reproduce it.  I tried the following:

cat some.pdf |
PPD=/path/to/psc_1200_series.ppd \
gs -dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH \
-sDEVICE=cups -sstdout=%stderr \
-sOutputFile=%stdout \
-I/usr/share/cups/fonts -sMediaType=Plain \
-sOutputType=0 -r600x600 -dMediaPosition=7 \
-dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=841 \
-dcupsBitsPerColor=8 -dcupsColorOrder=0 \
-dcupsColorSpace=1 -dcupsRowStep=1 \
-dcupsInteger0=26 -scupsString0=PlainNormalColor \
-scupsPageSizeName=A4 -c -f -_ >out 2>err
echo $?

with ghostscript being version 8.71~dfsg2-9.  If you can reproduce
it this way, please attach the PDF; otherwise, we will have to figure
out something else.  Thanks.



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110818193054.gh30...@elie.gateway.2wire.net

Bug#638277: libgs8 segfault : print jobs (recto/verso) stop after 2nd page

[Jonathan Nieder]

Christophe Alonso wrote:

> Attached cups error_log.

Thanks.  Quick analysis:

> D [18/Aug/2011:11:56:45 +0200] [Job 7] 
> envp[20]="PPD=/etc/cups/ppd/psc_1200_series.ppd"

It would be interesting to see /etc/cups/ppd/psc_1200_series.ppd, too.

[...]
> I [18/Aug/2011:11:56:45 +0200] [Job 7] Started filter 
> /usr/lib/cups/filter/pdftopdf (PID 5597)
> I [18/Aug/2011:11:56:45 +0200] [Job 7] Started filter 
> /usr/lib/cups/filter/pdftoraster (PID 5598)
> I [18/Aug/2011:11:56:45 +0200] [Job 7] Started filter 
> /usr/lib/cups/filter/hpcups (PID 5599)
> I [18/Aug/2011:11:56:45 +0200] [Job 7] Started backend 
> /usr/lib/cups/backend/hp (PID 5600)
[...]
> D [18/Aug/2011:11:56:45 +0200] PID 5597 (/usr/lib/cups/filter/pdftopdf) 
> exited with no errors.

The error probably happens in pdftoraster (which is good news, since
that step is not device-specific).

> D [18/Aug/2011:11:56:45 +0200] [Job 7] Ghostscript command line: /usr/bin/gs 
> -dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH -sDEVICE=cups -sstdout=%stderr 
> -sOutputFile=%stdout -I/usr/share/cups/fonts -sMediaType=Plain -sOutputType=0 
> -r600x600 -dMediaPosition=7 -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=841 
> -dcupsBitsPerColor=8 -dcupsColorOrder=0 -dcupsColorSpace=1 -dcupsRowStep=1 
> -dcupsInteger0=26 -scupsString0=PlainNormalColor -scupsPageSizeName=A4 -c -f 
> -_

A gs commandline.  We are halfway to a testcase.

[...]
> D [18/Aug/2011:11:59:17 +0200] PID 5598 (/usr/lib/cups/filter/pdftoraster) 
> stopped with status 1!

Indeed, pdfraster failed.

[...]
> E [18/Aug/2011:11:59:23 +0200] [Job 7] Job stopped due to filter errors; 
> please consult the error_log file for details.

So, now my goal is to convince cups to give us a postscript file
so the problem can be reproduced independently of cups.  My
best idea for that at the moment is modifying the PPD, but I'm
also cc-ing the cups maintainers in case they know of an easier
way.

Hope that helps,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110818154805.gb30...@elie.gateway.2wire.net

Bug#638277: libgs8 segfault : print jobs (recto/verso) stop after 2nd page

[Jonathan Nieder]

severity 638277 important
quit

Hi Christophe,

Christophe Alonso wrote:

> If I want to print pdf on both sides, I have to print first even pages then 
> odd
> ones.
> Then printer stops after 2nd page.
> Seems libgs8 segfault.

Hm, that's unfortunate.

[...]
> ipp://localhost:631/printers/psc_1200_series
> usblp0: removed
> gs[5856]: segfault at 7fff1131c668 ip 7fb167cc55e5 sp
> 7fff122b4268 error 4 in libgs.so.8.71[7fb167b5+467000]

Please set LogLevel to debug in /etc/cups/cupsd.conf, set debug to 1
in /etc/foomatic/filter.conf, run

/etc/init.d/cups reload

and try again, attaching the resulting /var/log/cups/error_log,
/tmp/foomatic-rip.log, and /tmp/foomatic-rip.ps files (compressing if
they are large).  (If you can reproduce the problem by printing to
file, that would be ideal.)

> usb 5-2: USB disconnect, address 3

This part happens later rather than during printing, right?

Thanks for reporting,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110818082741.gq31...@elie.gateway.2wire.net

Bug#588929: CUPS unable to print. CUPS runs gs and libgs8 shows segmentation fault in the /var/log/messages

[Jonathan Nieder]

Hi,

Christophe Alonso wrote:

> I have similar problem here, with squeeze version of libgs8 (8.71).
> When trying to print some pdf, it goes well for 2 pages (everytime) then
> segfault.

Please file a new bug.  If they turn out to have the same cause, we can
merge them.

Thanks,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110817215433.gf31...@elie.gateway.2wire.net

Bug#582417: libjpeg8: Please provide variant compiled with #define D_MAX_BLOCKS_IN_MCU 64

[Jonathan Nieder]

Bill Allombert wrote:

> Honestly, unless you provide evidence that PS files that include invalid
> jpeg-encoded data are still in use, I am not going to include two new packages
> to support non-standard compliant data in Debian, and in any case, I doubt the
> FTP master would let me. 

Makes sense.  Currently ghostscript/README.Debian says:

GPL Ghostscript is linked against the shared IJG JPEG library (not a
statically linked local copy).  Some valid PostScript and PDF files will
fail to parse due to some (old, presumably?) Adobe interpreters
violating the JPEG standard.  More info at [bug#582521].

[bug#582521]: 

http://www.ghostscript.com/pipermail/gs-code-review/2002-March/002275.html
tells a slightly different story:

   First, I have no doubt that at one time there were files in the
wild that exceeded the JPEG standard for the number of blocks in the
MCU. In fact, Adobe's tech note 5116 suggests that Adobe did come
across such implementations in their own interoperability testing
in 1991. This tech note also states that Adobe's implementation, at
least in some cases, will tolerate such out-of-spec JPEG streams.

   That said, the PRLM3 states quite straightforwardly that the number
of blocks in the MCU must not exceed 10. The PRLM2 contains the same
condition, but attributes it to "the JPEG-proposed standard". Thus,
I believe that any PostScript file containing a non-compliant JPEG
stream can safely be considered invalid.

   How likely are we to run across such invalid files? A note from Tom
Lane (author of libjpeg) states that he's never seen such a file, nor
has he recieved a bug report from anybody about the MCU issue:

  http://remotesensing.org/lists/libtiff_archive/msg00355.html

   Thus, I conclude that the chance of ordinary users running across a
problem with such files is nil.

So I do not even think that there are old Adobe interpreters involved
(despite what jpeglib.h says).  Would it be enough to say something
like this?

On Debian systems, ghostscript is linked against the shared
IJG JPEG library, instead of using the patched local copy
bundled with the ghostscript source.  The two versions of
the library behave identically except in two respects, both
concerning invalid JPEG streams:

- The bundled libjpeg fakes a valid component id when JPEG
  streams include an SOF or SOS marker whose component
  identifiers are not all distinct (see the description of
  C_i in B.2.2 of the JPEG spec).  The shared IJG JPEG
  library produces artifacts (e.g., stripes) when presented
  with such component ids.

  http://bugs.ghostscript.com/show_bug.cgi?id=686980

- The bundled libjpeg is configured to accept up to 64 blocks
  per MCU, instead of the limit of 10 blocks per MCU described
  in the Postscript reference manual and JPEG standard.
  According to lore and Adobe's tech note 5116, in 1991 Adobe
  came across some files in the wild exceeding the standard
  for blocks per MCU, and Adobe's implementation would
  sometimes accept such streams.

If you come across a file triggering either of these
conditions, please let us know by reporting a bug against
the ghostscript package.



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110806232954.ga4...@elie.gateway.2wire.net

Re: Recent upgrade broke my canon printer

[Jonathan Nieder]

Rustom Mody wrote:

> I just have one little question -- hope someone on printing team can answer:
> Who makes the /dev/usb/lp0 device?

udev.  What versions of udev and the kernel do you use?  Does
/etc/udev/rules.d contain any custom entries?


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110803192827.GA3223@elie.Hillsp

Re: Recent upgrade broke my canon printer

[Jonathan Nieder]

Hi,

Rustom Mody wrote:

> I have a canon printer that has been working with debian and the canon
> supplied packages for quite a while
> Recent upgrades broke the printer is now the captstatusui gives me:

Quick context for the printing team: this printer is not currently
supported out of the box by Debian, nor by packages in the non-free
repository that accompanies it.  There is a free driver available
though I'm not sure how well it works.  Packaging work is tracked at
http://bugs.debian.org/618640


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110803133759.GB5186@elie.Hillsp

Bug#632607: ps2pdf.1: please clarify that output is to the cwd by default

[Jonathan Nieder]

Package: ghostscript
Version: 9.02~dfsg-2
Severity: minor
Tags: upstream patch
Forwarded: http://bugs.ghostscript.com/show_bug.cgi?id=692322

Hi,

Today I wanted to view a manual page with a PDF viewer:

 $ man -t ls >/tmp/ls.ps
 $ ps2pdf /tmp/ls.ps
 $ run-mailcap /tmp/ls.pdf
 Error: no such file "/tmp/ls.pdf"

My mistake --- the output actually went to ./ls.pdf.  But could this
be clarified in the manpage?  Patch at the URL above.

Incidentally, the manpage in German seems to be slightly out of date.
It does not contain the paragraph about the output filename, nor the
pointer to look at the HTML documentation for information about PDF/X
and PDF/A documents.

Thanks for keeping Debian's ghostscript package in good shape, and
hope that helps.

Regards,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110704011032.GA12384@elie

Bug#343901: gs-esp's lx5000 driver runs into infinite loop with mozilla's postscript files

[Jonathan Nieder]

forwarded 343901 http://bugs.ghostscript.com/show_bug.cgi?id=691820
quit

Sebastian Schmidt wrote:

> gs-esp with -sDEVICE=lx5000 hangs when printing PostScript files
> generated by mozilla (firefox, in this case).

Based on a belief that there are no coincidences, I'm linking this to
a seemingly related upstream report.  Further discussion should
probably happen there.

Thanks again for your help.



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110704002925.GA11903@elie

Bug#626122: [sparc] ghostscript: segfault using pdfwrite device

[Jonathan Nieder]

Package: ghostscript
Version: 9.02~dfsg-2
Severity: important
Justification: ftbfs

Hi,

A couple of months ago, altree failed[1] to build from source on sparc
due to a bus error.  That's been fixed and altree given back; alas,
now altree FTBFS[2] on sparc due to a segmentation fault.

This is not serious because altree:sparc is not in testing.

The relevant gs invocation looks like so:

 gs -q -dNOPAUSE -sAutoRotatePages=None \
-dAutoFilterColorImages=false \
-dColorImageFilter=/FlateEncode \
-sDEVICE=pdfwrite \
-dPDFSETTINGS=/prepress \
-sOutputFile=fig/overview.pdftex \
- -c quit

Afterwards, fig2dev dies with a double free or corruption (it is not
so graceful about gs failures --- see Bug#614538).

I suppose a next step might be (on any platform) to grab the ps file
that is fed to gs, and (on sparc) to grab a backtrace and start
investigating.

Thanks and hope that helps,
Jonathan

[1] http://bugs.debian.org/613642
[1] 
https://buildd.debian.org/status/fetch.php?pkg=altree&arch=sparc&ver=1.0.1-4&stamp=1304761037



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110509013144.GA25951@elie

Bug#619306: ghostscript segfaults on some eps file

[Jonathan Nieder]

Jonas Smedegaard wrote:
> On 11-05-04 at 05:44am, Jonathan Nieder wrote:

>> Ok, so I was looking for an upstream repository to sift through but I 
>> don't think there is one for lcms1.
>
> Not sure I understand what you mean above: Sure there is upstream source 
> for lcms1: http://www.littlecms.com/download.html

All I meant is that there doesn't seem to be a VCS with split-out
patches for the pre-lcms2 code like there is for lcms2.

> Ghostscript recently added support for LittleCMS 2.x which I hope to 
> soon use instead of LittleCMS 1.x.

Ah, that seems like a smart thing to do.  I'll stop digging.  Thanks
for pointing it out.



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110504110835.GA9537@elie

Bug#619306: ghostscript segfaults on some eps file

[Jonathan Nieder]

Jonathan Nieder wrote:
> Håkon A. Hjortland wrote:

>> Downgrading liblcms1 from 1.18.dfsg-1.2ubuntu1 to 1.16-7ubuntu1 also
>> fixes the segfaults for both arch-SPOT.eps and transmitter.pdf.
>
> Ah, thanks for this (and for pinpointing which pointers are NULL)!
> I'll bisect.

Ok, so I was looking for an upstream repository to sift through but I
don't think there is one for lcms1.  Results for "gs -dSAFER
arch-SPOT.eps" using packages from snapshot.debian.org:

 liblcms1 1.16-7ok
 liblcms1 1.17-2ok
 liblcms1 1.17.dfsg-1   ok
 liblcms1 1.17.dfsg-1+lenny1segfault
 liblcms1 1.17.dfsg-1+lenny2segfault
 liblcms1 1.18.dfsg-1   segfault

Either ghostscript 9 is abusing lcms1 (quite possible --- ghostscript
is just starting to use littlecms and there is doubtless a learning
curve involved) or there was an undeclared ABI break.

Based on lcms-user mailing list archives around that time, the patch
from 1.17.dfsg-1+lenny1[1] is not the patch to look at and it is
better to look at what 1.18 did:

| With this patch lcms does not work at all. Please upgrade to 1.18 and 
| let's forgot all this nasty stuff.

When ghostscript renders arch-SPOT.eps, Device2PCS->CLut16params (as
filled by cmsReadICCLut) is all-zeroes with modern liblcms1 and in
particular the pointer to its Interp3D method is NULL when cmsEvalLUT
calls it.  Håkon did the brave thing and tried omitting the Interp3D
call, and it seemed to work okay.

So it's all a little puzzling.  Hints welcome.

Still, hope that helps,
Jonathan

[1] Changelog for 1.17.dfsg-1+lenny1:

  * Non-maintainer upload by the security team
  * Include upstream fixes for integer overflows, possible memory leaks
and a buffer overflow
Fixes: CVE-2009-0723 CVE-2009-0581 CVE-2009-0733

DSA: http://www.debian.org/security/2009/dsa-1745



--
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110504104453.GB1553@elie

Bug#619306: ghostscript segfaults on some eps file

[Jonathan Nieder]

Hi,

Håkon A. Hjortland wrote:

> Downgrading liblcms1 from 1.18.dfsg-1.2ubuntu1 to 1.16-7ubuntu1 also
> fixes the segfaults for both arch-SPOT.eps and transmitter.pdf.

Ah, thanks for this (and for pinpointing which pointers are NULL)!
I'll bisect.



--
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110504042206.GE8187@elie

Bug#625518: foomatic: please document PPD format

[Jonathan Nieder]

Package: foomatic-db-engine
Version: 4.0.7-1
Severity: wishlist
Tags: upstream

Hi,

I was looking to track down a bug experienced using the driver [1], from
the point of view of ghostscript.  In that PPD, I see:

| *FoomaticIDs: Samsung-ML-1020 gdi
| *FoomaticRIPCommandLine: "gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPA&&
| USE -sDEVICE=gdi%A%Z -sOutputFile=-%C -f - | perl -p -e '%E'&&
| "

So I wondered: what is the command line actually used?  In particular, I
wanted to know what would be substitued for %A and %Z.

| $ man ppd
| No manual entry for ppd
| $ man -s 5 -k foomatic
| $

What I am dreaming of is a short foomatic-ppd(5) page explaining that
the format is based on Adobe's PPD format and listing extensions.  That
way, the documentation could fill out over time, and it would be easier
for people to see where to look to learn the basics in the meantime.

The package this is filed against is a wild guess; please feel free to
reassign if I got it wrong.

What do you think?  Would that make sense?  Any idea where one can get
that information today, in order to start?

Regards,
Jonathan

[1] 
http://www.openprinting.org/ppd-o-matic.php?driver=gdi&printer=Samsung-ML-1020&show=1



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110504035546.GA8875@elie

Bug#359821: gs: ghostcript dies when printing to epson r300, but not hp lj1200

[Jonathan Nieder]

retitle 458008 xpdf writes DCTDecodeFilter input without JPEG SOI marker (gs: 
ERROR: /ioerror in --image--)
reassign 359821 xpdf
tags 359821 - moreinfo
merge 458008 359821
affects 359821 + ghostscript
quit

Jonathan Nieder wrote:
> Jonathan Nieder wrote:

>> Probably this will be lumped with the other "/ioerror in --image" bugs
>> (which are fixed, I suspect). ;-)
>
> Merging.

Oh, right!  From upstream[1]:

| I haven't investigated in detail, but Adobe Acrobat Distiller *also* gives an
| error on this file:
|
| %%[ Error: ioerror; OffendingCommand: imageDistiller; ErrorInfo:
| DCTDecodeFilter Input did not begin with a JPEG SOI marker ]%%

Reassigning and merging.  This way it should be possible to check if
the diagnosis is correct (it very well may not be, in which case
please reassign back).

Hope that helps,
Jonathan

[1] http://bugs.ghostscript.com/show_bug.cgi?id=691902



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110501035655.GA10676@elie

Bug#480423: gs-esp: some documents printed using ML-1020 driver cause printer to become unresponsive.

[Jonathan Nieder]

Hi again,

Jonathan Nieder wrote:
> Ben Hildred wrote:

>> I have a Dell 1100 printer which uses the samsung ML-1020 driver.
>> (rebranded printer) In many respects this printer works reasonably well.
>> Overall a satisfactory b&w printer. However many documents give me
>> trouble printing, paticualary documents with lots of graphic information (ie.
>> printing google maps form firefox give me corupted horizontal bars, some
>> blueprints and photos cause the printer to cease responding requiring a
>> reboot of the printer)
>
> Thanks for reporting.  Do you have an example?  (Printing to file as PS
> is a good way to make one.)

Ping?  Some other information would be useful, too:

 * does this still happen?  If not, do you remember around when it stopped?
 * do you use cups?  If so, which PPD do you use?
 * do you use the "gs" utility directly to print?  If not, why'd you
   report it to this package? :)

Even an answer of "I don't know" would be useful, to figure out whether we
should spend more time trying to track it down.

Thanks,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110501011135.GA385@elie

Bug#359821: gs: ghostcript dies when printing to epson r300, but not hp lj1200

[Jonathan Nieder]

reassign 359821 ghostscript
found 359821 gs-esp/8.15.1.dfsg.1-1
merge 437262 359821
quit

Jonathan Nieder wrote:
> Kenward Vaughan wrote:

>> I can hardly remember this now... :(  The R300 isn't even alive.  I'm
>> sorry.
>
> That's fine.  Stealing the bug so (hopefully) you won't get more mail.
>
> Probably this will be lumped with the other "/ioerror in --image" bugs
> (which are fixed, I suspect). ;-)

Merging.



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110501005311.GA32625@elie

Bug#372608: gs-esp launched by cupsys failes on cups PS test pages : Error: /rangecheck in .installpagedevice

[Jonathan Nieder]

tags 372608 =
reassign 372608 ghostscript
found 372608 gs-esp/8.15.1.dfsg.1-2
found 372608 gs-esp/8.15.2.dfsg.1-1
quit

Hi Bastien,

Bastien ROUCARIES wrote:

> tags 372608 + fixed
> thanks
>
> Fixed in gnu gpl edition

Thanks for checking.  What version did you check with?

Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110501003351.GA32407@elie

Bug#414002: ghostscript: cannot open OutputFile if -dSAFER specified with piped or interactive input

[Jonathan Nieder]

found 414002 ghostscript/9.02~dfsg-1
tags 414002 + upstream
retitle 414002 gs -dSAFER: /invalidfileaccess with "run" operator
quit

Jonathan Nieder wrote:

> Confirmed: with version 8.71~dfsg2-6.1 running
> 
>   man -t ls >ls.1
>   echo '(ls.ps) run' | ghostscript -dSAFER
>
> fails with /invalidfileaccess, while with 8.71~dfsg2-6 it succeeds (and if
> ghostscript-x is installed, renders the manpage).  This has nothing to do
> with OutputFile, piped input, or relative paths --- something[1] has changed
> to make innocuous _reads_ break with -dSAFER.

The above should say ">ls.ps", not ">ls.1", of course.  Sorry for the
nonsense.

> Michael, any hints?

Since the change is upstream, I can stop blaming Michael.

This bisects to r11494 (Dont't search for initialization files in the
current directory first; also revert rev. 11468, 2010-07-07), which
has description

 commit 35d24ae5fea94cf4f6bb2983967e0ab9b020bbd0
 Author: Alex Cherepanov 
 Date:   Wed Jul 7 17:47:09 2010 +

 Dont't search for initialization files in the current directory first
 by default because this leads to well-known security and confusion 
problems.
 Do this only on the user's request by -P switch. Also revert rev. 11468,
 which is no longer needed. Bug 691350.

Changing

 # Define whether or not searching for initialization files should always
 # look in the current directory first.  This leads to well-known security
 # and confusion problems,  but may be convenient sometimes.
 
 SEARCH_HERE_FIRST=0

to 1 and rebuilding seems to get it working again.  So it looks like
SEARCH_HERE_FIRST affects more than it's designed to; not sure where
to look next (I guess this should be forwarded to ghostscript
bugzilla).



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110421020112.GA25723@elie

Bug#619306: ghostscript segfaults on some eps file

[Jonathan Nieder]

found 619306 ghostscript/9.02~dfsg-1
quit

Hi,

Colin wrote:
> On Mon, Apr 18, 2011 at 10:37 PM, Jonas Smedegaard  wrote:

>>  A thir aproach is to download
>> and install using dpkg.
>
> Next I tried this solution and installed the following packages:
> liblcms1_1.18.dfsg-1.2+b3_amd64.deb
> libgs9-common_9.02~dfsg-1_all.deb
> libgs9_9.02~dfsg-1_amd64.deb
> ghostscript-dbg_9.02~dfsg-1_amd64.deb
> ghostscript_9.02~dfsg-1_amd64.deb
> But the problem persists:
[...]
> If this was corrected on this version this should not happen, right?

Right.  Thanks for checking.



--
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110419105840.GA19691@elie

Bug#622196: ghostscript: GPL Ghostscript 9.01: Error: Font Renderer Plugin ( FreeType ) return code = -1

[Jonathan Nieder]

Hi Pual,

Paul Menzel wrote:

> opening the document [1] with Evince the following error is printed to
> the terminal and navigating the document seems sluggish.

I think you left out the error message.

FWIW I tried with libgs9 9.02~dfsg-1 (first using "gs -dSAFER irw.ps"
directly and then using evince-gtk) and it works okay for me (no error
message, not sluggish).  To confirm that I am using the right file:

 $ sha1sum irw.ps 
 f1e6aa8b608fd2053db53debffc6b4dac785  irw.ps

What I am doing wrong?

Thanks,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110410204649.GA29264@elie

Bug#522417: ghostscript: Doesn't work with Brother printers

[Jonathan Nieder]

Hi,

Antonio Aguilar wrote:

> - Debian unstable (installed a week ago).
[...]
> - Brother HL-2030 - CUPS+Gutenprint v5.2.6 [en] driver
>
> When I try to print with my Brother Hl-2030 it doesn't work.

Even though this may well be the same bug, could you file it
separately so it can be unmerged if appropriate?  I guess the package
to file against would be cups or foomatic-db, since that is the
"front-end" whose maintainers would know what information to get and
what back-end to blame it on.

> I have
> tried with ghostscript from stable (8.71) and unstable (9.01). When
> I try the Mike Simons reproducer it outputs this:
>
> $ /usr/bin/gs -r1200 -g10200x13200 -q -dNOPROMPT \
>   -dNOPAUSE -dSAFER -sDEVICE=bit -sOutputFile=- - -c quit \
>   < /usr/share/cups/data/testprint | wc
> GPL Ghostscript 9.01: Unrecoverable error, exit code 1
>   8  56 630

If you get rid of the "| wc" then the result becomes more obvious:

| $ gs -r1200 -g10200x13200 -q -dNOPROMPT -dNOPAUSE -dSAFER -sDEVICE=bit \
|   -sOutputFile=- - -c quit < /usr/share/cups/data/testprint
| Error: /undefined in #CUPS-BANNER
| Operand stack:
| 
| Execution stack:
|%interp_exit   .runexec2   --nostringval--   --nostringval--   
--nostringval--   2   %stopped_push   --nostringval--   --nostringval--   
--nostringval--   false   1   %stopped_push   1910   1   3   %oparray_pop   
1909   1   3   %oparray_pop   1893   1   3   %oparray_pop   1787   1   3   
%oparray_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval--   
--nostringval--   --nostringval--   2   %stopped_push   --nostringval--
[...]

In other words, the testprint file is not a postscript file.
Debugging would require the full relevant pipeline; see

 http://fedoraproject.org/wiki/Printing/Debugging#Finding_where_the_problem_lies

Looking at /usr/share/foomatic/db/source/printer/Brother-HL-2030.xml,
I see:

  B
  hl1250

> Finally I get working the printer using the foomatic drivers:
> Brother HL - 2030 Foomatic/hl1250

Ah, ok.  I suppose the failures happen with

  
gutenprint
  

My foomatic-db-fu is not so great, so the closest I could find is
/usr/share/foomatic/db/source/driver/gutenprint-ijs.5.2.xml which says

 
  
  gs -q -dPARANOIDSAFER -dNOPAUSE -dBATCH -sDEVICE=ijs 
-sIjsServer=ijsgutenprint.5.2 -dIjsUseOutputFD%A 
-sIjsParams="STP_VERSION=5.2.6,%B"%Z -sOutputFile=- -
 

i.e., device=ijs, not device=bit.

Changing "debug: 0" to "debug: 1" in /etc/foomatic/filter.conf and
looking at /tmp/foomatic-rip.log might be helpful.

> The CUPS  error's logs contains:
>
> E [09/Apr/2011:11:14:29 +0200] [Job 9] File
> '/System/Library/ColorSync/Profiles/sRGB Profile.icc' not found

This sounds interesting and worth reporting (or finding a similar
bug), too.  I don't know if it's related, either.

Thanks, and hope that helps.
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110409211740.GA4496@elie

Re: Problems with libgs9

[Jonathan Nieder]

Hi,

Daniel Stender wrote:

> I am not so deep into this, is it a local problem or would be a bug
> report appropriate:
>
> trying to print anything always leads to:
> [ 8561.256399] usblp1: nonzero read bulk status received: -71
> [ 8561.606400] gs[4592]: segfault at 88 ip 7f3efe12c806 sp 
> 7fff43433690 error 4 in
> libgs.so.9.01[7f3efdf23000+4fa000]
> or similiar (and nothing happens).
>
> My setup: very up-to-date Linux Mint Debian/Debian Testing, Kernel
> 2.6.32-5, Cups 1.4.6-3, libgs9 9.01~dfsg-2. Printer is Canon MF 4140
> with vendor's Cups driver (cndrvcups-common, cndrvcups-ufr2-uk
> 2.20-2, proper 64bit RPMs converted with Alien).
>
> A couple of days ago it printed fine so I would guess everything is
> installed properly.

Could you install the ghostscript, ghostscript-dbg, libgs9, etc
packages from http://incoming.debian.org/ and try to get a stack
trace?  That would be very interesting.

My hunches are:

 1) This is a regression and a segfault, so it's probably a bug
(of insufficient validation of input from drivers, if nothing
else);

 2) Canon's ufr2 driver would be very interesting for inclusion in
the non-free repository that accompanies Debian, to help others
who want this driver.  Naturally that would make working on bugs
like this much easier.  AFAICT the license allows distribution.
Do you know anyone interested in working on that?

(For reference, the driver is at
http://support-asia.canon-asia.com/contents/ASIA/EN/0100270807.html
for example.)

 3) The UFR II (“ultra-fast rendering”) protocol is a winprinter
protocol used mostly for multifunction printers in the LBP and MF
series (imageRunner, etc).  Many printers supporting it also
accept PCL or postscript.

 4) No one I know of has acquired specifications or even started to
reverse-engineer it, to develop a free driver.  If you want to
work on this (please?) a good place to start might be
http://ww1.pragana.net/gdiprinters.html .

> Any pointers appreciated & greetings,

I'd suggest filing a bug once you get a backtrace and keeping us
posted about getting this printer to work "out of the box".

Thanks and hope that helps,
Jonathan


--
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110409222835.GA5556@elie

Bug#619934: /usr/bin/pdfopt: Let Adobe do its own advertizement rather than pdfopt

[Jonathan Nieder]

# upstream documentation
tags 619934 + upstream
severity 619934 minor
quit

Stefan Monnier wrote:

>adds "hint" pointers, allowing Adobe's Acrobat(TM) products to  display
>individual  pages  of  the  file  more  quickly when accessing the file
>through a network.
>[...]
>
> I see no need for such advertizement of products whose companies don't
> reciprocate.  I.e. just say "...allowing PDF viewers to display...".

What you say makes some sense, assuming it is technically accurate.
Because I am lazy: do evince, xpdf, and other poppler-based viewers
implement that feature, too?



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110328184917.GA13433@elie

Bug#616054: ghostscript: segfault on particular file not reproducible in git master

[Jonathan Nieder]

merge 619306 616054
quit

Hi Yves,

Yves-Alexis Perez wrote:

> I have some eps files (not easily sharable though) which make segfault
> gs everytime. I've tried to rebuild ghostscript from upstream sources
> to make a usable backtrace, but it appears that it's not reproducible
> using git master nor 9.00 tag.

*nod*

Good news: Alexandre Duret-Lutz has provided a reproducible (with Debian
ghostscript, no success reproducing with the upstream source yet)
testcase, so the work of debugging can be shared. :)

For debugging, I had to add "-g" in front of -O2 in the CFLAGS line in
lcms's debian/rules.

Thanks again.
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110325083813.GA10941@elie

Bug#619306: ghostscript segfaults on some eps file

[Jonathan Nieder]

tags 619306 + confirmed
quit

Hi,

Alexandre Duret-Lutz wrote:

> Running gs on the attached file ends with a segfault.
> 
> % gs -dSAFER arch-SPOT.eps

I can't reproduce this with upstream gs (I'm probably using the wrong
build-time parameters) but I can easily reproduce it with the ghostscript
Debian package.  Backtrace:

 Program received signal SIGSEGV, Segmentation fault.
 0x in ?? ()
 (gdb) bt
 #0  0x in ?? ()
 #1  0x77fc4206 in cmsEvalLUT (Lut=0x887920, In=, 
Out=0x7fffc970)
 at cmslut.c:512
 #2  0x77fcb741 in NormalXFORM (p=0x887770, in=, 
out=, Size=1)
 at cmsxform.c:210
 #3  0x77fbab71 in _cmsComputePrelinearizationTablesFromXFORM 
(h=0x7fffcb10, nTransforms=1, 
 Grid=0x8895c0) at cmsgmt.c:1121
 #4  0x77fce217 in _cmsPrecalculateDeviceLink (h=0x887770, 
dwFlags=)
 at cmssamp.c:271
 #5  0x77fcc8bd in cmsCreateProofingTransform (InputProfile=, InputFormat=196618, 
 OutputProfile=0x580660, OutputFormat=262170, ProofingProfile=, nIntent=1, 
 ProofingIntent=3, dwFlags=9216) at cmsxform.c:1537
 #6  0x77fccfbb in cmsCreateTransform (Input=, 
InputFormat=, 
 Output=, OutputFormat=, 
Intent=, 
 dwFlags=) at cmsxform.c:1618
 #7  0x775eb3d7 in gsicc_get_link_profile (pis=, 
dev=, 
 gs_input_profile=0x885bf0, gs_output_profile=0x5b1c10, 
rendering_params=0x7fffccf0, memory=0x4028c8, 
 include_softproof=0) at ./base/gsicc_cache.c:592
 #8  0x775e82f7 in gx_remap_ICC (pcc=0x6d1b00, pcs=0x445ba8, 
pdc=0x770db0, pis=0x428d58, dev=0x4903b8, 
 select=gs_color_select_texture) at ./base/gsicc.c:347
 #9  0x77529b8a in gx_remap_CIEA (pc=0x6d1b00, pcs=0x445af8, 
pdc=0x770db0, pis=0x428d58, dev=0x4903b8, 
 select=gs_color_select_texture) at ./base/gsciemap.c:665
 #10 0x777862bc in gx_remap_color (pgs=0x428d58) at ./base/gxcmap.c:553
 #11 0x77778cb8 in gs_text_begin (pgs=0x428d58, text=0x7fffce60, 
mem=0x4028c8, ppte=0x7fffcf48)
 at ./base/gstext.c:262
 #12 0x77779015 in gs_xyshow_begin (pgs=0x428d58, str=, size=, 
 x_widths=0x882b08, y_widths=0x0, widths_size=6, mem=0x4028c8, 
ppte=0x7fffcf48) at ./base/gstext.c:413
 #13 0x774f1777 in moveshow (i_ctx_p=0x444d50, have_x=1, have_y=0) at 
./psi/zcharx.c:113
 #14 0x775592eb in interp (pi_ctx_p=0x402388, pref=, perror_object=0x7fffde20)
 at ./psi/interp.c:1263

In other words, the Device2PCS->CLut16params.Interp3D callback passed
to cmsEvalLUT is null.  In fact, the entire CLut16params struct
consists of zeroes.  The relevant Device2PCS structure has few nonzero
fields:

.wFlags = 584,
.InputChan = 3,
.OutputChan = 3,
.OutputEntries = 2,
.L2 = {0x72ea80, 0x72efc0, 0x729e70, 0, ...},
.Out16params = {
.nSamples = 2,
.nInputs = 1,
.nOutputs = 1,
.Domain = 1,
},
.Mat4 = {
.v = {
[0] = {.n = {14870, 11683, 5040},},
[1] = {.n = {7908, 9, 2630},},
[2] = {.n = {467, 2684, 23883},},
}
},
.L4 = {0x78ebc0, 0x78efd0, 0x78f3e0, 0, ...},
.L4params = {
.nSamples = 512,
.nInputs = 1,
.nOutputs = 1,
.Domain = 511,
},
.L4Entries = 512

That structure is filled by cmsReadICCLut, which calls
ReadLUT_A2B(Icc, NewLUT, offset, sig) to fill it.  What this all means
is beyond my expertise.  Hints?

$ dpkg-query -W liblcms1
liblcms11.18.dfsg-1.2



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110325081347.GA29625@elie

Bug#619476: libgs9: gs catch segfault on printing specific pdf, after page 6

[Jonathan Nieder]

Hi,

Aleksandr Lavrushchenko wrote:

> When i'm trying to print this file (from evince):
> http://www-scicos.inria.fr/ScicosCBlockTutorial.pdf
> gs fail with segfault, after page 6. I mean, i can print pages from 1st to 6, 
> but
> not 7-25.

Page 7 is where the screenshots start (well, the first screenshot is
on page 8).

I'm afraid my cups fu is not strong enough to reproduce this.  Can you
get gs to segfault from the command line?  Maybe adding "LogLevel
debug" to /etc/cups/cupsd.conf and looking at /var/log/cups/error_log
would help with this.

> [444352.228046] usb 4-6: new full speed USB device using ohci_hcd and address 
> 11
> [444352.443289] usb 4-6: New USB device found, idVendor=04e8, idProduct=325b
> [444352.443299] usb 4-6: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [444352.443305] usb 4-6: Product: Xerox Phaser 3117
> [444352.443310] usb 4-6: Manufacturer: Xerox Corporation
> [444352.443315] usb 4-6: SerialNumber: L93139284...
> [444352.443562] usb 4-6: configuration #1 chosen from 1 choice
> [444352.452509] usblp0: USB Bidirectional printer dev 11 if 0 alt 0 proto 2 
> vid
> 0x04E8 pid 0x325B
> [444390.318355] gs[19424]: segfault at 10 ip b7076a3d sp bf92b820 error 4 in
> libgs.so.9.01[b6f84000+45e000]

Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110325064015.GB12886@elie

Bug#618530: ghostscript: cannot open OutputFile if -dSAFER specified with piped or interactive input

[Jonathan Nieder]

fixed 618530 ghostscript/8.71~dfsg2-6
found 618530 ghostscript/8.71~dfsg2-6.1
found 618530 ghostscript/9.01~dfsg-2
tags 618530 + confirmed
# regression
severity 618530 important
retitle 618530 gs -dSAFER: /invalidfileaccess with "run" operator
forcemerge 414002 618530
quit

Hi again,

Ralph Smith wrote:

> Surprisingly, the invalid file access does not occur in any of the versions
> you suggested, but returns when I upgrade to the current version
> (8.71~dfsg2-9).  For each case, I installed ghostscript, libgs8 and
> gs-common debs for the test.

Confirmed: with version 8.71~dfsg2-6.1 running

man -t ls >ls.1
echo '(ls.ps) run' | ghostscript -dSAFER

fails with /invalidfileaccess, while with 8.71~dfsg2-6 it succeeds (and if
ghostscript-x is installed, renders the manpage).  This has nothing to do
with OutputFile, piped input, or relative paths --- something[1] has changed
to make innocuous _reads_ break with -dSAFER.

Michael, any hints?

Jonathan

[1] via debian/patches/1010_CVE-2010-2055.patch



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110320103051.GA15794@elie

Bug#618533: Coordinating work on supporting CAPT printers

[Jonathan Nieder]

clone 618533 -1
reassign -1 cups 1.4.6-2
retitle -1 CAPT (first-generation Canon winprinters --- e.g. LBP-1120) support
tags -1 + upstream
quit

Rustom Mody wrote:

> My printer is Canon LBP-1210
> Cant see it here -- closest I can see is
> http://www.openprinting.org/printer/Canon/Canon-LBP-1120

Hmm, while at it let's track "out of the box" support for that as a
separate bug.

CUPS maintainers, please feel free to reassign to some other package
as appropriate.

Thanks.
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110317065939.GA24260@elie

Bug#618533: CAPT printers (Re: gs-esp has disappeared)

[Jonathan Nieder]

Rustom Mody wrote:

> My printer is Canon LBP-1210
> Cant see it here -- closest I can see is
> http://www.openprinting.org/printer/Canon/Canon-LBP-1120

Thanks.

To summarize, this is a GDI winprinter with undocumented protocol
(Canon Advanced Printing Technology rather than CAPT2 or CAPT3).  It
would be very interesting to hear whether Nicolas Boichat's capt
driver[1] works, and ideally to package it for Debian.  If you have
any questions, I'd be glad to help with this. :)

Canon's driver[2] does not seem to come with complete source.  It has
many components.  The license allows

 * various boring things (storage, installation, execution,
   public demos)
 * modification, but only for one's own use
 * reverse engineering, at least for the sake of debugging
   modifications of the above sort
 * redistribution under the same terms

It is clearly not free software but this looks like a good candidate
for distribution in the non-free archive that accompanies Debian.  (I
_think_ distribution along with a patch might even be allowed, but
presumably it wouldn't come to that anyway).  It is not obvious to me
whether distributing only part of the driver (say, libs/captfilter
without libcncaptnpm) is allowed.

The promisingly named pstocapt ("postscript to capt") program just
runs

/usr/bin/gs -r -dNOPROMPT -dSAFER -sDEVICE=pgmraw \
-sOutputFile=-

to get the image in greyscale and then passes that to the binary-only
libs/captfilter --- presumably it would be possible to learn something
by feeding grayscale images into that program.

I wonder if there is a project out there dedicated to collecting
information from reverse-engineering the CAPT protocol.

[1] http://www.boichat.ch/nicolas/capt/
[2] http://software.canon-europe.com/software/0040567.asp



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110317064850.GA23484@elie

Re: gs-esp has disappeared

[Jonathan Nieder]

reassign 618533 ghostscript 8.71~dfsg2-9
retitle 618533 ghostscript: please add Provides: gs-esp
severity 618533 wishlist
quit

Rustom Mody wrote:

> Ok works.

Thanks.  Jonas, do you think it would make sense to add "Provides:
gs-esp" to the ghostscript package to support obsolete and out-of-tree
drivers like this one?

Rustom, I would still be curious to hear whether your printer is
listed at  and what driver it
recommends.

> Dropped Kenshi Muto cc since he probably (assuming  he is in Japan)
> has bigger problems right now than bugs reported by pesky debian users

Quite possible. :/

Regards,
Jonathan


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110317053213.GA23325@elie

Bug#618533: gs-esp has disappeared

[Jonathan Nieder]

Rustom Mody wrote:

> Depends: libatk1.0-0 (>= 1.7.2), libc6 (>= 2.3.2.ds1-21), libglade2-0
[...]
> cupsys | cups, gs-esp, libcups2 | libcupsys2 (>= 1.1.23)

Ah, good --- it's an unversioned dependency, so a Provides could work.
Does the driver work ok after running the following?

-- 8< -- cut here ---
apt-get install equivs
cat >fake-gs-esp.control <<\EOF
Package: fake-gs-esp
Provides: gs-esp
EOF
equivs-build fake-gs-esp.control
dpkg -i fake-gs-esp_1.0_all.deb
-- >8 --

> What would it take to get cndrvcups-captcndrvcups-common into the
> debian repos?
> [I would like to try my hand at some debian packaging if its not
> entirely outside reach of my pea-sized-brain :-) ]

Mm, not sure.  Is it freely distributable?  Cc-ing Kenshi Muto, who
might have some advice.

Thanks again.
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110316044822.GA31353@elie

Bug#618533: gs-esp has disappeared

[Jonathan Nieder]

Hi,

Rustom Mody wrote:

> In a normal upgrade aptitude removed the canon printer driver cndrvcups-common
>
> I find it has a dependency on gs-esp

What printer do you use?  Is it listed at [1]?

cndrvcups-common from [2] does not seem to request gs-esp by name.
What does "apt-cache show cndrvcups-common" say for you?  (I'm trying
to figure out whether we need to document how to pretend to have
gs-esp using "equivs" or whether a simple Provides would work.)

Thanks for reporting,
Jonathan

[1] http://www.openprinting.org/printers
[2] 
http://kmuto.jp/debian/mtu/pool/main/c/cndrvcups-common/cndrvcups-common_1.30-1.dsc



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110316030847.GA25029@elie

Bug#618530: ghostscript: cannot open OutputFile if -dSAFER specified with piped or interactive input

[Jonathan Nieder]

Hi Ralph,

Ralph A. Smith wrote:

> user@host:path$ gs -q -dSAFER -dSAFINTERPOLATE -dTextAlphaBits=4 
> -dGraphicsAlphaBits=4 -sDEVICE=ppmraw -r144 -sOutputFile=foo.ppm
> GS>(foo.ps) run
> Error: /invalidfileaccess in --run--
> Operand stack:
>(foo.ps)   (r)
> ...

Thanks for reporting.  Could you try some versions among 8.71~dfsg2-6,
8.71~dfsg2-4, 8.71~dfsg2-3, 8.70~dfsg-2.1, and 8.64~dfsg-13 from
snapshot.debian.org and let us know which ones work?

Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110316013633.GA9882@elie

Bug#616054: ghostscript: segfault on particular file not reproducible in git master

[Jonathan Nieder]

Hi Yves-Alexis,

Yves-Alexis Perez wrote:

> I tried:
>
> DEB_BUILD_OPTIONS='noopt,nostrip' debuild -us -uc

This should be

DEB_BUILD_OPTIONS='noopt nostrip' debuild -us -c

> An example gcc command line is:
>
> gcc  -DHAVE_MKSTEMP -DHAVE_HYPOT -DHAVE_FILE64 -DHAVE_MKSTEMP64
> -DHAVE_FONTCONFIG -DHAVE_LIBIDN -DHAVE_SETLOCALE -fPIC  -O2 -Wall
> -Wstrict-prototypes -Wundef -Wmissing-declarations -Wmissing-prototypes
> -Wwrite-strings -Wno-strict-aliasing -Wdeclaration-after-statement
> -fno-builtin -fno-common -DHAVE_STDINT_H -DGX_COLOR_INDEX_TYPE="unsigned
> long int" -g -O2 -g -O2 -fPIC -DUSE_LIBPAPER -DGS_DEVS_SHARED
> -DGS_DEVS_SHARED_DIR=\"/usr/lib/ghostscript/9.01\" -I./psi -I./obj
> -I./obj -I./base  -o ./obj/zcharout.o -c ./psi/zcharout.c
>
> (so no -O0)

That's okay, and even preferred (disabling optimization can mask
some bugs).

> so there's not much I can do.

Hope that helps,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110302215621.GA17049@elie

Bug#483268: ghostscript does not report the correct bounding box

[Jonathan Nieder]

tags 483268 + moreinfo
quit

Hi,

Two years ago, Jeff Kenvin wrote:

> gs -sDEVICE=bbox -dNOPAUSE -dBATCH fname.ps
>
> Returns a bounding box that is too small,
>
> I have tried this on the K7 kernel and the amd64 kernel.
> Both have the same error.
>
> The cygwin version of ghostscript does not have the error

Mark T. B. Carroll wrote:

> I can't reproduce it now either, I'm afraid -- I have no memory at all
> of what it might have been! Ah well.

Thanks, Mark.  Jeff, do you remember?



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110226020436.GI6339@elie

Bug#613642: bus error in ps2pdf

[Jonathan Nieder]

forwarded 613642 http://bugs.ghostscript.com/show_bug.cgi?id=691989
quit

Julien Cristau wrote:
> On Wed, Feb 16, 2011 at 13:56:52 +0100, Julien Cristau wrote:

>> gx_semaphore_alloc() allocates a 8-byte-aligned gx_semaphore_t, which
>> means that sema->native is *not* 8-byte-aligned (its offset is 4),
>> whereas alignof(pt_semaphore_t) == 8.  The easiest fix is probably to
>> make sure gp_semaphore has maximal alignment.
>
> Quick test with the following patch seems to work (using Stéphane's test
> case).

Thanks, both.  I've filed the bug upstream.

Jonas et al, would you like a git branch with this patch applied?



--
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110221000948.GC14248@elie

Re: Getting started with CDBS

[Jonathan Nieder]

Jonas Smedegaard wrote:
> On Thu, Feb 17, 2011 at 09:33:04PM -0600, Jonathan Nieder wrote:

>> My first two CDBS questions:
[... snip lots of helpful information ...]

I suppose "make" ought to learn a
--files-affecting-variable/--files-affecting-target option. :)

Thanks for the hints.


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110220032954.GB6877@elie

Getting started with CDBS (Re: libgs9: please Recommends: (not Depends:) gs-cjk-resource)

[Jonathan Nieder]

Jonas Smedegaard wrote:

> I will be happy to help teach about CDBS issues if anyone is
> interested.  It is not like "I have no time to deal with mere
> mortals" but more that I really love the way CDBS uses make and
> dislike how short-form dh reinvents make with its core "redirect any
> build target to debhelper" trick.  So feel free to ask questions
> about CDBS, and don't expect to convince me that short-form dh is
> better for _me_. :-)

Thank you for this explanation.  Sensible. [*]

My first two CDBS questions: 

 - how can I list the makefiles involved in building a given
   target (e.g., debian/control)?  How does one find the corresponding
   documentation for those files?

 - how does one go about figuring out how to tweak some particular
   behavior?  For example, suppose I want to allow the "clean" target
   to run as non-root, or to set some particular CFLAGS in the "build"
   target.

Jonathan

[*] When using short-form dh, I tend to write:

build clean install binary-arch binary-indep binary:
+dh $@ --parallel $(opt_no_act)
.PHONY: build clean install binary-arch binary-indep binary

opt_no_act =
ifneq (,$(findstring n,$(MAKEFLAGS)))
opt_no_act = --no-act
endif

I dislike the "default pattern rule" style, too.  And I want
"debian/rules -n " to work.  Even with this, dh does not feel
like native "make" because dh lists targets it has built in
debhelper.log and skips them unless one manually deletes that log.

So your explanation sounds about right.


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110218033252.GB7874@elie

Re: libgs9: please Recommends: (not Depends:) gs-cjk-resource

[Jonathan Nieder]

Hi Jonas,

Jonas Smedegaard wrote:

> Good.  I will take care of that, then, and of these concrete issues
> of package relations.
>
> Is it ok that I repackage in one source per upstream source?
>
> Is it ok that I move the packaging to Git (in collab-maint at Alioth)?
>
> Is it ok that I repackage using CDBS?
>
> If not, then I will only touch the packaging as least possible, as I
> cannot work comfortable with the current style of it (no offense!).

Of course I have zero say in the decision, just throwing an idea
out there.

Would it be okay for the packaging of gs-cjk-resource, which is
relatively simple, to use debhelper 7 instead of CDBS?

My reasons for asking this are that

 - in my experience, dh is much easier to debug without "deep"
   knowledge about the workings.  To find out what a given sequence
   does, there is "dh foo --no-act".  Each command in that sequence
   can be invoked on the command line and has a clear manual page.

 - more people seem to be comfortable reading and writing using it

Either way, if there is any way I can help, I'd be glad to.


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110217110924.GC7740@elie

Bug#613665: ghostscript: circular dependency with gs-cjk-resource, libgs9

[Jonathan Nieder]

reassign 613665 gs-cjk-resource,libgs9
found 613665 ghostscript/9.01~dfsg-1
found 613665 gs-cjk-resource/1.20100103-2
quit

Bill Allombert wrote:

> There is a circular dependency between ghostscript, gs-cjk-resource and 
> libgs9:
>
> ghostscript :Depends: libgs9 (= 9.01~dfsg-1)
> gs-cjk-resource   :Depends: ghostscript (>= 8.70~dfsg-2.1)
> libgs9:Depends: gs-cjk-resource
>
> Complex circular dependencies are known to cause problems during upgrade, so 
> we
> should try to get rid of them.

Agreed.  I plead ignorance about these particular dependencies.

Compare Bug#613580 (advocating changing the dependency by libgs9 to a
Recommends) and Bug#613597 (requesting clarification of
gs-cjk-resource's other dependencies).

Anyway, it looks like any one of the two packages could fix this, so
reassigning.

Thanks for reporting,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110216203941.GD2110@elie

Bug#613642: bus error in ps2pdf

[Jonathan Nieder]

Hi,

Stéphane Glondu wrote:

> ocaml-melt currently FTBFS on sparc [1] because of a bus error
> provoked by ps2pdf. The bus error is easily reproduced by running
> ps2pdf on the file available at [2]. This bug is not present with the
> previous version, 8.71~dfsg2-10.

Thanks for reporting it.  If anyone has time on a sparc, what might be
useful is

apt-get build-dep ghostscript

git clone git://git.ghostscript.com/ghostscript.git
cd ghostscript/gs
# configure to minimize features (hopefully speeding up build)
./autogen.sh -C \
--disable-fontconfig \
--disable-freetype --disable-cups --disable-gtk \
--enable-dynamic --with-system-libtiff \
--without-ijs --without-jbig2dec --without-jasper
make

# [2]
lib/ps2pdfwr /path/to/doc.ps

git show -s HEAD

If that reproduces the error, it could be reported at
http://bugs.ghostscript.com and I'd be glad to hear about it.

git bisect start
git bisect bad HEAD
git bisect good ghostscript-8.71

can guide through the bisection process afterwards to find the bad
patch (which is hopefully an underalignment problem or similar).

Any takers?
Jonathan

> [1] 
> https://buildd.debian.org/fetch.cgi?pkg=ocaml-melt&arch=sparc&ver=1.3.0-2&stamp=129769&file=log&as=raw
> [2] http://glondu.net/tmp/doc.ps



--
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110216115527.GA5516@elie

Bug#613580: libgs9: please Recommends: (not Depends:) gs-cjk-resource

[Jonathan Nieder]

clone 613580 -1
retitle -1 gs-cjk-resource: please clarify font and cmap dependencies
reassign -1 gs-cjk-resource 1.20100103-2
quit

Hi,

Jonas Smedegaard wrote:
> On Tue, Feb 15, 2011 at 09:27:59PM +0100, Luca Capello wrote:

>> PS2, gs-cjk-resource needs two packages to be fully functional:
>> cmap-adobe-* and ttf-*, but only the former are listed as
>> Recommends:, with the latter being only as Suggests:, which is IMHO
>> a bug, both should be at the same level, according to the
>> Description:...
>
> I agree that there are issues with the gs-cjk-resource package. It
> is plural issues: also one of or'ing the relationships for the
> multiple CJK supportive areas instead of declaring them
> independently.  I have encouraged the maintainer to move it to
> co-maintainance at the Debian Printing Team with the intend of
> helping weed out things like that myself, but have not yet heard
> back on that proposal.  I have not yet been bothered enough to file
> bugreports yet (for some weird reason I find it more bothersome to
> file bugreports than to fully package code and maintain it for
> years).

cc-ing the gs-cjk-resource maintainers.  Please see
http://bugs.debian.org/613580 for background.

Thanks,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110215231829.GC17812@elie

Re: ghostscript: prints extra blank page

[Jonathan Nieder]

Hi Brian,

brian m. carlson wrote:

> When I print a file with ghostscript 9, I always get a blank page
> printed first.  Then my document prints normally.
[...]
> The printer I am using is an Officejet 4500.  I also see this problem
> with a Deskjet 5740.  Both of these printers use the hplip/hpijs
> functionality, although one uses the full hplip (with the hp backend)
> and the other uses just the ppds (with the usb backend); these printers
> are on two different machines.  While this is not terrible, it is
> inconvenient and quite irksome when I'm printing twenty copies of
> something.

Cc-ing the hplip maintainers for ideas.

What would be most useful for debugging: do you know any way to
detect the blank page in the output (using gs -sOutputFile) without
using an actual printer?  With that information, it should be
possible to bisect using the upstream ghostscript repo[1].

Thanks for reporting,
Jonathan

[1] git://git.ghostscript.com/ghostscript.git


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110214234425.GB25209@elie

autotools handling (Re: Accepted ghostscript 9.01~dfsg-1 (source all amd64))

[Jonathan Nieder]

Jonas Smedegaard wrote:

>* Stop custom-handling upstream-shipped patch noise or autotools
>  files: Properly shipped upstream now.
>  Stop build-depending on autotools-dev or autoconf.

Hmm, does this mean that supporting new architectures in config.guess
will require manual intervention in the future?

Thanks for a nice release.


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110212224333.GA12686@elie

Bug#419180: gs-esp fails while processing a file prepared for printing

[Jonathan Nieder]

Alexei Ustyuzhaninov wrote:

> Please find the files attached.
>
> I've just tried to re-execute this command with current ghostscript
> (8.71~dfsg2-6) and it failed again, but without segmentation fault.
> I will investigate this more carefully on weekend.

Thanks, Alexei.  I tried with 8.71~dfsg2-10 and 9.00~dfsg-4 on an
amd64 machine; the file renders okay and the command you suggested
(with "gs" in place of "gs-esp") runs to completion without complaint.

It is possible there is something different between our
configurations.  Listing various package versions for reference just
in case.

$ dpkg-query -W libcups2 libcupsimage2 libgs8 gsfonts gs-cjk-resource
gs-cjk-resource 1.20100103-2
gsfonts 1:8.11+urwcyr1.0.7~pre44-4.2
libcups21.4.4-7
libcupsimage2   1.4.5-3
libgs8  8.71~dfsg2-10



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110210215934.GB22644@elie

Bug#419180: gs-esp fails while processing a file prepared for printing

[Jonathan Nieder]

Hi Alexei,

Three years ago, you wrote:

> I can't print an openoffice document on a cups printer. Some
> investigation shows that the problem occurs when gs-esp processes a
> postscript file prepared for printing The situation may be modelled with
> the following command:
>
> $ cat prt.ps | /usr/bin/gs-esp -dQUIET -dDEBUG -dPARANOIDSAFER\
> -dNOPAUSE -dBATCH -dNOMEDIAATTRS -sDEVICE=cups -sstdout=%stderr\
> -sOUTPUTFILE=%stdout -c - >prt.out 2>&1
> Segmentation fault
>
> Files prt.ps and prt.out may be taken at
> https://208.195-224-87.telenet.ru:4445/.

Sorry for the long delay in responding; naturally I am interested to
see if this still happens.  Is the prt.ps in question available
somewhere?  Have you tried with recent ghostscript and cups?

Bastien, this might be another manifestation of
http://bugs.debian.org/422712

Thanks for reporting and sorry for the trouble,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110210101147.GA19667@elie

Re: gs-common: dvipdf + ps2pdf on .tex gives wrong papersize

[Jonathan Nieder]

Debian Bug Tracking System wrote:

> To: 444987-d...@bugs.debian.org
[...]
> Package: gs-common
> Version: 8.71~dfsg2-9
> 
> Closed as dup of 355757 (closed)

For the future, a nicer way to do the same is:

To: 444987-submit...@bugs.debian.org
Bcc: cont...@bugs.debian.org

unarchive 355757
forcemerge 355757 444987
quit

Strongly reminiscent of 355757 (which was fixed a while ago).

since that makes the bug log a little easier to read and is more
resilient against typos.

Not a big deal, just a pointer for the future. :)

Hope that helps,
Jonathan


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110207193444.GD11897@elie

Bug#379901: gs-gpl: `ps2pdf' fails to embed URW++ fonts from `gsfonts'

[Jonathan Nieder]

reopen 379901
submitter 379901 !
severity 379901 normal
tags 379901 = upstream moreinfo
done

Ludovic Courtès wrote:

> This is a 5-year old bug report, I changed email addresses in the
> meantime (congrats for finding a new one), and I even changed distros.
> :-)

Thanks for an update.  I'll take the bug. :)

Happy hacking,
Jonathan



--
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110207190945.GB11897@elie

Bug#422712: [gs-esp]

[Jonathan Nieder]

Bastien ROUCARIES wrote:

> Package: gs-esp
> 
> Does this bug fixed in gpl version ?

gs-esp was merged into ghostscript bit by bit, culminating in
2007-06-22 (so gs-gpl versions before then lack some gs-esp patches).

Anyway, I've checked that modern ghostscript doesn't have Troy's
patch applied but not decided whether something like it is useful for
robustness.  Probably it isn't (which would mean that the bug was
fixed in cups at some point).



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110207131039.GA11897@elie

Bug#470501: ghostscript bug

[Jonathan Nieder]

# does not sound intermittent
tags 470501 - unreproducible
quit

Bastien ROUCARIES wrote:

> tags 470501 + unreproducible
> tags  470501 + moreinfo
> thanks
> 
> I have tested with gs 2.71 and your file does not crash. Could you retest
> please and close the bug report if needed

Yes, I can render the file just fine, too (i386, ghostscript-x
8.71~dfsg2-9).

I wonder if http://bugs.ghostscript.com/show_bug.cgi?id=689340 is
related.  Any idea what could be different between the machines that
reproduce it and the ones that don't?



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110204203002.GA26971@elie

Bug#169678: "Print file was not accepted (client-error-bad-request)!"

[Jonathan Nieder]

tags 169678 - unreproducible
quit

Bastien ROUCARIES wrote:

> tags 169678 + unreproducible
> tags 169678 +  moreinfo
> thanks
>
> Please supply some information. feel free to close

It is amazing to see the bug list being separated between confirmed
and unconfirmed --- thanks very much for this.

My wild guess is that this is a (past or present) foomatic bug that
caused it to call ghostscript without specifying a driver (so it
defaulted to x11) in some circumstance.  At any rate, the reporter
didn't say what foomatic version was in use and whether it was an
intermittent problem --- so we do not even have enough information to
say if it is reproducible. :/




-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110204180404.GA2085@elie

Bug#440478: gs-esp: hangs at ~98% CPU with DEVICE=bbox reading a .ps from tiff2ps

[Jonathan Nieder]

found 440478 ghostscript/8.62.dfsg.1-3.2lenny5
quit

paolo wrote:
> 2011/1/23 Jonathan Nieder :

>> Do you know of a ghostscript version that did not have this problem?
>> (That could make life very easy.)
>
> nope, all gs I've installed so far (but am still on Lenny as most updated
> system, which means GPL Ghostscript 8.62 (2008-02-29) ) do have
> behave like that, sorry

I was hoping for an ancient version --- that maybe this had once
worked and then stopped working.  Well, one can't have everything. :)
Thanks for an update.



-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110126233244.GA30774@burratino

Re: Bug#610948: unblock: ghostscript/8.71~dfsg2-8

[Jonathan Nieder]

Jonathan Nieder wrote:

> didn't seem like something to spend the release team's time on (since
> anyway, they seem to prefer less change, all else being equal).

(By this I mean less change in testing.  Sorry for the lack of
clarity.)

Thanks again for your work on this.
Jonathan


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110126202243.GB18025@burratino

Re: Bug#610948: unblock: ghostscript/8.71~dfsg2-8

[Jonathan Nieder]

Jonas Smedegaard wrote:
> On Wed, Jan 26, 2011 at 01:13:21PM -0600, Jonathan Nieder wrote:

>> I'd like it.  apt's heuristics are kind of goofy, and if I
>> understand correctly then removing Breaks removes a small chance
>> of apt getting confused and deciding to remove ghostscript as part
>> of an upgrade.
>
> Whoah - if there is the slightest risk of that I agree it is worth
> the effort.
>
> Any other complaints, before I start compiling?

None from my end.  I should mention that I'm not an apt/aptitude
resolver expert; on the contrary, I'm terrified of those algorithms.
So please take my worry with a grain of salt.

> P.S.  Beware that you posted only to me!  I respond equally to
> respect eventual privacy concerns of yours, but recommend you to
> repost.

I had only wanted to mention why that change would be a comfort; it
didn't seem like something to spend the release team's time on (since
anyway, they seem to prefer less change, all else being equal).

Cc-ing debian-printing so others can correct me or provide pointers.

Jonathan


-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110126202029.GA18025@burratino

Bug#122415: gs vertically misaligns printed output

[Jonathan Nieder]

tags 122415 - moreinfo
tags 122415 + upstream
reassign 122415 ghostscript
found 122415 ghostscript/6.51-5
quit

Hi,

Richard Kettlewell wrote:

> Oops, my apologies, I should have put that in the original message.
> The gs command line is:
>
> gs -sDEVICE=stp \
> -sModel=escp2-660 \
> -sQuality='360dpi' \
> -sInkType='CMYK' \
> -sMediaType='Plain' \
> -sPaperSize='A4' \
> -sPAPERSIZE='a4' \
> -sDither='Adaptive' \
> -dImageType=0 \
> -r360 \
> -q -dSAFER -dNOPAUSE -dBATCH -sOutputFile=- -
>
> The paper is indeed physically A4 paper, and the printer is an Epson
> Stylus Color 660.
>
>>> You can, hopefully, make out what I mean in the photo at:
>>> 
>>> http://www.greenend.org.uk/rjk/junk/gsbug.jpg
>> 
>> Just got a timeout...
>
> It should be working now.

Hmm, there was some work in this area recently upstream, but for HP
printers.  So I find this bug quite believable. :)

Anyone can debug this; it shouldn't require an Epson printer.  The
ESC/P2 language is documented at
http://web.archive.org/web/*/http://www.epson.co.uk/support/manuals/pdf/ESCP/Part_1.pdf
http://web.archive.org/web/*/http://www.epson.co.uk/support/manuals/pdf/ESCP/Part_2.pdf

Thanks for reporting.
Jonathan




-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110123132310.GA22546@burratino

Bug#350553: ghostscript: major slowdown after upgrade

[Jonathan Nieder]

tags 350553 - moreinfo
reassign 350553 ghostscript
found 350553 gs-esp/8.15.1.dfsg.1-1
found 350553 ghostscript/8.62.dfsg.1-2.1
found 350553 ghostscript/8.71~dfsg2-6.1
quit

Marc Lehmann wrote:

> I downgraded and of course had the speed back then, but now i upgraded to
> squeeze and the slowdown is as horrible as before.
>
> also, this seems to be a very common issue, there are lots of reports about
> people having printing issues because gs takes a long time now, for ps that
> was fast to print before. it seems upstream thinks that this is a
> ubuntu/debian issue, and some people have reported that downloading and
> building upstream results in a fast ghostscript.

Thanks, Marc.  I hope I can find time to look into it (though anyone
else interested is welcome to test old packages and sift through
debdiffs, too).




-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110123130148.GA22379@burratino

Bug#480423: gs-esp: some documents printed using ML-1020 driver cause printer to become unresponsive.

[Jonathan Nieder]

Hi Ben,

Ben Hildred wrote:

> I have a Dell 1100 printer which uses the samsung ML-1020 driver.
> (rebranded printer) In many respects this printer works reasonably well.
> Overall a satisfactory b&w printer. However many documents give me
> trouble printing, paticualary documents with lots of graphic information (ie.
> printing google maps form firefox give me corupted horizontal bars, some
> blueprints and photos cause the printer to cease responding requiring a
> reboot of the printer)

Thanks for reporting.  Do you have an example?  (Printing to file as PS
is a good way to make one.)

> I suspect this may be related to the 64kb bug on
> http://www.openprinting.org/download/printing/samsung-gdi/README.txt

Unfortunately Grant Taylor's patch was already applied in 8.15.3.dfsg.1
so that can't be the fix. :/

Sorry for the long delay.
Jonathan




-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110123090328.GA32680@burratino

Bug#474300: gs segfaults on russian fonts

[Jonathan Nieder]

tags 474300 + upstream moreinfo
quit

Miloslav Semler wrote:

> when I tried to print some document in russian (cyrillic), it does not
> print. In
> mean time I found some problem with ghostscript:
>
> ESP Ghostscript 815.03: Failed to interpret TT instructions of the font
> DejaVuSa
> ns-Bold. Continue ignoring instructions of the font.
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1214211264 (LWP 5090)]
> 0x08247fa1 in ialloc_consolidate_free ()
[...]
> commandline parameters: -sPAPERSIZE=a4 -g9920x7016 -r1200x600
> -sDEVICE=pbmraw -sOutputFil
> e=tmp.pbm tmp.pdf

Thanks for reporting.  Do you have a copy of tmp.pdf?  Can you reproduce
this still (with any version of ghostscript, not necessarily the latest
one)?




-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110123084604.GA32542@burratino

Bug#422712: gs-esp: pstoraster fails with signal 11 when printing cups testpage

[Jonathan Nieder]

severity 422712 wishlist
retitle 422712 pstoraster segfaults with ancient cups
tags 422712 - moreinfo
tags 422712 + upstream
quit
(-cc: the world since I have veered off topic)

Troy Rollo wrote:

> I do not recall the precise reasoning behind this, other than that at the 
> time 
> the patch seemed to make sense mathematically and without it there was a 
> segmentation violation
[...]
> The code patched seems to attempt to constrain "lasty" to a position within 
> the passed in "btile", vertically (that is, "btile->size.y").

That helps.  If I understand correctly then

by = lasty % btile->size.y;
if (by < 0)
by += btile->size.y;

would be another way to convey the same thing.

The context is beyond my depth (and undercommented, I suppose).
wrap_shifted_cursor seems to do something complicated involving
tile_shift, so if I had to guess, the fix would be something like:

ptc->tile.shift = btile->shift;
by = lasty + btile->size.y;
if (by < 0)
by += btile->size.y;
bx = endx;
if (ptc->tile.shift) {
int quotient = lasty / btile->size.y;
if (lasty < 0)
quotient--;
bx += quotient * ptc->tile.shift;
}
bx %= tw;
if (bx < 0)
bx += tw;

What I had been hoping for was something like "lasty gets set using
this library call from CUPS, which used to return this out-of-range
but meaningful value but always returns nonnegative values now".
Oh, well.

Maybe it would make sense to do

if (by < 0)
... error out with a helpful message ...

I'm marking figuring this out as a wishlist bug for now.

Thanks again.
Jonathan




-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110123080559.GC31997@burratino

Bug#458008: gs-esp: gs crash on ps generated by xpdf

[Jonathan Nieder]

retitle 458008 gs: ERROR: /ioerror in --image--
tags 458008 + confirmed upstream
forwarded 458008 http://bugs.ghostscript.com/show_bug.cgi?id=691902
reassign 458008 ghostscript
found 458008 gs-esp/8.15.3.dfsg.1-1
found 458008 ghostscript9.00~dfsg-2
quit

Tim wrote:

> ERROR: /ioerror in --image--

Huzzah!  Nicely reproducible.  Please send any further comments
upstream (or here if bugzilla account creation doesn't work or
something).

Reproduction recipe:

 1. gunzip Shuttle56-101-038Dec03Dec3107tl24.ps.gz
 2. ghostscript -dSAFER Shuttle*.ps

Thanks for a clear report.




-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110123072933.GB31997@burratino

Bug#359821: gs: ghostcript dies when printing to epson r300, but not hp lj1200

[Jonathan Nieder]

submitter 359821 !
quit

Kenward Vaughan wrote:
>> Kenward Vaughan wrote:

>>> Error: /ioerror in --image--
[...]
> I can hardly remember this now... :(  The R300 isn't even alive.  I'm
> sorry.

That's fine.  Stealing the bug so (hopefully) you won't get more mail.

Probably this will be lumped with the other "/ioerror in --image" bugs
(which are fixed, I suspect). ;-)

Thanks.

Regards,
Jonathan




-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110123060628.GB31548@burratino

Bug#437262: Actually, that's gs-esp there...

[Jonathan Nieder]

reassign 437262 ghostscript
reassign 443957 ghostscript
forcemerge 437262 443957
found 437262 gs-gpl/8.56.dfsg.1-1.1
quit

Anthony DeRobertis wrote:

> Gilberto's report actually shows its using gs-esp (note the "ESP
> Ghostscript" down at the bottom). However, this actually happens with
> gs-gpl as well, with basically the same error.

The versions merged at long last.




-- 
To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110123054101.GA30283@burratino