Comment 95 for bug 419143
Revision history for this message
| Adrian Johnson (ajohnson-redneon) wrote Re: Printing from evince (and perhaps other GTK apps) to PostScript printers is broken | #95 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
> Are the upstream developers of Cairo also aware that the fix does not solve the problem in all situations?
No. Probably because it is a different bug.
If you think you've found a cairo printing bug I suggest the following:
1. First show that the PDF fails to print when cairo is part of the printing pipeline but prints correctly when cairo is not involved:
a) Check that using poppler to generate the PostScript then sending the PS file directly to the printer bypassing any cups filters works:
pdftops file.pdf
lpr -o raw file.ps
b) Then use cairo to convert the PDF to PS. This can be done by opening the file in evince and printing to a PS file. Print with "lpr -o raw". If this fails but (a) works it is a cairo bug.
c) Alternatively you can use evince to print to PDF then use pdftops to convert to PS. If this fails to print but (a) works it is a cairo bug.
2. Either report the bug on cairo bugzilla, send mail to the cairo list, contact me on #cairo or cc me on the Ubuntu bug.
3. Unless the bug can be reproduced on a LaserJet 4050, chances are I can't reproduce it as I don't have the same printer. So you will have to help me debug it. You can do this by:
a) Find the smallest simplest PDF file that reproduces the problem. Find which page it fails on and provide me with the cairo generated PS that fails and the poppler PS that works for that page and the printer error message.
b) Identify any patterns. Does it fail for every page in the PDF? Does it only fail on pages with images or certain fonts?
c) Find other PDFs that fail the same way. Look for patterns. Are they from the same PDF creator? Are they using the same font?