On April 21, 2005 12:22, Ron Hunter-Duvar wrote: > On April 21, 2005 11:49, Rob Blomquist wrote: > > On Thursday 21 April 2005 8:50 am, Ron Hunter-Duvar wrote: ... > > Typically firefox and Acroread print around Kprinter, accessing the > > printer through lpr. > > > > So your problem is likely in kprinter. > > > > Have you inspected your logs for kernel messages, cups messages, and the > > like? > > > > Rob > > Ah, I didn't think to check the logs. I see that cups has it's own logs, > and the last few lines of /var/log/cups/error_log are: > > I [20/Apr/2005:15:11:04 -0600] Printer 'HPDeskJet990C' started by 'root'. > I [21/Apr/2005:09:14:31 -0600] Adding start banner page "none" to job 92. > I [21/Apr/2005:09:14:31 -0600] Adding end banner page "none" to job 92. > I [21/Apr/2005:09:14:31 -0600] Job 92 queued on 'HPDeskJet990C' by 'rhd'. > I [21/Apr/2005:09:14:31 -0600] Started filter /usr/lib/cups/filter/pstops > (PID 27159) for job 92. > I [21/Apr/2005:09:14:31 -0600] Started > filter /usr/lib/cups/filter/foomatic-rip (PID 27160) for job 92. > I [21/Apr/2005:09:14:31 -0600] Started backend /usr/lib/cups/backend/usb > (PID 27161) for job 92. > E [21/Apr/2005:09:15:04 -0600] PID 27160 stopped with status 3! > I [21/Apr/2005:09:15:04 -0600] Hint: Try setting the LogLevel to "debug" to > find out more. > > So, foomatic-rip error'ed out with status 3. Haven't found any > documentation on what this error code means (the man page just says that it > returns 0 unless something goes wrong - duh!). But at least it's a clue to > start investigating. Thanks.
Hmm, I printed the same email message from Kmail to a postcript file, print.ps, then did the following: foomatic-rip -P HPDeskJet990C print.ps | lpr -l This ran with no errors and printed all three pages of the email. I'm still invoking kprinter to generate the postscript file. I'm still sending it through foomatic-rip to convert it to raw (raster) printer input. I'm still sending it through cups (the lpr installed is just a compatibility layer on top of cups for old-style unix printing). The only difference is that instead instead of it all being done in a single pipe, I'm breaking the steps up. I still haven't been able to determine what error code 3 from foomatic-rip means. At least I've figured out a work-around. Where do I go from here? -- Ron ronhd at users dot sourceforge dot net Opinions expressed here are all mine. "As you know, necessity is the mother of invention. I don't know who the father is. Remorse, I guess." - Red Green
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
