Hide Forgot
Description of problem: 1) Printing to ricoh aficio CL3000 direct from any application that uses the gtk print dialog seems to fail, such as inkscape or gedit. 2) evince won't print any pdf files on disk. 3) evince will print black and white ps files from disk (created from print dialog in other applications). 4) Printing from Libreoffice appears to work as expected. Color output direct to printer as expected. 5) "Print Test page" and "Print Self-Test Page" from system-config-printer dialog work. Version-Release number of selected component (if applicable): cups-1.4.8-5.fc15.x86_64 gtk3-3.0.12-1.fc15.x86_64 Seems to impact F16 beta as well, But my day to day machine at work is F15 still so its easier for me to test that for bug follow through.
Please attach the PPD for the queue (from the /etc/cups/ppd/ directory). Additionally it would be useful to have the troubleshooting report: https://fedoraproject.org/wiki/Printing/Debugging#Printing_troubleshooter
Created attachment 530136 [details] ppd file for impacted printer Ricoh-Aficio-CL3000.ppd as generated by system-config-printer
Created attachment 530137 [details] cups error log showing PDF and PS job /var/log/cups/error_log error_log should capture a failed attempt to print a 2 page pdf from evince as job 109 followed by a successful print of a 2 page ps file from evince as job 110.
The log shows what looks to be a normal job transfer for job 109. If you print the same PDF from the command line, does that also fail? What is the nature of the failure -- how does the printer behave? lp -d Ricoh-Aficio-CL3000 spaleta20110603145917.pdf
pdf commandline also fails. Printer wakes up. Data-in LED on printer front panel lights up. But no printing.
Are you able to attach the PDF?
not that one. but tomorrow I create a new one that I can attach. Its pretty much every pdf I throw at it with this particular printer. -jef
Created attachment 530591 [details] Test PDF that won't print to the Aficio-CL3000 printer So here's a simple PDF. This one prints to other printers I have access to without issue. But not to the Aficio-CL3000. Postscript version of the same document prints without issue. Printer's incoming data LED lights up, printer makes noises like its waking up and preparing to print. But no printing. Also note that printing from a work colleague's windows 7 machine prints pdf without issue.
Please run these commands (copy and paste into a terminal) ==> PPD=/etc/cups/ppd/Ricoh-Aficio-CL3000.ppd \ /usr/lib/cups/filter/pdftops 1 me '' 1 '' \ test_document.pdf > pdftops.ps lp -dRicoh-Aficio-CL3000 -oraw pdftops.ps <== Does that give a correct print-out?
No print out. Same behavior I see the printer data led blink but no print. pdftops.ps file generated from the first command opens in evince without issue. but will not print from evince. Now if I print to pdftops.ps from evince to pdftopstoimevince.ps this file does not print either. I'm attaching a zip with four version of the same file. test_document.pdf : original pdf test_document.ps : ps generated using evince print to ps file dialog pdftops.ps : generated via the filter command in Comment 9 pdftopstopsinevince.ps : generated from evince Out of the four only test_document.ps prints to this printer. -jef
Created attachment 530702 [details] zip with multiple generated test document files.
Created attachment 532287 [details] Ricoh-Aficio-CL3000-PS2.ppd The one that works for you is PostScript level 2; the one that fails is PostScript level 3. Please try creating a new queue from this modified PPD, which claims only PostScript level 2 support. Does that fare any better?
No Joy. Repeating the commandline test from Comment 9 using PPD="/path/to/Ricoh-Aficio-CL3000-PS2.ppd" still results in a lack of printing. command: file pdftops.ps give: pdftops.ps: PostScript document text conforming DSC level 3.0, Level 2 confirming the new PPD was used and produced a level 2 document but still no joy printing it. And creating a printer entry via system-config-printer and selecting the new ppd manually is also a no joy situation. The mystery continues. -jef
This may be an SELINUX problem. Please see this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=804304 I found this out by starting Evince from a terminal as sudo evince. An ABRT error window popped up when I tried to print. When I followed the instructions in that report, the document printed. A subsequent test with evince as a regular user also succeeded where it had continually failed before.
Stephen: thanks, but bug #804304 is not related.
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