When something does not print, I open the print job listing, click the icon for all jobs, and the print that did not come out was marked "aborted". When I go into the IPP report, it shows "aborted-by-system".
I looked in /var/log/cups and forwarded part of the log to a friend. He noticed
E [15/Jun/2004:19:26:23 -0400] Bad request line "request id is styluscolor640-103 (1 file(s))"!
and stated that data being sent to the filter is bad.
Since this is happening on two different systems, with different applications, I can only guess that it appears to be a Linux issue. I found updated CUPS drivers via YaST as part of a download of files pertaining to ghostscript, but the updated drivers did not solve this problem. The printer on the other system is an Epson Stylus Color 400. The printer referenced in the above quote is the Stylus Color 640. The 640 is capable of being connected either via USB or the parallel port, however the connection did not matter as it coocurred when it was connected to both types on different occasions.
Mozilla uses the LPR command to print, and I have not had aborted print jobs with that.
Does anyone have a clue as to why these print jobs are aborting?
Opera has an option to add in a printer command which when added, will appear in the Print window as a separate item.
When I add such an option, lpr -Pstyluscolor400 is the command sent to the printer. In this instance, the job does not appear in the print jobn listing mentioned above, but even with this, the first couple of print jobs will print, then nothing. It doesn't matter whether it is a web page, or an e-mail message.
The print system used is CUPS, and the driver used is CUPS+gimp_print.
Before I decide to go back to Windows permanently, is there anything that I should look at?