[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#478248: marked as done (cupsys: CUPS fails to print certain PDF files)



Your message dated Sat, 30 Apr 2011 20:04:59 -0500
with message-id <20110501010429.GA32759@elie>
and subject line Re: cupsys: CUPS fails to print certain PDF files
has caused the Debian Bug report #478248,
regarding cupsys: CUPS fails to print certain PDF files
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
478248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478248
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: cupsys
Version: 1.3.7-5
Severity: important


This package worked just fine until the latest update from CUPS 1.3.7-1 to the present set of packages. While I can print some PDFs, other pdfs (such as ones created on the Macintosh) fail. Please note that this problem does *not* seem to be related to the XPDF utils -- the problem only occured after the latest CUPS update.
 
 
According to the debug output,

D [25/Apr/2008:07:59:39 -0500] [Job 207] Error: /undefined in ViZj1\
D [25/Apr/2008:07:59:39 -0500] [Job 207] Operand stack:
D [25/Apr/2008:07:59:39 -0500] [Job 207] 
D [25/Apr/2008:07:59:39 -0500] [Job 207] Execution stack:
D [25/Apr/2008:07:59:39 -0500] [Job 207] %interp_exit   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --nost
ringval--   --nostringval--   false   1   %stopped_push   1905   1   3   %oparray_pop   1904   1   3   %oparray_pop   1888   1   3   %oparray_pop   1771   1   3   %op
array_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--
D [25/Apr/2008:07:59:39 -0500] [Job 207] Dictionary stack:
D [25/Apr/2008:07:59:39 -0500] [Job 207] --dict:1152/1684(ro)(G)--   --dict:0/20(G)--   --dict:99/200(L)--   --dict:65/75(L)--   --dict:18/25(L)--
D [25/Apr/2008:07:59:39 -0500] [Job 207] Current allocation mode is local
D [25/Apr/2008:07:59:39 -0500] [Job 207] Last OS error: 2
D [25/Apr/2008:07:59:39 -0500] [Job 207] GPL Ghostscript 8.62: Unrecoverable error, exit code 1
E [25/Apr/2008:07:59:39 -0500] PID 27481 (/usr/lib/cups/filter/pstoraster) stopped with status 1!

For *some* older pdf files created on this Linux box, I see errors such as:

D [25/Apr/2008:08:05:23 -0500] [Job 208] Error: /ioerror in --image--

I if convert these failing older PDF files to PDF using ImageMagick ("convert x.pdf x.pdf"), the files print -- but the output is completely erroneous, a mass of splotches overlaying some distorted text.

The test print page prints normally. Some PDF files print normally. I suspect that the problem lies with the pstops or pdftops filters, but I can't find any documented method to test these filters.

Please let me know if you need additional information.


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages cupsys depends on:
ii  adduser               3.107              add and remove users and groups
ii  cupsys-common         1.3.7-5            Common UNIX Printing System(tm) - 
ii  debconf [debconf-2.0] 1.5.21             Debian configuration management sy
ii  ghostscript           8.62.dfsg.1-2      The GPL Ghostscript PostScript/PDF
ii  ghostscript-x [gs-esp 8.62.dfsg.1-2      The GPL Ghostscript PostScript/PDF
ii  gs-esp                8.62.dfsg.1-2      Transitional package
ii  libavahi-compat-libdn 0.6.22-3           Avahi Apple Bonjour compatibility 
ii  libc6                 2.7-10             GNU C Library: Shared libraries
ii  libcupsimage2         1.3.7-5            Common UNIX Printing System(tm) - 
ii  libcupsys2            1.3.7-5            Common UNIX Printing System(tm) - 
ii  libdbus-1-3           1.2.1-1            simple interprocess messaging syst
ii  libgnutls26           2.2.2-1            the GNU TLS library - runtime libr
ii  libkrb53              1.6.dfsg.3~beta1-4 MIT Kerberos runtime libraries
ii  libldap-2.4-2         2.4.7-6.2          OpenLDAP libraries
ii  libpam0g              0.99.7.1-6         Pluggable Authentication Modules l
ii  libpaper1             1.1.23             library for handling paper charact
ii  libslp1               1.2.1-7.2          OpenSLP libraries
ii  lsb-base              3.2-10             Linux Standard Base 3.2 init scrip
ii  perl-modules          5.8.8-12           Core Perl modules
ii  procps                1:3.2.7-8          /proc file system utilities
ii  ssl-cert              1.0.18             simple debconf wrapper for OpenSSL
ii  xpdf-utils [poppler-u 3.02-1.3           Portable Document Format (PDF) sui

Versions of packages cupsys recommends:
ii  avahi-utils             0.6.22-3         Avahi browsing, publishing and dis
ii  cupsys-client           1.3.7-5          Common UNIX Printing System(tm) - 
ii  foomatic-filters        3.0.2-20080211-3 OpenPrinting printer support - fil
ii  smbclient               1:3.0.28a-2      a LanManager-like simple client fo

-- debconf information:
* cupsys/raw-print: true
* cupsys/backend: ipp, lpd, scsi, serial, socket, usb, snmp, dnssd



--- End Message ---
--- Begin Message ---
Jonathan Nieder wrote:

> Sorry for the long silence.  Could you attach a sample PDF that fails
> to print?  Even better would be a postscript file (from printing to
> postscript) that fails to print, if you can acquire one.

Apparently this had something to do with xpdf-utils?  Nowadays
xpdf-utils is a dummy package that pulls in poppler-utils.

Well, so goes the theory.  Unfortunately when this was reassigned
to ghostscript it was not rephrased as a ghostscript bug, and I
can't really see anything to do about it.  Plus it's from so long
ago, it's probably past the point of debuggability... so I'm giving
up and closing it.

Martin, Moshe, please reopen this if you have ideas for pursuing it
further.

Thanks,
Jonathan


--- End Message ---

Reply to: