Bug#425405: Not a bug
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
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
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
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#586970: ghostscript: symbol lookup error: /usr/lib/libgs.so.8: undefined symbol: TIFFCleanup
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#582522: please document D_MAX_BLOCKS_IN_MCU deviation from upstream more clearly
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#681843: ghostscript: ps2epsi inserts '\r' (0x0d)
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#681843: ghostscript: ps2epsi inserts '\r' (0x0d)
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#404017: new driver for ghostscript
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
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#664966: Add an option to disable T3CCITT encoding
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 ken.sh...@artifex.com 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#663902: ghostscript: FTBFS on hurd-i386: extra gs_realloc in symbols file
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#661764: dangling symlink /usr/share/ghostscript/9.05/Resource/CIDFSubst/DroidSansFallback.ttf
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 chris.lidd...@artifex.com
| 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#613665: ghostscript: circular dependency with gs-cjk-resource, libgs9
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#661863: ghostscript: CIDFont fallback to DroidSansFallback doesn't happen as advertised
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 return 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 return 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#661764: dangling symlink /usr/share/ghostscript/9.05/Resource/CIDFSubst/DroidSansFallback.ttf
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
Re: cups ignores duplex setting in postscript files
# 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
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 http://bugs.ghostscript.com/ 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
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
Re: libjpeg8: Please provide variant compiled with #define D_MAX_BLOCKS_IN_MCU 64
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#608802: ghostscript: version 8.71~dfsg2-6.1 breaks preview-latex-style
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
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 (?)
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#644670: ghostscript: FTBFS: devlibs error: There is no package matching [liblcms2-dev] and noone provides it
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)
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
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#638277: libgs8 segfault : print jobs (recto/verso) stop after 2nd page
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
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 2err 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
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#588929: CUPS unable to print. CUPS runs gs and libgs8 shows segmentation fault in the /var/log/messages
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
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://bugs.debian.org/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
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
Re: Recent upgrade broke my canon printer
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
Bug#626122: [sparc] ghostscript: segfault using pdfwrite device
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=altreearch=sparcver=1.0.1-4stamp=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
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#359821: gs: ghostcript dies when printing to epson r300, but not hp lj1200
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#480423: gs-esp: some documents printed using ML-1020 driver cause printer to become unresponsive.
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 bw 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
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#414002: ghostscript: cannot open OutputFile if -dSAFER specified with piped or interactive input
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 alex.cherepa...@artifex.com 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
found 619306 ghostscript/9.02~dfsg-1 quit Hi, Colin wrote: On Mon, Apr 18, 2011 at 10:37 PM, Jonas Smedegaard d...@jones.dk 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
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
Re: Problems with libgs9
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#522417: ghostscript: Doesn't work with Brother printers
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: functionalityB/functionality driverhl1250/driver Finally I get working the printer using the foomatic drivers: Brother HL - 2030 Foomatic/hl1250 Ah, ok. I suppose the failures happen with driver idgutenprint/id /driver 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 execution filter / prototypegs -q -dPARANOIDSAFER -dNOPAUSE -dBATCH -sDEVICE=ijs -sIjsServer=ijsgutenprint.5.2 -dIjsUseOutputFD%A -sIjsParams=quot;STP_VERSION=5.2.6,%Bquot;%Z -sOutputFile=- -/prototype /execution 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
Bug#619934: /usr/bin/pdfopt: Let Adobe do its own advertizement rather than pdfopt
# 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#619476: libgs9: gs catch segfault on printing specific pdf, after page 6
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#619306: ghostscript segfaults on some eps file
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=value optimized out,
Out=0x7fffc970)
at cmslut.c:512
#2 0x77fcb741 in NormalXFORM (p=0x887770, in=value optimized out,
out=value optimized 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=value optimized out)
at cmssamp.c:271
#5 0x77fcc8bd in cmsCreateProofingTransform (InputProfile=value
optimized out, InputFormat=196618,
OutputProfile=0x580660, OutputFormat=262170, ProofingProfile=value
optimized out, nIntent=1,
ProofingIntent=3, dwFlags=9216) at cmsxform.c:1537
#6 0x77fccfbb in cmsCreateTransform (Input=value optimized out,
InputFormat=value optimized out,
Output=value optimized out, OutputFormat=value optimized out,
Intent=value optimized out,
dwFlags=value optimized out) at cmsxform.c:1618
#7 0x775eb3d7 in gsicc_get_link_profile (pis=value optimized out,
dev=value optimized out,
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=value optimized
out, size=value optimized out,
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=value optimized
out, 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#616054: ghostscript: segfault on particular file not reproducible in git master
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#618530: ghostscript: cannot open OutputFile if -dSAFER specified with piped or interactive input
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
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#618530: ghostscript: cannot open OutputFile if -dSAFER specified with piped or interactive input
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
Re: libgs9: please Recommends: (not Depends:) gs-cjk-resource
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
Getting started with CDBS (Re: libgs9: please Recommends: (not Depends:) gs-cjk-resource)
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 target 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
Bug#613580: libgs9: please Recommends: (not Depends:) gs-cjk-resource
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
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
Bug#169678: Print file was not accepted (client-error-bad-request)!
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
Re: Bug#610948: unblock: ghostscript/8.71~dfsg2-8
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#440478: gs-esp: hangs at ~98% CPU with DEVICE=bbox reading a .ps from tiff2ps
found 440478 ghostscript/8.62.dfsg.1-3.2lenny5 quit paolo wrote: 2011/1/23 Jonathan Nieder jrnie...@gmail.com: 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
Bug#422712: gs-esp: pstoraster fails with signal 11 when printing cups testpage
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#474300: gs segfaults on russian fonts
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#480423: gs-esp: some documents printed using ML-1020 driver cause printer to become unresponsive.
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 bw 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#350553: ghostscript: major slowdown after upgrade
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#122415: gs vertically misaligns printed output
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#248947: cupsys: gs crash, no pages output
tags 248947 + upstream moreinfo retitle 248947 ghostscript: Error: /typecheck in --.unread-- printing postscript documents quit Derrick 'dman' Hudson wrote: I can no longer print postscript documents. Tonight is the first time I tried printing since the last package upgrade. (although I did print a pdf earlier tonight. I guess it only affects postscript) The error log reports the following: [...] Error: /typecheck in --.unread-- Hmm. Unfortunately this is a vague message; I suspect it represents an error in the command line options. Some internet sightings: Using ps2pdf on a filename with spaces. [1] That one was fixed by Tim Waugh in ghostscript-7.20~256. The ImageMagick identify and convert[2][3] utilities once provoked this in some way. Use of an unknown option[4] (for example, due to a mismatch between expected and actual ghostscript version) can also provoke it. [1] http://www.ghostscript.com/pipermail/bug-gs/2003-June/003222.html [2] http://studio.imagemagick.org/pipermail/magick-users/2003-September/010856.html [3] http://studio.imagemagick.org/pipermail/magick-users/2003-June/009642.html [4] http://groups.google.com/group/comp.text.tex/msg/4d432d65f7b5d777 -- 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/20110123020532.GA27463@burratino
Re: cupsys: No debug information logged from gs-esp
tags 321484 + moreinfo help quit Hi Roger et al, Roger Leigh wrote: Ambrose Li ambrose...@cccgt.org writes: After upgrading to the new gutenprint drivers, if a Windows print job causes gs-esp to crash, /var/log/cups/errors will not log anything useful from gs-esp, even if the debug level is set to debug2. Running gs-esp manually with the crashed print job reveals that gs-esp cannot find Helvetica-Bold. This should have been logged in /var/log/cups/errors, esp. when the debug level is debug or debug2. This is a gs-esp bug (it was recently updated in addition to gutenprint); I've reassigned the bug. Do you happen to remember how gutenprint invokes ghostscript? I am looking to fix the ancient Bug#321484, but to do so I would need to be able to reproduce it. Thanks, and 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/20110123021918.GA27662@burratino
Bug#324458: gs-common: ps2pdf segfaults on s390
reassign 324458 ghostscript retitle 324458 [s390, powerpc] ps2pdf segfaults unarchive 457547 forcemerge 457547 324458 quit Hi Robert and Jack, Robert Lemmen wrote: as you can see from this [0] build log, ps2pdf segfaults on s390 for an input that can be processed just fine on other architectures. the last lines of output are: ps2pdf ragel-guide.ps ragel-guide.pdf Unrecoverable error: typecheck in .getdeviceparams [...] http://buildd.debian.org/fetch.php?pkg=ragelver=4.1-3arch=s390stamp=1124455821file=logas=raw I'm merging this with Bug#457547; please let me know if that turns out to be incorrect. 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/20110123023803.GA27744@burratino
Bug#359821: gs: ghostcript dies when printing to epson r300, but not hp lj1200
retitle 359821 gs: Error: /ioerror in --image-- printing to epson R300 through cups (hp lj1200 works ok) tags 359821 + moreinfo quit Kenward Vaughan wrote: [Subject: gs: ghostcript dies when printing to epson r300, but not hp lj1200] [...] Error: /ioerror in --image-- [...] It's a fragment of the error_log file for CUPS. I'll gladly send the whole thing as an attachment. An example postscript file and a commandline for gs that reproduces the error would indeed be nice. Yes, I know it's a little late to ask. :/ Thanks for the report, 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/20110123031418.GA28603@burratino
Bug#422712: gs-esp: pstoraster fails with signal 11 when printing cups testpage
tags 422712 + moreinfo quit Hi, Troy Rollo wrote: This only seems to affect applications using the CUPS v1.1 libraries - applications using the CUPS v1.2 libraries seem to work OK. diff -ru gs-esp-8.15.3.dfsg.1/src/gxcht.c gs-esp-8.15.3.dfsg.1-fixed/src/gxcht.c --- gs-esp-8.15.3.dfsg.1/src/gxcht.c 2005-01-19 15:08:41.0 +1100 +++ gs-esp-8.15.3.dfsg.1-fixed/src/gxcht.c2007-12-25 19:55:36.0 +1100 @@ -1087,7 +1087,14 @@ int tw = btile-size.x; int bx = ((ptc-tile_shift = btile-shift) == 0 ? endx : endx + lasty / btile-size.y * ptc-tile_shift) % tw; -int by = lasty % btile-size.y; +int by; + +if (lasty 0) + by = btile-size.y - (-lasty % btile-size.y); +else + by = lasty % btile-size.y; + +by = lasty % btile-size.y; This patch does not seem to be part of current ghostscript. Could you explain what it does? Is there an example postscript file and gs invocation that would trigger it, or is it useful for robustness reasons? Thanks and 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/20110123041023.GA28975@burratino
Bug#437262: CUPS with gs-gpl doesn't print pdf pages with images
retitle 437262 gs: /ioerror in --image-- printing PDF with images tags 437262 + moreinfo quit Hi, Gilberto Taccari wrote: CUPS doesn't print pdf pages with images: the result is a blank page and a stop of printing job. Reading log file I think that the cause of problem is gs-gpl (I've the same problem with gs-esp). That's some lines from log file: E [11/Aug/2007:12:10:01 +0200] [Job 57] /ioerror in --image-- Anthony DeRobertis wrote: I have tested by running gs-gpl and gs-esp directly on one of the spool files. I will attach the spool file to the bug. Good idea. Could you? Thanks for reporting, and sorry for the long delay in responding. 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/20110123051218.GA29958@burratino
Bug#440478: gs-esp: hangs at ~98% CPU with DEVICE=bbox reading a .ps from tiff2ps
reassign 440478 ghostscript found 440478 gs-esp/8.15.3.dfsg.1-1 found 440478 ghostscript/9.00~dfsg-2 tags 440478 + confirmed upstream quit Hi Paolo, Paolo wrote: let PS file be fax.ps: - gv fax.ps - shows up on screen correctly - ps2pdf fax.ps fax.pdf - xpdf shows just a tiny white square - ps2ps fax.ps fax2.ps - bbox is 0 0 0 0, gv fax2.ps - blank - gs -sDEVICE=lj4dith- prints just ~70 char of pjl cmd - nothing gets printed on printer - gs -sDEVICE=bbox - gs hangs ~98% CPU forever, strace -f shows: Interesting. Yes, I can reproduce this: - gs -dSAFER fax.ps; # just shows a white screen. - evince fax.ps; # shows the fax. - $ gs -dSAFER -sDEVICE=bbox -sOutputFile=/dev/null fax.ps GPL Ghostscript 9.00 (2010-09-14) Copyright (C) 2010 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. [hangs here] Backtrace at a random moment: | #0 zoom_y (st=0xb2697ac, pr=0xbfc24734, pw=0xbfc24728, last=0) at ./base/siscale.c:388 | #1 s_IScale_process (st=0xb2697ac, pr=0xbfc24734, pw=0xbfc24728, last=0) at ./base/siscale.c:594 | #2 image_render_interpolate_icc (penum=0xb108214, buffer=0xb2690d0 \377\377[... etc ...]\377..., data_x=0, iw=1728, h=1, dev=0xb269fb4) at ./base/gxiscale.c:1019 | #3 gx_image1_plane_data (info=0xb108214, planes=0xb26a75c, height=9, rows_used=0xbfc25d6c) at ./base/gxidata.c:209 | #4 bbox_image_plane_data (info=0xb20c1cc, planes=0xb26a75c, height=9, rows_used=0xbfc25d6c) at ./base/gdevbbox.c:1063 | #5 bbox_image_plane_data (info=0xb20c0f8, planes=0xb26a75c, height=9, rows_used=0xbfc25d6c) at ./base/gdevbbox.c:1063 | #6 gs_image_next_planes (penum=0xb26a5ec, plane_data=0xbfc25ddc, used=0xbfc25e54) at ./base/gsimage.c:600 | #7 image_file_continue (i_ctx_p=0xb033ef8) at ./psi/zimage.c:549 | #8 in interp (pi_ctx_p=0xb00ba14, pref=value optimized out, perror_object=0xbfc26bf4) at ./psi/interp.c:1150 | #9 gs_call_interp (pi_ctx_p=0xb00ba14, pref=0xbfc26b78, user_errors=1, pexit_code=0xbfc26bfc, perror_object=0xbfc26bf4) at ./psi/interp.c:484 | #10 gs_interpret (pi_ctx_p=0xb00ba14, pref=0xbfc26b78, user_errors=1, pexit_code=0xbfc26bfc, perror_object=0xbfc26bf4) at ./psi/interp.c:442 | #11 gs_main_interpret (minst=0xb00b9c0, user_errors=1, pexit_code=0xbfc26bfc, perror_object=0xbfc26bf4) at ./psi/imain.c:240 | #12 gs_main_run_string_end (minst=0xb00b9c0, user_errors=1, pexit_code=0xbfc26bfc, perror_object=0xbfc26bf4) at ./psi/imain.c:556 | #13 gs_main_run_string (minst=0xb00b9c0, str=0xb130be8 2f746d702f6661782e7073.runfile, user_errors=1, pexit_code=0xbfc26bfc, perror_object=0xbfc26bf4) at ./psi/imain.c:496 | #14 run_string (minst=0xb00b9c0, str=value optimized out, options=value optimized out) at ./psi/imainarg.c:814 | #15 runarg (minst=0xb00b9c0, pre=value optimized out, arg=value optimized out, post=0x84ba3e5 .runfile, options=3) at ./psi/imainarg.c:805 | #16 argproc (minst=0xb00b9c0, arg=0xbfc27cc4 /tmp/fax.ps) at ./psi/imainarg.c:738 | #17 gs_main_init_with_args (minst=0xb00b9c0, argc=5, argv=0xbfc27694) at ./psi/imainarg.c:215 | #18 main (argc=5, argv=0xbfc27694) at ./psi/gs.c:96 Do you know of a ghostscript version that did not have this problem? (That could make life very easy.) fax.ps (~10kB) pasted at bottom - hope it gets through Attached to this message in more wasteful MIME format for the convenience of others. ;-) 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/20110123053249.GC30054@burratino
Bug#437262: Actually, that's gs-esp there...
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
Bug#359821: gs: ghostcript dies when printing to epson r300, but not hp lj1200
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#458008: gs-esp: gs crash on ps generated by xpdf
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#274553: gs-esp: pdf document printing fails
tags 274553 + upstream moreinfo quit Hi Mark, Mark Hubbard wrote: Package: gs-esp Version: 7.07.1-9 [...] I [02/Oct/2004:16:02:27 +0100] Started backend /usr/lib/cups/backend/parallel (PID 894) for job 31. E [02/Oct/2004:16:02:30 +0100] [Job 31] Unable to get media size! E [02/Oct/2004:16:02:30 +0100] [Job 31] Invalid printer settings! I believe that this is the same ghostscript bug reported at Redhat to do with null page sizes: Chasing down links leads to [1]: --- Comment #14 From Alex Cherepanov 2006-06-04 15:59:12 --- The patch (and analysis) is incorrect. Some printers don't support setting the page using numeric values but a small set of special purpose operators. The table look-up checks whether there is a predefined page size operatot to set this page size. When there is no such operator, null indicates that the page size should be set using numeric method. The patch makes Ghostscript ignore the page size of the document and use US Letter size for any non-standard document. This is clearly wrong. Probably, most users would prefer to fit non-standard pages to the paper size. However, for the printers with expensive media, a PostScript error is preferable. Do you agree with this analysis? Are you sure it is the same bug? Aside from that, I'd also be interested in whether the same problem appears with current ghostscript-x. (I am able to open PDFs with gs -dSAFER on version 9.00~dfsg-2, at least). Thanks for the report, Jonathan [1] http://bugs.kde.org/show_bug.cgi?id=61922 -- 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/20110115092552.GC27448@burratino
Bug#291670: gs-common: error in printing pdf files
tags 291670 + upstream moreinfo quit Hi, Alberto Hernando wrote: I have a problem with printing pdf files. I can see these files well with xpdf and kghostview, but when I try to print them, the pages are scaled so that the margins are lost. Mario Lipinski wrote: i just had the same problem and solved it by setting the default gs interpreter to gs-gpl. It was set to gs-esp before. (update-alternatives --config gs) Is this problem still present for you with current gs? (I assume not, but it can't hurt to check.) Thanks to both of you for reporting. 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/20110115093803.GA27657@burratino
Bug#314169: gs: gs -sDEVICE=ppmraw fails with unrecoverable error
reassign 314169 ghostscript found 314169 gs/8.01-5 found 314169 ghostscript/9.00~dfsg-2 tags 314169 + confirmed help quit Hi, Uwe Muench wrote: when calling gs with the option -sDEVICE=ppmraw, 36 gs -sDEVICE=ppmraw fax-eltern-1.ps it fails with this error message: So it does. [1] The same happens when trying to open the PS file with 'xv', because that program calls 'gs' with the option -sDEVICE=ppmraw. For curiosity's sake, what version of xv do you have? It seems it was removed from the archive after 3.10a-26 or so but snapshot.debian.org only has 3.10a-20. gs experts: is this an error in usage or is something terribly wrong? Even in the former case the error message could be improved. Thanks for a clear report. Regards, Jonathan [1] $ gs -dSAFER -sDEVICE=x11 debian-cd.ps GPL Ghostscript 9.00 (2010-09-14) [...] Substituting font Helvetica-Bold for Arial-Bold. Loading NimbusSanL-Bold font from /usr/share/fonts/type1/gsfonts/n019004l.pfb... 2587224 1248792 6359328 4089934 5 done. showpage, press return to continue showpage, press return to continue showpage, press return to continue showpage, press return to continue GSquit $ gs -dSAFER -sDEVICE=laserjet debian-cd.ps GPL Ghostscript 9.00 (2010-09-14) [...] Substituting font Helvetica-Bold for Arial-Bold. Loading NimbusSanL-Bold font from /usr/share/fonts/type1/gsfonts/n019004l.pfb... 2610424 1253752 3911248 1642131 5 done. GPL Ghostscript 9.00: Could not open the file . Error: /invalidfileaccess in --showpage-- Operand stack: 1 true Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1894 1 3 %oparray_pop 1893 1 3 %oparray_pop 1877 1 3 %oparray_pop 1771 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- 1777 0 4 %oparray_pop --nostringval-- --nostringval-- Dictionary stack: --dict:1153/1684(ro)(G)-- --dict:0/20(G)-- --dict:78/200(L)-- --dict:108/300(L)-- Current allocation mode is local Last OS error: 2 Current file position is 180508 GPL Ghostscript 9.00: Unrecoverable error, exit code 1 GPL Ghostscript 9.00: Could not open the file . GPL Ghostscript 9.00: ERROR -9 closing laserjet device. See gs/src/ierrors.h for code explanation. -- 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/20110115101002.GA27856@burratino
Bug#343901: gs-esp's lx5000 driver runs into infinite loop with mozilla's postscript files
reassign 343901 libgs9 found 343901 gs-esp/8.15.1.dfsg.1-1 found 343901 ghostscript/9.00~dfsg-2 tags 343901 + confirmed quit Sebastian Schmidt wrote: gs-esp with -sDEVICE=lx5000 hangs when printing PostScript files generated by mozilla (firefox, in this case). I have attached a file which causes gs to fail; you can reproduce this bug with gs -sDEVICE=lx5000 -sOutputFile=/dev/null file gs without -sDEVICE or gv display the file fine. Thanks for a clear report. Still happens exactly as described. Ghostscript wizards: any ideas for tracking this down? $ gs -dSAFER -sDEVICE=lx5000 -sOutputFile=/dev/null ~/web/mozilla.ps GPL Ghostscript 9.00 (2010-09-14) Copyright (C) 2010 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Loading NimbusRomNo9L-Regu font from /usr/share/fonts/type1/gsfonts/n021003l.pfb... 2619136 1254085 8750092 7450110 1 done. Loading NimbusRomNo9L-Medi font from /usr/share/fonts/type1/gsfonts/n021004l.pfb... 2682564 1363434 8750092 7456503 1 done. Loading NimbusRomNo9L-MediItal font from /usr/share/fonts/type1/gsfonts/n021024l.pfb... 2799708 1471362 8770188 7466010 1 done. Loading NimbusRomNo9L-ReguItal font from /usr/share/fonts/type1/gsfonts/n021023l.pfb... 2916852 1582897 8770188 7472159 1 done. Loading NimbusSanL-Regu font from /usr/share/fonts/type1/gsfonts/n019003l.pfb... 3013900 1678963 8770188 7478372 1 done. Loading NimbusSanL-Bold font from /usr/share/fonts/type1/gsfonts/n019004l.pfb... 3090852 1764420 8790284 7487849 1 done. Loading NimbusSanL-BoldItal font from /usr/share/fonts/type1/gsfonts/n019024l.pfb... 3187900 1852077 8790284 7493998 1 done. Loading NimbusSanL-ReguItal font from /usr/share/fonts/type1/gsfonts/n019023l.pfb... 3284948 1938835 8790284 7500147 1 done. Loading NimbusMonL-Regu font from /usr/share/fonts/type1/gsfonts/n022003l.pfb... 3402092 2053607 8810380 7509624 1 done. Loading NimbusMonL-Bold font from /usr/share/fonts/type1/gsfonts/n022004l.pfb... 3519236 2175599 8810380 7515901 1 done. Loading NimbusMonL-BoldObli font from /usr/share/fonts/type1/gsfonts/n022024l.pfb... 3574036 2193018 8810380 7465778 1 done. Loading NimbusMonL-ReguObli font from /usr/share/fonts/type1/gsfonts/n022023l.pfb... 3671084 2300599 8810380 7471927 1 done. Loading StandardSymL font from /usr/share/fonts/type1/gsfonts/s05l.pfb... 3711276 2340770 8810380 7478380 1 done. [hangs there at 100% CPU] Attaching with gdb gives (gdb) bt #0 0xb7218041 in ?? () from /usr/lib/libgs.so.9 #1 0xb7219822 in ?? () from /usr/lib/libgs.so.9 #2 0xb710bbd0 in gx_default_print_page_copies () from /usr/lib/libgs.so.9 #3 0xb710bd05 in gdev_prn_output_page () from /usr/lib/libgs.so.9 #4 0xb7276ec3 in gs_output_page () from /usr/lib/libgs.so.9 #5 0xb70806df in ?? () from /usr/lib/libgs.so.9 #6 0xb7050fc4 in ?? () from /usr/lib/libgs.so.9 #7 0xb7052030 in gs_interpret () from /usr/lib/libgs.so.9 #8 0xb7045df8 in gs_main_run_string_end () from /usr/lib/libgs.so.9 #9 0xb7046252 in gs_main_run_string_with_length () from /usr/lib/libgs.so.9 #10 0xb70462aa in gs_main_run_string () from /usr/lib/libgs.so.9 #11 0xb7047060 in ?? () from /usr/lib/libgs.so.9 #12 0xb70478f8 in ?? () from /usr/lib/libgs.so.9 #13 0xb7047b6a in ?? () from /usr/lib/libgs.so.9 #14 0xb7048feb in gs_main_init_with_args () from /usr/lib/libgs.so.9 #15 0xb704a10e in gsapi_init_with_args () from /usr/lib/libgs.so.9 #16 0x0804887c in main () Using the usual X11 driver gives the same terminal output, with showpage, press return to continue appended and a webpage shows. -- 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/20110115181621.GA1169@burratino
Bug#352069: gs: Japanese printing problem
reassign 352069 ghostscript found 352069 gs/8.15-4.1 tags 352069 + moreinfo help quit Jan Willem Stumpel wrote: There are problems with Japanese printing through Ghostscript (gs variants with gs-cjk-resource). These problems turn up with - moz: printing through PostScript/Default (not xprint) in Mozilla. - xpdf: printing through xpdf (with Japanese support). [...] new old === === gs-esp, moz ryumin errorOK gs-esp, xpdf ryumin errorOK gs-gpl, moz ryumin errorboxes gs-gpl, xpdf ryumin errorrubbish Explanation: - ryumin error means that when a .ps file is viewed with gv, you get the dreaded error message which begins Error: /undefinedresource in --findresource-- Operand stack: F3331_0 0 Ryumin-Light-H Font Ryumin-Light-H (Ryumin-Light-H) 12 Ryumin-Light H H Ryumin-Light Ryumin-Light Ryumin-Light --nostringval-- (r) --nostringval-- CMap (r) CMap (r) Thanks for a clear report. I tried printing from chromium and it worked okay, but it only supports printing by PDF. Do you perhaps have a postscript file exhibiting the problem? Ideally some ghostscript wizard can make sense of the error message, but barring that, the ability to reproduce it would be nice. 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/20110115184603.GA1416@burratino
