For some reason, when I try to print any graphic PDF (or a PS file made from said graphic), it kills my Minolta 1100 laser printer, and I have to cancel the job, disable the printer and turn the printer off and on as many times as it takes to clear its buffer of the trash.
I'm running CentOS 5.0 and have tried Adobe Acrobat Reader 7.0 for Linux; I have also tried printing the pdf to a file and running it straight through lpr, using the GIMP (although I've NEVER been able to print graphics from there), and even the Image Viewer (which chokes and dies silently while trying to load the file).
Any suggestions? I'm using the standard CUPS print system for all of this....
Thanks.
mhr
Mark Hull-Richter spake the following on 7/31/2007 6:19 PM:
For some reason, when I try to print any graphic PDF (or a PS file made from said graphic), it kills my Minolta 1100 laser printer, and I have to cancel the job, disable the printer and turn the printer off and on as many times as it takes to clear its buffer of the trash.
I'm running CentOS 5.0 and have tried Adobe Acrobat Reader 7.0 for Linux; I have also tried printing the pdf to a file and running it straight through lpr, using the GIMP (although I've NEVER been able to print graphics from there), and even the Image Viewer (which chokes and dies silently while trying to load the file).
Any suggestions? I'm using the standard CUPS print system for all of this....
Thanks.
mhr
Does the printer have enough memory to render a full page at whatever output resolution you are using?
Have you checked for driver up dates for the printer?? Could be the issue...
john
Scott Silva wrote:
Mark Hull-Richter spake the following on 7/31/2007 6:19 PM:
For some reason, when I try to print any graphic PDF (or a PS file made from said graphic), it kills my Minolta 1100 laser printer, and I have to cancel the job, disable the printer and turn the printer off and on as many times as it takes to clear its buffer of the trash.
I'm running CentOS 5.0 and have tried Adobe Acrobat Reader 7.0 for Linux; I have also tried printing the pdf to a file and running it straight through lpr, using the GIMP (although I've NEVER been able to print graphics from there), and even the Image Viewer (which chokes and dies silently while trying to load the file).
Any suggestions? I'm using the standard CUPS print system for all of this....
Thanks.
mhr
Does the printer have enough memory to render a full page at whatever output resolution you are using?
On 8/1/07, John Plemons john@mavin.com wrote:
Have you checked for driver up dates for the printer?? Could be the issue...
According to most of the sites I found in Google, the last update to the Linux printer driver was on August 12, 2004. I am using the latest RedHat drivers for RHEL 5.0 (repackaged as CentOS 5.0), which I am guessing contain the latest and greatest driver code available.
I am using the CUPS foomatic pclmono driver (the recommended driver) for this printer, and with the exception of graphics files (PDFs, PS from PDFs and anything from GIMP), everything prints just fine.
Since this does not appear to be a CentOS issue, I have also posted this in the gnome email list, although I'm not entirely sure that's the right place to ask, either.
Thanks - more suggestions welcome should any arise.
mhr
Mark Hull-Richter spake the following on 8/2/2007 9:53 AM:
On 8/1/07, John Plemons john@mavin.com wrote:
Have you checked for driver up dates for the printer?? Could be the issue...
According to most of the sites I found in Google, the last update to the Linux printer driver was on August 12, 2004. I am using the latest RedHat drivers for RHEL 5.0 (repackaged as CentOS 5.0), which I am guessing contain the latest and greatest driver code available.
I am using the CUPS foomatic pclmono driver (the recommended driver) for this printer, and with the exception of graphics files (PDFs, PS from PDFs and anything from GIMP), everything prints just fine.
Since this does not appear to be a CentOS issue, I have also posted this in the gnome email list, although I'm not entirely sure that's the right place to ask, either.
Thanks - more suggestions welcome should any arise.
mhr
Try a lower resolution as a test for a printer memory issue.
On 8/2/07, Scott Silva ssilva@sgvwater.com wrote:
Try a lower resolution as a test for a printer memory issue.
Same problem at 600dpi and 300dpi (lowest setting available).
Still, if that were the problem, would it not also occur when printing from a Wndows guest under VMWare to the same printer? It doesn't (or didn't when my VMWare was running ok).
mhr
Mark Hull-Richter spake the following on 8/2/2007 11:11 AM:
On 8/2/07, Scott Silva ssilva@sgvwater.com wrote:
Try a lower resolution as a test for a printer memory issue.
Same problem at 600dpi and 300dpi (lowest setting available).
Still, if that were the problem, would it not also occur when printing from a Wndows guest under VMWare to the same printer? It doesn't (or didn't when my VMWare was running ok).
mhr
It could have been that the windows driver sent the images compressed or some other optimizations. Open printing recommends the pxlmono driver. Maybe theirs is more up to date.
On 8/2/07, Scott Silva ssilva@sgvwater.com wrote:
It could have been that the windows driver sent the images compressed or some other optimizations. Open printing recommends the pxlmono driver. Maybe theirs is more up to date.
That's the one I'm using....
Thanks.
mhr
On Thu, Aug 02, 2007 at 02:18:41PM -0700, Mark Hull-Richter wrote:
On 8/2/07, Scott Silva ssilva@sgvwater.com wrote:
It could have been that the windows driver sent the images compressed or some other optimizations. Open printing recommends the pxlmono driver. Maybe theirs is more up to date.
That's the one I'm using....
I missed earlier postings in this thread, so please allow me to ask: Areyou trying to print with (e.g.) Acroread, or are you trying to print using "lpr foo.pdf"? Does either (or neither) work?
On 8/2/07, fredex fredex@fcshome.stoneham.ma.us wrote:
I missed earlier postings in this thread, so please allow me to ask: Areyou trying to print with (e.g.) Acroread, or are you trying to print using "lpr foo.pdf"? Does either (or neither) work?
I would be amazed if the lpr command worked - never tried it. Printing directly from Acroread....
mhr
On Fri, Aug 03, 2007 at 10:32:30AM -0700, Mark Hull-Richter wrote:
On 8/2/07, fredex fredex@fcshome.stoneham.ma.us wrote:
I missed earlier postings in this thread, so please allow me to ask: Areyou trying to print with (e.g.) Acroread, or are you trying to print using "lpr foo.pdf"? Does either (or neither) work?
I would be amazed if the lpr command worked - never tried it. Printing directly from Acroread....
At the time I posted that, I tried it from the commandline just to make sure it did work (as I had believed it would but had never before tried), and sure enough it printed just fine.
Note that I'm using Centos 4.5, if that makes any difference.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Mark Hull-Richter Sent: Thursday, August 02, 2007 12:53 PM To: CentOS mailing list Subject: Re: [CentOS] Re: Can't print PDFs or PSs in CentOS 5.0
On 8/1/07, John Plemons john@mavin.com wrote:
Have you checked for driver up dates for the printer??
Could be the issue...
According to most of the sites I found in Google, the last update to the Linux printer driver was on August 12, 2004. I am using the latest RedHat drivers for RHEL 5.0 (repackaged as CentOS 5.0), which I am guessing contain the latest and greatest driver code available.
I am using the CUPS foomatic pclmono driver (the recommended driver) for this printer, and with the exception of graphics files (PDFs, PS from PDFs and anything from GIMP), everything prints just fine.
Since this does not appear to be a CentOS issue, I have also posted this in the gnome email list, although I'm not entirely sure that's the right place to ask, either.
Thanks - more suggestions welcome should any arise.
By the looks of it it appears to be a problem with printing postscript.
Is the ghostscript package and it's fonts properly installed?
If you enscript a text file and print it does it come out ok?
-Ross
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.
On 8/2/07, Ross S. W. Walker rwalker@medallion.com wrote:
By the looks of it it appears to be a problem with printing postscript.
Is the ghostscript package and it's fonts properly installed?
Here's what I show (that I know to looks for, although I presume that if this shows, other dependencies must have been resolved since I use yum for virtually all installations):
$ rpm -qa | grep ghost ghostscript-8.15.2-9.1.el5.x86_64 ghostscript-fonts-5.50-13.1.1.noarch ghostscript-8.15.2-9.1.el5.i386
If you enscript a text file and print it does it come out ok?
Not quite sure how to do this, but here's what I did:
Used gedit to create a pdf of a text file, then AR to print it - fine. Used AR to create a ps file from the pdf, then printed it - fine. Used gedit to print to the generic postscript printer (lpr) and - came out fine.
Text is not a problem, just something about these graphic pdfs (and any graphics file from the GIMP). Note that the image viewer prints jpeg graphics just fine, too.
Thanks again.
mhr
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Mark Hull-Richter Sent: Thursday, August 02, 2007 5:44 PM To: CentOS mailing list Subject: Re: [CentOS] Re: Can't print PDFs or PSs in CentOS 5.0
On 8/2/07, Ross S. W. Walker rwalker@medallion.com wrote:
By the looks of it it appears to be a problem with printing
postscript.
Is the ghostscript package and it's fonts properly installed?
Here's what I show (that I know to looks for, although I presume that if this shows, other dependencies must have been resolved since I use yum for virtually all installations):
$ rpm -qa | grep ghost ghostscript-8.15.2-9.1.el5.x86_64 ghostscript-fonts-5.50-13.1.1.noarch ghostscript-8.15.2-9.1.el5.i386
If you enscript a text file and print it does it come out ok?
Not quite sure how to do this, but here's what I did:
Used gedit to create a pdf of a text file, then AR to print it - fine. Used AR to create a ps file from the pdf, then printed it - fine. Used gedit to print to the generic postscript printer (lpr) and - came out fine.
Text is not a problem, just something about these graphic pdfs (and any graphics file from the GIMP). Note that the image viewer prints jpeg graphics just fine, too.
Ok, so it's not a general postscript failure, but maybe just EPS...
If the printer needs a hard-reset to recover then it is probably because the printer isn't fully PCL compatible as it advertises, can you try using an HP Deskjet engine which does PCL 3?
-Ross
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.
On 8/2/07, Ross S. W. Walker rwalker@medallion.com wrote:
Ok, so it's not a general postscript failure, but maybe just EPS...
EPS?
If the printer needs a hard-reset to recover then it is probably because the printer isn't fully PCL compatible as it advertises, can you try using an HP Deskjet engine which does PCL 3?
It usually takes two or three power cycles to get the printer to quit being stupid about it (so to speak). I also have to cancel the print job (of course).
I'm not sure how to do what you suggest here. In AR on the 'print' window, there are a few options I've tried differently. The default is optimize for speed and use level 2 (I'm guessing that's PCL level 2). I've tried setting it to 'save printer memory' and 'use level 3', neither of which works.
What usually happens is that the green light on the printer flashes for a few seconds, indicating that it is processing the file, then the red light goes on steady (I don't know how to retrieve the printer status on Linux, and it only worked sporadically on Windows when I used that, but I never saw this particular problem there...).
I've only been able to find a paucity of information about this (or any) printer under Linux/CentOS - I've used lpstat, the (gnome) printer administration tool, and occasionally the CUPS interface - what am I looking for so that I can tell what/how to change it?
Thanks.
mhr
On Thu, August 2, 2007 6:02 pm, Mark Hull-Richter wrote:
On 8/2/07, Ross S. W. Walker rwalker@medallion.com wrote:
Ok, so it's not a general postscript failure, but maybe just EPS...
EPS?
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Mark Hull-Richter Sent: Thursday, August 02, 2007 6:02 PM To: CentOS mailing list Subject: Re: [CentOS] Re: Can't print PDFs or PSs in CentOS 5.0
On 8/2/07, Ross S. W. Walker rwalker@medallion.com wrote:
Ok, so it's not a general postscript failure, but maybe just EPS...
EPS?
As the other poster pointed out it encapsulated postscript, a lot of bitmaps are bound in an encapsulating postscript object wrapped in a postscript object for printing.
If the printer needs a hard-reset to recover then it is probably because the printer isn't fully PCL compatible as it advertises, can you try using an HP Deskjet engine which does PCL 3?
It usually takes two or three power cycles to get the printer to quit being stupid about it (so to speak). I also have to cancel the print job (of course).
If you kill the job first then power cycle the printer it could be done in 1 I bet, otherwise the job keeps pumping output to the printer and you get a ton of garbage.
I'm not sure how to do what you suggest here. In AR on the 'print' window, there are a few options I've tried differently. The default is optimize for speed and use level 2 (I'm guessing that's PCL level 2). I've tried setting it to 'save printer memory' and 'use level 3', neither of which works.
Not in reader, but down at the CUPS setup when you setup your printer originally you probably chose a model from the foomatic database that was close-enough, go back and change that model to HP Deskjet which should provide the lowest level of PCL support that almost all PCL compatible printers should support. If that works then try an HP LaserJet 4 next, if that works then you have a good fall-back.
The levels in AR correspond to PostScript levels and not PCL, I think it's a PCL compatibility issue that your hitting here.
You can also scan the Internet to see if someone has put together a working CUPS PPD (different PPD than the standard postscript printer definition) file for your particular model.
What usually happens is that the green light on the printer flashes for a few seconds, indicating that it is processing the file, then the red light goes on steady (I don't know how to retrieve the printer status on Linux, and it only worked sporadically on Windows when I used that, but I never saw this particular problem there...).
I've only been able to find a paucity of information about this (or any) printer under Linux/CentOS - I've used lpstat, the (gnome) printer administration tool, and occasionally the CUPS interface - what am I looking for so that I can tell what/how to change it?
Well I think printer status is communicated through hal/dbus and cups, but if the printer blinks red that's a sure sign that things are not good.
-Ross
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.
On Fri, 2007-08-03 at 00:15 -0400, Ross S. W. Walker wrote:
Not in reader, but down at the CUPS setup when you setup your printer originally you probably chose a model from the foomatic database that was close-enough, go back and change that model to HP Deskjet which should provide the lowest level of PCL support that almost all PCL compatible printers should support. If that works then try an HP LaserJet 4 next, if that works then you have a good fall-back.
Interesting. I set it to be an HP Deskjet, and it almost worked (clipped a little at the top and bottom of the image). Then I set it for the Minolta HP Laserjet 4d PPD, and that worked. There are some other Minolta drivers that look promising, so I'll play around with it and see what happens.
Many, many thanks!
mhr
One other thing, printer settings, and also is it only with this PDF file, or all?? If it is just this PDF then it could be a bad conversion...
john
Scott Silva wrote:
Mark Hull-Richter spake the following on 7/31/2007 6:19 PM:
For some reason, when I try to print any graphic PDF (or a PS file made from said graphic), it kills my Minolta 1100 laser printer, and I have to cancel the job, disable the printer and turn the printer off and on as many times as it takes to clear its buffer of the trash.
I'm running CentOS 5.0 and have tried Adobe Acrobat Reader 7.0 for Linux; I have also tried printing the pdf to a file and running it straight through lpr, using the GIMP (although I've NEVER been able to print graphics from there), and even the Image Viewer (which chokes and dies silently while trying to load the file).
Any suggestions? I'm using the standard CUPS print system for all of this....
Thanks.
mhr
Does the printer have enough memory to render a full page at whatever output resolution you are using?
On 8/1/07, John Plemons john@mavin.com wrote:
One other thing, printer settings, and also is it only with this PDF file, or all?? If it is just this PDF then it could be a bad conversion...
john
Scott Silva wrote: Mark Hull-Richter spake the following on 7/31/2007 6:19 PM:
:>
mhr
Does the printer have enough memory to render a full page at whatever outputresolution you are using?
This looks to me like an excellent example of why top-posting does not work (and is deprecated in this mailing list)
However, to answer the question, I'm not sure which printer settings would be affected here, but the problem is primarily restricted to graphical PDFs - those that are all or mostly text print just fine.
Also, as a rule, when my VMWare Windows guest was working, I would routinely go there to print the files from the Windows Acrobat Reader (version 8 I think) with no trouble at all.
mhr
On 8/1/07, Scott Silva ssilva@sgvwater.com wrote:
Does the printer have enough memory to render a full page at whatever output resolution you are using?
Ithas 4MB on board memory. The PDFs I have been unable to print range from 1/2MB to 3MB, none larger, but I'm not sure that answers the question.
mhr
-
fredex -
John Plemons -
Mark Hull-Richter -
Marko A. Jennings -
Ross S. W. Walker -
Scott Silva