Lexmark 710 Pro cannot print from ePDF
Lexmark 710 Pro cannot print from ePDF
All,
This is odd, I get the following error in CUPS when I try to print from ePDF. Other document readers work.
This is on a Lexmark 710 Pro.
"/usr/lib/cups/filter/fax-pnh-filter failed"
Thanks in advance.
This is odd, I get the following error in CUPS when I try to print from ePDF. Other document readers work.
This is on a Lexmark 710 Pro.
"/usr/lib/cups/filter/fax-pnh-filter failed"
Thanks in advance.
Thanks for looking at this!
1. What Puppy version are you using?
Precise 5.6.1, though I confirmed this in Precise 5.5 with the same drivers
2. What printer driver package are you using?
I am using the Lexmark package for Ubuntu 12.04.
3. Where did you get the package? Provide a link.
http://support.lexmark.com:80/lexmark/i ... id=DR21222
4. Does the unit print a test page from CUPS?
Yes, full color. The issue comes in with PDF documents:
a. I cannot print from ePDF. Error above.
b. Adobe will print, but just one page at a time, I cannot insert a range.
c. FoxitPDF will work but it prints verry slow.
d. Other documents from libreoffice or leafpad work fine.
1. What Puppy version are you using?
Precise 5.6.1, though I confirmed this in Precise 5.5 with the same drivers
2. What printer driver package are you using?
I am using the Lexmark package for Ubuntu 12.04.
3. Where did you get the package? Provide a link.
http://support.lexmark.com:80/lexmark/i ... id=DR21222
4. Does the unit print a test page from CUPS?
Yes, full color. The issue comes in with PDF documents:
a. I cannot print from ePDF. Error above.
b. Adobe will print, but just one page at a time, I cannot insert a range.
c. FoxitPDF will work but it prints verry slow.
d. Other documents from libreoffice or leafpad work fine.
These Lexmark Debian packages are a nightmare. Since you haven't described how you installed it, it's difficult for me to comment.
As usual, your first source for printer drivers should have been here. It has a link to a whole page of Lexmark driver packages in PET form, some of which support your Pro710.
Your printer appears to be Postscript-capable. There is a section that discusses this.
As usual, your first source for printer drivers should have been here. It has a link to a whole page of Lexmark driver packages in PET form, some of which support your Pro710.
Your printer appears to be Postscript-capable. There is a section that discusses this.
For the Lexmark package I installed it as the default .deb from the site.
Interestingly enough, the Lexmark Valuewriter 300 - CUPS+Gutenprint v5.2.8-pre1 works fine with ePDF! I could not get the Pro700 drivers to print though.
I don't mind having 2 printers set up in CUPS, one for color/other utilities, another for B&W PDF.
I'm going to send a hate-mail to the lexmark folks to see what they say about the driver not liking PDF's.
Thanks for your (free) time and instant feedback.
Interestingly enough, the Lexmark Valuewriter 300 - CUPS+Gutenprint v5.2.8-pre1 works fine with ePDF! I could not get the Pro700 drivers to print though.
I don't mind having 2 printers set up in CUPS, one for color/other utilities, another for B&W PDF.
I'm going to send a hate-mail to the lexmark folks to see what they say about the driver not liking PDF's.
Thanks for your (free) time and instant feedback.
How did you install it? By clicking on the .deb? Then how did you install it in CUPS?Cadejo wrote:For the Lexmark package I installed it as the default .deb from the site.
The driver fails with ePDFview because it sees the print job in Postscript form and thinks that it is a fax job. Hence the error message. Modern Linux applications send their print jobs to CUPS in PDF form.
Did you try any of my suggestions?
That would be pointless. If you installed the driver in the environment for which it was designed, it would probably work.I'm going to send a hate-mail to the lexmark folks to see what they say about the driver not liking PDF's.
I see what you're asking now.
After installing the .Deb, the PPD's are automatically available to puppy on the CUPS model selection screen. I provided a snip.
I did try the Lexmark Pro700.pet package, but that did not work.
What you're saying makes sense.
Since it's an application-ism and not a driver issue I think that the issue is understood and the workaround is acceptable.
How'd you get so smart on printers? Everyone hates them.
Thanks!
After installing the .Deb, the PPD's are automatically available to puppy on the CUPS model selection screen. I provided a snip.
I did try the Lexmark Pro700.pet package, but that did not work.
What you're saying makes sense.
Since it's an application-ism and not a driver issue I think that the issue is understood and the workaround is acceptable.
How'd you get so smart on printers? Everyone hates them.
Thanks!
- Attachments
-
- Lexmarkcups.png
- (70.2 KiB) Downloaded 1097 times
Here is something to try.
1. Go to the folder /usr/share/ppd/Lexmark
2. Open the file Lexmark_Pro710_Series_Fax.ppd
3. Delete Line 95
4. Repeat with the file Lexmark_Pro710_Series_Postscript.ppd
5. Run CUPS and delete your current printer.
6. Add it again - choose the Fax model.
7. Test with a PDF.
1. Go to the folder /usr/share/ppd/Lexmark
2. Open the file Lexmark_Pro710_Series_Fax.ppd
3. Delete Line 95
Code: Select all
*cupsFilter: "application/vnd.cups-postscript 0 /usr/lib/cups/filter/fax-pnh-filter"
5. Run CUPS and delete your current printer.
6. Add it again - choose the Fax model.
7. Test with a PDF.
Excellent.Cadejo wrote:That fixed it.
Until recently, a print job came out of an application program as a stream of Postscript data. CUPS would look at the printer's PPD file for information about how to process that data.I have so many questions...
Usually, the data needs to be sent through various filters that convert the Postscript into a form compatible with your printer. That's why most printers require a driver package to be installed, like HPLIP for HP printers.
But some printers, like yours, are Postscript-compatible. So they can receive the data directly and print it.
But modern software sends the print job as a PDF. You can think of PDF as "Postscript on steroids". In your case, CUPS converts the PDF to Postscript and sends it to the printer. So you can print from most applications.
If the print job is still in Postscript, like with ePDFview, it should still work. But your PPD file has that line that you deleted. It acts as a switch that sends the print job to a dead-end. (This probably works correctly if you install the .deb in a "real" Linux.)
By deleting the line, the Postscript job flows correctly through the system to your printer.
BTW, you probably saw a non-Fax entry for your printer in CUPS. It sends the print job in a different direction through another filter. But it doesn't get installed properly in Puppy, so it fails.
Last edited by rcrsn51 on Wed 17 Jul 2013, 14:36, edited 1 time in total.