Created attachment 891672 [details] troubleshooter output from printing test page Description of problem: When I try to print a certain document, the printer clicks, the green lignt may flash a few times, then the jobs disappears from the job queue with nothing accomplished. Version-Release number of selected component (if applicable): cups-1.7.2-1.fc20.x86_64 evince-3.10.3-1.fc20.x86_64 How reproducible: Every time. Test page printed OK. Steps to Reproduce: 1. Open Print settings and use Help to initiate Troubleshooting mode 2. Select printer, Brother HL2270DW 3. Use evince to put document in print queue 4. While document is in queue, mark it for Troubleshooter Actual results: No printinr Expected results: Normal printing. When printing, I'd also like to see progress information. Additional info:
Created attachment 891673 [details] toubleshooter while printing document
Created attachment 891674 [details] pdf triggering the problem
(In reply to Peter H. Jones from comment #1) > toubleshooter while printing document [Job 78] Started filter /usr/lib/cups/filter/pdftopdf (PID 5776)', [Job 78] Started filter /usr/lib/cups/filter/pdftops (PID 5777)', [Job 78] Started filter /usr/lib/cups/filter/brlpdwrapperHL2280DW (PID 5778)', [Job 78] Started backend /usr/lib/cups/backend/usb (PID 5779)', [Job 78] Switching to Poppler's pdftops instead of Ghostscript for Brother ... I tried to print the document on postscript printer using the Poppler's pdftops renderer and it printed correctly so I think the Brother's brlpdwrapperHL2280DW filter has problems with the Poppler's generated postscript. You can try to use ghostscript as pdftops renderer with: # lpadmin -p Brother-HL-2270DW-A-UQAM -o pdftops-renderer-default=gs Then return to default with: # lpadmin -p Brother-HL-2270DW-A-UQAM -R pdftops-renderer-default Can you attach /etc/cups/ppd/Brother-HL-2270DW-A-UQAM.ppd and tell me where you got it ?
I installed the drivers from Brother's download page at http://support.brother.com/g/b/downloadlist.aspx?c=us&lang=en&prod=hl2270dw_all&os=127 . To be specific, I have: -rw-rw-r--. 1 jones 14576 Feb 7 2013 cupswrapperHL2270DW-2.0.4-2.i386.rpm -rw-rw-r--. 1 jones 37748 Feb 7 2013 hl2270dwlpr-2.1.0-1.i386.rpm And md5sum *2270* gives me: 5a7cc60cafaf60d722d9bce3f2751164 cupswrapperHL2270DW-2.0.4-2.i386.rpm 69c1987c0636a64fb48f3c6826a3ae28 hl2270dwlpr-2.1.0-1.i386.rpm The file appears to be generated by a script at /usr/local/Brother/Printer/HL2270DW/cupswrapper/cupswrapperHL2270DW-2.0.4 , which is part of the first RPM. I seemed to have to install these drivers in order to have the printer recognized. Perhaps this is no longer true.
I was able print the document with the first command given in comment 3. The job in the "Processing" state for about 3 minutes. As the machine was heavily loaded, I would have found it reassuring to see a progress indicator indicating the job wasn't hung, or perhaps wating for something like fresh paper. I then entered the second command, and the document still printed. I wonder why, for I expected a failure.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.