Description of problem: Printing from evince to an HP LasertJet 4250 printer has the following result: * CUPS says the job has been successfully printed (e.g., status "completed") * make the printer to freeze (without actually printing anything), showing the message "Service Error". Version-Release number of selected component (if applicable): 2.26.2-1.fc11.x86_64 How reproducible: Steps to Reproduce: 1. Install the HP LaserJet 4250 with system-config-printer, using the "HP LaserJet 4250 Postscript (recommended)" driver 2. Download, for instance, this document: http://enterprise.amd.com/Downloads/Ziff_Power_and_Cooling_IT_.pdf 3. Open with evince: evince Ziff_Power_and_Cooling_IT_.pdf 4. Print to an HP LaserJet 4250 Actual results: No printed document and printer blocked, showing the "Service Error" message. Expected results: Printed document and printer ready to print another document. Additional info: I've tried with other documents and the problem remains. I've tried with an HP LaserJet 8000 and it works. I've tried to print that document with Acrobat Reader 9.1.3 and with "lp -d printer file" and it works Before installing F11 I had installed F10 and evince worked perfectly. The CUPS printer detail is: Description: HP LaserJet 4250 Driver: HP LaserJet 4250 Postscript (recommended) (grayscale, 2-sided printing) Connection: socket://###.###.###.###:9100 Defaults: job-sheets=none, none media=iso_a4_210x297mm sides=two-sided-short-edge My system is a Dell Latitude D830 with: Linux feedback 2.6.29.6-213.fc11.x86_64 #1 SMP Tue Jul 7 21:02:57 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
Marco: as well as trying another application that uses the GTK+ print dialog, it would be really useful if you could give us some diagnostic information: Start the printing troubleshooter: System->Administration->Printing, then Help->Troubleshoot. Follow the on-screen instructions. When it asks you to print a test page, start evince and print your Ziff PDF document. Continue following the instructions from the troubleshooter and you should end up with a file 'troubleshoot.txt' -- please attach that file to this bug report using the 'Add an attachment' link further up this page. One last thing: please attach the PPD file you are using, from the /etc/cups/ppd/ directory.
OK! I've tried to print with the following apps: * firefox-3.5.1-3.fc11.x86_64 * openoffice.org-impress-3.1.0-11.3.fc11.x86_64 * gedit-2.26.3-1.fc11.x86_64 And in all cases it worked! Then I've tried with evince and again the printer blocked (with the Service Error message). I attach the troubleshoot file and the PPD.
Created attachment 356278 [details] Print of Ziff PDF document with evince (troubleshoot file)
Created attachment 356279 [details] PPD of the HP LaserJet 4250 printer
IMHO the fix is for evince not to try to convert the document to PostScript but to send the print job as a PDF file directly. All CUPS queues accept application/pdf unless specifically configured not to (and why would you?), and this has been the case since we first shipped CUPS. CUPS converts to PostScript internally. In fact, there is talk (and some work done) of having the base job format move from application/postscript to application/pdf because PDFs are easier to manipulate. Many printers handle PDF natively anyway.
Created attachment 356287 [details] amd.pdf For completeness, here is a local copy of the PDF file in case the URL (or the document) changes.
For your info, I've asked to a collegue to print that PDF doc from the evince shipped with F10. And it worked. So the problem is *presumably* in the version of evince shipped with F11.
Under F12, it seems this problem has been solved.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. 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 '11'. 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 11'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 11 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.