Hide Forgot
Created attachment 530332 [details] Output from system-config-printer as directed by How_to_debug_printing_problems Description of problem: Trying to print a PDF file over the net just gets me: $ lpq dcsc is ready and printing Rank Owner Job File(s) Total Size active vonbran 275 propuesta1.pdf 97280 bytes There it stays, the file isn't printed and no change in status is reported either. Printer properties: Device URI: hp:/net/HP_LaserJet_M1522nf_MFP?ip=200.1.21.56 Make and model: HP LaserJet m1522nf MFP pcl3, hpcups 3.11.7 Version-Release number of selected component (if applicable): cups-1.4.8-5.fc15.x86_64 hplip-3.11.7-2.fc15.x86_64 How reproducible: Always Steps to Reproduce: 1. lpr propuesta1.pdf 2. 3. Actual results: Nothing printed out, lpq(1) reports "ready and printing," which is a lie (O, it is ready but doesn't print). The objectionable file is one page. Expected results: Additional info: # lpinfo -l -v Device: uri = socket class = network info = AppSocket/HP JetDirect make-and-model = Unknown device-id = location = Device: uri = cups-pdf:/ class = file info = CUPS-PDF make-and-model = Virtual PDF Printer device-id = MFG:Generic;MDL:CUPS-PDF Printer;DES:Generic CUPS-PDF Printer;CLS:PRINTER;CMD:POSTSCRIPT; location = Device: uri = ipp class = network info = Internet Printing Protocol (ipp) make-and-model = Unknown device-id = location = Device: uri = smb class = network info = Windows Printer via SAMBA make-and-model = Unknown device-id = location = Device: uri = https class = network info = Internet Printing Protocol (https) make-and-model = Unknown device-id = location = Device: uri = lpd class = network info = LPD/LPR Host or Printer make-and-model = Unknown device-id = location = Device: uri = scsi class = direct info = SCSI Printer make-and-model = Unknown device-id = location = Device: uri = http class = network info = Internet Printing Protocol (http) make-and-model = Unknown device-id = location = Device: uri = beh class = network info = Backend Error Handler make-and-model = Unknown device-id = location = Device: uri = hp class = direct info = HP Printer (HPLIP) make-and-model = Unknown device-id = location = Device: uri = hpfax class = direct info = HP Fax (HPLIP) make-and-model = Unknown device-id = location =
Forget to mention that I also tried to print from oowriter, also "Ready and printing" but nothing. Converted to PS, prints fine: $ pdf2ps propuesta1.pdf lpr propuesta1.ps poppler-0.16.7-1.fc15.x86_64, installed in July (and it used to work).
This looks like the problem: D [26/Oct/2011:13:25:32 -0300] [Job 275] Error: /syntaxerror in (binary token, type=156) If you convert the file using pdftops (not pdf2ps), and then view it using gs, do you get the same error? Are you able to attach that PDF file?
(In reply to comment #2) > This looks like the problem: > > D [26/Oct/2011:13:25:32 -0300] [Job 275] Error: /syntaxerror in (binary token, > type=156) > > If you convert the file using pdftops (not pdf2ps), and then view it using gs, > do you get the same error? Are you able to attach that PDF file? $ gs propuesta1.ps GPL Ghostscript 9.04 (2011-08-05) Copyright (C) 2011 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Error: /syntaxerror in (binary token, type=156) Operand stack: Encoding --nostringval-- --nostringval-- 166 - 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 Dictionary stack: --dict:1153/1684(ro)(G)-- --dict:0/20(G)-- --dict:78/200(L)-- --dict:67/75(L)-- --dict:5/10(L)-- Current allocation mode is local GPL Ghostscript 9.04: Unrecoverable error, exit code 1
Created attachment 530482 [details] The offending PDF file
ghostscript-9.04-3.fc15.x86_64 poppler-utils-0.16.7-1.fc15.x86_64
$ pdftops propuesta1.pdf $ gs propuesta1.ps PL Ghostscript 9.04 (2011-08-05) Copyright (C) 2011 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Error: /syntaxerror in (binary token, type=156) Operand stack: Encoding --nostringval-- --nostringval-- 166 - 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 Dictionary stack: --dict:1153/1684(ro)(G)-- --dict:0/20(G)-- --dict:78/200(L)-- --dict:67/75(L)-- --dict:5/10(L)-- Current allocation mode is local GPL Ghostscript 9.04: Unrecoverable error, exit code 1 It's because of this sort of thing: dup 164 /currency put dup 165 /yen put dup 166 /-ù<9c>wµÔ<83> put dup 167 /-ù<9c>wµÔ<83> put dup 168 /-ù<9c>wµÔ<83> put dup 169 /-ù<9c>wµÔ<83> put dup 170 /-ù<9c>wµÔ<83> put dup 171 /-ù<9c>wµÔ<83> put dup 172 /-ù<9c>wµÔ<83> put Looks like a poppler bug.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping