https://bugzilla.novell.com/show_bug.cgi?id=751889 https://bugzilla.novell.com/show_bug.cgi?id=751889#c3 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID Summary|cups fails to print large |Xerox Phaser 6280N fails to |images ... |print large color images in | |PostScript mode --- Comment #3 from Johannes Meixner 2012-03-13 09:35:53 UTC --- According to your var/log/cups/error_log -------------------------------------------------------------------------------- .. 21:18:50 ... [Job 167] File of type application/pdf queued by "michael". .. .. 21:18:50 ... envp[23]="PRINTER_INFO=Xerox Phaser 6280N" .. .. 21:18:50 ... Started filter /usr/lib/cups/filter/pdftops (PID 9356) .. 21:18:50 ... Started backend /usr/lib/cups/backend/ipp (PID 9357) .. .. 21:18:50 ... Started filter pdftops (PID 9359) .. 21:18:50 ... Started filter pstops (PID 9360) .. .. 21:24:56 ... PID 9359 (pdftops) exited with no errors. .. .. 21:24:56 ... PID 9360 (pstops) exited with no errors. .. 21:24:56 ... PID 9356 (/usr/lib/cups/filter/pdftops) exited with no errors. .. .. 21:24:56 ... PID 9357 (/usr/lib/cups/backend/ipp) exited with no errors. .. 21:24:56 ... [Job 167] Job completed. -------------------------------------------------------------------------------- nothing in CUPS fails to print your large images. But your var/log/cups/error_log shows that there is no driver program running (only conversion PDF->PostScript which is sent to the printer) which indicates that your use the Xerox Phaser 6280N as PostScript printer and your etc/cups/ppd/xerox.ppd proves that. Because your Xerox Phaser 6280N prints "normal" documents and images but only fails to print large images, it is a well know issue with PostScript printers that they fail to print too complex PostScript code or too big embedded images - usually simply because the PostScript printer runs out of memory, see "PostScript Printers" and "Potential Problems with PostScript Printers in http://en.opensuse.org/SDB:Purchasing_a_Printer_and_Compatibility and compare http://en.opensuse.org/SDB:Laser_Printer_Does_Not_Print_Properly_Or_Does_Not... The only real solution to print large color images in PostScript mode on a PostScript printer is to provide the printer with more memory. But even then it may take a longer time until the printer actually prints out large color images in PostScript mode - this depends mainly on the CPU speed in the printer. In your particular case the PDF->PostScript conversion might blow up the size of the images in PostScript - or perhaps the converion of your original images into PDF might already have blown up their size in PDF. If you have your images e.g. as JPEG files, try out if it works to print those files e.g. using lp -d xerox -o scaling=100 file.jpg see "Image Options" at http://www.cups.org/documentation.php/doc-1.5/options.html For fun you may experiment with special PostScript programs e.g. Google for "postscript raytracer" to get e.g. http://www.physics.uq.edu.au/people/foster/postscript.html where you can find in particular this URL http://www.physics.uq.edu.au/people/foster/ps/hayakawa_ray_c.ps Send it to your PostScript printer in "raw" mode e.g. using $ lp -d xerox -o raw hayakawa_ray_c.ps and wait how long your PostScript printer needs to print it compared to how long Ghostscript needs to display it via $ gs -r60 hayakawa_ray_c.ps On my computer Ghostscript needs only a few seconds for it but since several minutes my b/w PostScript printer HP LaserJet 1220 is still processing it... FYI: Usually in a PostScript printer you can switch on that it prints out PostScript errors if it fails to process PostScript so that you get a PostScript error printed in such cases so that you know that it was your printer which failed. Unfortunately those PostScript error printouts are usually disabled so that the user is not informed what went wrong. Of course it saves a lot of paper (and money) when the one sheet with the PostScript error is not printed and apparently it costs nothing when then users need a lot of time to find out why a particular document does not print... ;-) I do not say that the typcial PostScript error printout text is meaningful for normal users but at least they would know their printer somehow does not like their particular document. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.