Red Hat Bugzilla – Bug 1248765
Cannot Print on Different Papers
Last modified: 2016-12-23 05:44:09 EST
Created attachment 1057826 [details]
Output from printer troubleshooter in system-config-printer
Description of problem:
I have a Brother MFC-J6520DW, purchased because they supplied a Linux driver. Everything worked well until Fedora 22. Since then I cannot select any paper type other than Plain Paper in the printer options, even if I have selected the same paper type on the printer.
When using any other paper type than plain the driver reports everything has completed but the printer does not print, complaining about data remaining in memory, eventually a blank page is ejected. The print troubleshooter does recognise that the print was unsuccessful!
If you use plain paper then the print is fine.
I have attached the output from the troubleshooter.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Print a document on something other than plain paper
A blank page
A printed document
I have reported this to brother who (naturally) say it is an "OS problem"
(In reply to Paul Finnigan from comment #0)
> I have a Brother MFC-J6520DW, purchased because they supplied a Linux driver.
I don't see this printer in http://www.openprinting.org/printers database so I guess you're using the driver directly from Brother, right ?
Could you try to obtain some more log messages via
> If you use plain paper then the print is fine.
Setting Severity to urgent can actually have opposite effect in that case ;-)
(/me couldn't resist to nitpick)
Created attachment 1058159 [details]
Output from journalctl -u cups.service -b 0
Created attachment 1058161 [details]
Print on Plain Paper
Created attachment 1058162 [details]
Print on Inkjet Paper
Created attachment 1058163 [details]
Command output - commands are shown before oputput in file
First I am using a printer driver provided by Brother. This has worked on previous releases of Fedora (20 and 21) without problems, I am not claiming that this stops the driver is at fault I just mention that it is a new problem.
I have attached the logs suggested by the debugging printer problems page. I have shown the output from the last boot (I rebooted for the tests). I printed the same page from LibreOffice 4 times using:
Job 116 - "Plain Paper" - printed OK
Job 117 - "Inkjet Paper" - blank page printed
Job 118 - "Other Photo Paper" - blank page printed
Job 119 - "Plain Paper" - printed OK
I have only included the logs for the first two jobs. If you want the others then let me know.
I can also tell you that the same problem occurs when printing from the Gimp and Eye of Gnome Image Viewer. My printer can connect via USB, Ethernet or wireless. I currently don't have it connected on Ethernet as I have no free ports but the same problem occurs via wireless or USB. The examples are via wireless. I also have the problem on two Fedora systems that I use with the printer.
As to the urgent flag, it was a typo. I thought I had put high. I could do with getting this fixed in the next few weeks if possible as I need to produce some presentations on glossy paper for mid-August.
I can always use a fallback, print it using my Android phone which works but misses out on the use of icc profiles. So perhaps even high was a little OTT. I will think before I select this in future.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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
Thank you for reporting this bug and we are sorry it could not be fixed.
The problem also happens on Fedora 23 and Fedora 24.
This problem has been outstanding since F22 but appears to be fixed in F25.
The brother (non-open) driver has not been altered.
The working configuration uses
As far as I am concerned the problem can be closed as fixed in F25. However the maintainers may like to look at the differences in version 1:2.0 to 1:2.2 to see what may have caused the problems.
thanks for letting me know. Closing as CURRENTRELEASE. I will look into it.