Followup to myself, but directed to James or anyone else with a clue (since 
I'm definitely lacking one here :).

While looking at /usr/lib/cups/filter/cupsomatic, I descovered that it has 
a debug option that writes tons of stuff to an output file.  I tried 
running another "test printer" function from within KUPS, and the last 
entries in the trace file said this:

Printer escp2-c80 is not a known model
Printer escp2-c80 is not a known model
**** Unable to open the initial device, quitting

Ok, so how come KUPS (and the "printers" option under the "system" part of 
the tree in control-panel) can figure out what the printer is, but when a 
job is passed off to CUPS itself, it doesn't know what the printer is?  How 
do I go about giving CUPS the information that it needs??

                --Dave

David Guntner grabbed a keyboard and wrote:
>
> James grabbed a keyboard and wrote:
> >
> > On Thu, 7 Feb 2002 11:42:30 -0800
> > "David Guntner" <[EMAIL PROTECTED]> wrote:
> > 
> > > > > There may also be a CUPS error log somewhere.  Look in /var/log  or 
> > > > > /var/spool/<cups or lpd>.
> > > 
> > > I did find /var/spool/cups, which had a error_log file in it.  I checked
> > 
> > > that, and found the following entries from when I told KUPS to send a
> > > test  print to the printer:
> > > 
> > > I [time] Job 10 queued on 'lp' by 'root'.
> > > I [time] Started filter /usr/lib/cups/filter/pstops (PID 4888) for job
> > 10.
> > > I [time] Started filter /usr/lib/cups/filter/cupsomatic (PID 4889)
> > >   for job 10.
> > > I [time] Started backend /usr/lib/cups/backend/parallel (PID 4890)
> > >   for job 10.
> > > E [time] PID 4889 stopped with status 32!
> > > 
> > > (Where I have "[time]" is where the timestamp appeared in the log.  But 
> > > since I'm typing this by hand, I figured that the timestamp wasn't that 
> > > important. :-)  I'm indenting where something was actually part of the
> > > line that's before it, since my mail program was wrapping in a way which
> > > might have made it harder to follow.)
> > > 
> > > That last line seems to indicate a problem, but it doesn't exactly
> > > explain what is causing it.
> > > 
> > > When I do a "lp some-text-file", I get the same log entries in error_log
> > > as above, but with an extra line saying:
> > > 
> > > I [time] Started filter /usr/lib/cups/filter/texttops
> > > 
> > > with the PID and job number.  Everything else is the same, including the
> > 
> > > error message for the cupsomatic PID.
> > > 
> > > Any thoughts on where I should look next?
> > > 
> > > > Another useful place for errors is $HOME/.xsession-errors. I recently
> > > > went through some problems with my printer, and found some good info
> > > > there. Try doing a "tail -f .xsession-errors", and then launching a
> > > > print, and see if you can capture anything useful.
> > > 
> > > When doing that "test print" function from within KUPS, I saw the
> > > following lines in the .xsession-errors log:
> > > 
> > > which: no openProfile in (directories in my $PATH)
> > > which: no webbrowsing in (directories in my $PATH)
> > > /usr/bin/kfmclient
> > > QMenuData::removeItem: Index -1 out of range
> > > QMenuData::removeItem: Index -1 out of range
> > > QMenuData::removeItem: Index -1 out of range
> > > QMenuData::removeItem: Index -1 out of range
> > > undecodable token: \001b(hex)[361
> > > QObject::connect: No such slot
> > >   CupsdServerSecurityPage::cleanupEventFilter()
> > > QObject::connect:  (sender name: 'unnamed')
> > > QObject::connect:  (receiver name: 'unnamed')
> > 
> > Don't know if this will help but I'm noticing that sender/reciever unamed.
> >  I had a problem before setting up a printer through samba and found that
> > using kups I had to "Name" the printer calling it lp didn't work I
> > acutally had to give it a name (mines called Epson) as for location I used
> > the samba name for the print share.  I know yours' is local... but it
> > might need a unique name.
> 
> Tried that, it made no difference.  /var/log/cups/error_log showed the same 
> messages as before, but .xsession-errors was quiet.  In fact, other than 
> that one time, it's continued to be quiet.  I'm not sure at this point that 
> the message I did get that one time is actually related to the problem at 
> all....  It's really weird - it can detect which printer I've got hooked up 
> to the computer, but it won't actually send anything to it.  I wish I knew 
> what "status 32" meant, since it continually tells me in the error_log that 
> the cupsomatic pid is exiting with that status...
> 
> Any other ideas?
-- 
      David Guntner      GEnie: Just say NO!
 http://www.akaMail.com/pgpkey/davidg or key server
                 for PGP Public key


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to