FS#47695 - [cups] pxlcolor driver just outputs plain text

Attached to Project: Arch Linux
Opened by Elmar Stellnberger (estellnb) - Sunday, 10 January 2016, 13:15 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 11 December 2019, 14:49 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When I try to print with my Brother MFC-9840CDW either via the pxcolor driver or via the postscript driver I get plain text output on the printer rather than a test page as expected;
pxlcolor: https://bugs.launchpad.net/ubuntu/+source/foomatic-db/+bug/1529690
postscript: https://bugs.launchpad.net/ubuntu/+source/foomatic-db/+bug/1529687
The last time when I have printed with these drivers under Ubunutu no such error ocurred. Finally I have tried it with the printer drivers directly supplied via solutions.brother.com/linux with exactly the same result: they print well under Mageia but just give unwanted text output when used with Arch Linux.
Besides this I do also still have to start cups by invoking the cupsd executable directly from a command line rather than being able to configure its startup via systemctl enable/start.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Wednesday, 11 December 2019, 14:49 GMT
Reason for closing:  No response
Comment by Elmar Stellnberger (estellnb) - Wednesday, 13 January 2016, 15:18 GMT
Well, the CUPS v1.1 driver as provided by Brother works in deed though it has never been packaged for Arch and though sources are not public for the lpr driver it requires (sorry for having indicated test results wrongly for the proprietary driver; it works with a bit of fine tuning). Consequently I would regard this bug as to be resolved upstreams. It can be inferenced that there is no configuration issue with CUPS but a driver issue with both the pxlcolor and the postscript driver.
Comment by Andreas Radke (AndyRTR) - Tuesday, 10 December 2019, 09:38 GMT
Has this been fixed with all the updates?

Loading...