FS#30306 - cups 1.5.3-5 printing regression with Brother HL-3070CW
Attached to Project:
Arch Linux
Opened by Jonathan Hudson (stronnag) - Friday, 15 June 2012, 17:16 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 22 July 2012, 14:30 GMT
Opened by Jonathan Hudson (stronnag) - Friday, 15 June 2012, 17:16 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 22 July 2012, 14:30 GMT
|
Details
Description:cups 1.5.3-5 printing regression with Brother
HL-3070CW
Additional info: * extra/cups 1.5.3-5 /cups-filters 1.0.18-2 extra/libcups 1.5.3-5 * Brother HL-3070CW BR-Script3 /usr/share/foomatic/db/source/PPD/Brother/BR3070_2_GPL.ppd.gz Steps to reproduce: Print a file (such as the attached). There are two options, either most of the text in the calendar part is missing (lp 2012-08.ps), or the image is "1980 dot matrix" resolution and general ugliness (including fuzzy text) (lp -oraw 2012-08.ps). The printer used to print beautifully prior to the recent cups 1.5.3 debacle (judging by the number of recent reports against cups). |
This task depends upon
Please let me know how I can help resolve this.
Any chance a generic driver is working better? Or maybe gutenprint.
The major change we made is now to use the pdf printing work flow introduced by cups-filter. Make also sure you have required
optional dependencies installed. Any better recommended ppd at linuxprinting.org?
I believe I have all the dependencies. The PPDs agree with latest at linuxprinting.org. Generic PS gives a blank page. Running
"foomatic-rip --debug -p /etc/cups/ppd/colour.ppd > /tmp/x.x 2> /tmp/foomatic-br3.log < 2012-08.ps"
reveals no errors. Baffled, older cups printed these DSC conformant file perfectly.
please get in contact with upstream devs (mainly printer guru Till Kampeter or cups mailing list).
Let me know if we are doing something wrong in our packages. Lately we introduced the full pdf printing workflow via cups-filters.
Thanks for the reminder. Since the last cups-filter update (1.0.19-1), I was delighted that a PDF of the format that failed previously printed perfectly (as does the example attached earlier to this bug report).
-jonathan