[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: HP printer saga

J. Zidar wrote:
After realizing that I must enable loopback device, I configured Cups to use my HP 656c printer. From www.linuxprinting.org I have downloaded the ppd file and copied it to the /usr/share/cups/model/. The configuration went without any problems.
I set up KDE to use Cups but when I sent something to be printed, nothing happens. 

What should I do?
thanks to anyone,
Jernej Zidar

Messages from cups's error_log:
I [06/Aug/2003:21:34:29 +0200] Job 2 queued on 'printercek' by 'zidar'.
I [06/Aug/2003:21:34:29 +0200] Started filter /usr/lib/cups/filter/pstops (PID 6575) for job 2. I [06/Aug/2003:21:34:29 +0200] Started filter /usr/lib/cups/filter/foomatic-rip (PID 6576) for job 2. 
E [06/Aug/2003:21:34:29 +0200] PID 6576 stopped with status 22!
I [06/Aug/2003:21:34:29 +0200] Started backend /usr/lib/cups/backend/usb (PID 6577) for job 2. 
I [06/Aug/2003:21:34:29 +0200] Saving printers.conf...
I [06/Aug/2003:21:34:42 +0200] Saving printers.conf...
I [06/Aug/2003:21:34:42 +0200] Started filter /usr/lib/cups/filter/pstops (PID 6579) for job 2. I [06/Aug/2003:21:34:42 +0200] Started filter /usr/lib/cups/filter/foomatic-rip (PID 6580) for job 2. I [06/Aug/2003:21:34:42 +0200] Started backend /usr/lib/cups/backend/usb (PID 6581) for job 2. 
I [06/Aug/2003:21:34:42 +0200] Saving printers.conf...
I [06/Aug/2003:21:34:42 +0200] Printer 'printercek' started by 'root'.
E [06/Aug/2003:21:34:42 +0200] PID 6580 stopped with status 22!
E [06/Aug/2003:21:34:51 +0200] restart_job: job #2 cannot be restarted - no files! 

Message from syslog:
Aug  6 21:35:48 kompi hpijs: unable to init hpijs server
Check the pppd file you got from www.linuxprinting.org. I suspect it also needs the hpijs package to work properly. If so, you will have to install it (the hpijs package).
If this is NOT the problem (hpijs package already installed) come on back with the CUPS packages you have installed and the VERSIONS. I am currenely running the packages from "unstable" and they have (or used to have) a few "gotchas" to get running. It involved the glibc and gcc transition going on right now. The ones from stable or testing were OK about a month ago. 

Cheers,
-Don Spoon-
Reply to: