Red Hat Bugzilla – Bug 827632
Printing PDF fails (although log says it's been ok), but postscript is ok
Last modified: 2013-02-13 18:54:23 EST
Created attachment 588593 [details]
cups error log for reference
Description of problem:
Printing from print dialog boxes fails, although print queue says job completed
Version-Release number of selected component (if applicable):
Linux localhost 3.3.6-3.fc16.x86_64 #1 SMP Wed May 16 21:43:01 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
"lpr output.ps" works fine as user and root.
Steps to Reproduce:
1. configure network printer Ricoh CL1000N post script printer in s-c-p
2. verify that test page works
3. open gedit, print file to printer, check queue
Print Queue says complete
log file in printer state: "The job was reset"
printout of text file from gedit (or any app)
The log is too big with too many jobs.
Would it be possible to attach only a respective parts of error log for successful (printing via lpr) and unsuccessful (printing from gedit) job.
Or even better to attach outputs from printing troubleshooter  for these two jobs. When it asks you to print test page, print something via lpr or from gedit as previously. Thanks !
Created attachment 589139 [details]
Output from S-C-P.
This is the output from the help part of S-C-P. The printout came out of the printer as expected. This was with the RAF10003.PPD driver.
Created attachment 589141 [details]
error log from lpr text file to printer setup in S-C-P - printing successful
This is the output from 'lpr testdocumentforprinting.txt' to the printer setup in S-C-P. This printout was successful. It printed as expected.
Created attachment 589142 [details]
error log from print dialog box in gedit to printer setup in S-C-P - printing failure
This is the output from error log when printing using the dialog box in gedit. I have tried several different apps, all the same result. Gedit was easiest. THis is a one line text file of "another test".
Well, I can't find anything stuffy in the unsuccessful print log. It seems perfectly ok.
Even comparing with the successful one doesn't reveal any significant difference. I have no idea what else could help us narrowing this problem down.
(In reply to comment #0)
> Actual results:
> Print Queue says complete
> log file in printer state: "The job was reset"
Where did you see this "The job was reset" message ?
I can't find anything like that anywhere.
Created attachment 589177 [details]
Screen shot of ricoh webserver on printer showing job was reset
The job was sent four times, and this screen shot is the error log on the printer showing that the job was reset.
Created attachment 589178 [details]
Screen shot of ricoh webserver on printer detailing job #4 of 4
Additional (although limited) information on the job was reset.
Does printing a pdf file with 'lpr file.pdf' succeed ?
lpr output.pdf - fails
lpr output.ps - succeeds
gedit text file used for this test. Print to file from dialog box in gedit. Printed to postscript (output.ps) and pdf (output.pdf)
On Ricoh printer - same error message:
Error Type : The job was reset.
Error Content : Job has been cancelled.
I changed the driver from the Ricoh CL1000N to the Generic postscript one, and the pdf file printed correctly (lpr output.pdf). That may be the short term workaround?
The original driver that wasn't working: RAF10003.PPD version 1.10 is now set to POSTSCRI.PPD version 1.1.
*** Bug 828301 has been marked as a duplicate of this bug. ***
I'm changing summary to better reflect what we know so far.
Bug #827490 could be another duplicate.
*** Bug 827490 has been marked as a duplicate of this bug. ***
So, if I understand it right the following chain
PDF file -> pdftops -> foomatic-rip -> postscript file
creates ps files that are incorrectly printed (or even not printed at all).
In case of this bug and bug #828301 nothing is printed out (even that error_log seems perfectly ok to me). In case of bug #827490 the output ps file looks ok in evince/okular but the printout has some errors (empty boxes instead of some characters).
But files created by
postscript file -> pstops -> foomatic-rip -> postscript file
chain are printed without any problems.
If my assumption is correct then we have the following components interested in this problem.
Note: the pdftops filter calls pdftops utility and pstops filter.
1) cups (/usr/lib/cups/filter/pdftops, /usr/lib/cups/filter/pstops)
2) poppler-utils (/usr/bin/pdftops)
3) foomatic (/usr/lib/cups/filter/foomatic-rip -> /bin/foomatic-rip)
4) ghostscript (/bin/gs)
So I'd suggest to downgrade these components ony by one and after each downgrade try to print a PDF file with 'lpr file.pdf'.
If the print succeeds then we know which version of which component makes this problem.
You could either user 'yum downgrade' or download the older builds from http://koji.fedoraproject.org/koji/.
I assume it's been caused by some update because you all filled the tickets at almost the same time and I don't remember any such report earlier.
But I can be wrong of course.
Created attachment 593265 [details]
Print To File output from gedit
If you print this file with "lp output.pdf", what happens?
This is the result of using "Print To File" from gedit, with US Letter portrait output.
Printing to File with gedit/evince is no problem for me. Using hpcups driver:
'HP LaserJet 3020 pcl3, hpcups 3.12.4' !
Dan Naughton: I'm particularly interested in your experience of the test in comment #19, using the driver that sometimes fails ('Ricoh Aficio CL1000N PS').
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '16'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 16's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 16 is 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" 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:
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.