hplip: hpssd needs cupsext. Where is that?

gkiagia · 09-01-2005, 08:53 AM

I installed hplip from rpm packages for suse that I found on rpmseek.com and I want to set up my dj3745 printer.
However, hpssd won't start. It says:

Quote:

# /etc/init.d/hplip restart
Stopping hpiod: /etc/profile: line 285: export: `PATH###': not a valid identifier
[ OK ]
Stopping hpssd: /etc/profile: line 285: export: `PATH###': not a valid identifier
[ OK ]
Starting hpiod: [ OK ]
Starting hpssd: [FAILED]
Note: You may have to restart the cupsd.

I tried to run hpssd manually by running /usr/share/hplip/hpssd.py and it says:

Quote:

# ./hpssd.py
Traceback (most recent call last):
File "./hpssd.py", line 50, in ?
from base import async, utils, database, status, pml, slp
File "/usr/share/hplip/base/database.py", line 38, in ?
import device
File "/usr/share/hplip/base/device.py", line 38, in ?
from prnt import pcl, ldl, cups
File "/usr/share/hplip/prnt/cups.py", line 38, in ?
import cupsext
ImportError: No module named cupsext

I guess it tries to load a file called cupsext.py and it can't find it. I searched in /usr but I can't find it. Am I missing something?

Help!

Edit:
Wrong, there it is: /usr/lib/python2.4/site-packages/cupsext.so
Is this what it tries to load? Why it cant load it?

kencaz · 09-01-2005, 09:05 AM

not sure about the particular "cupsext.py" location or purpose, however, here are some usefull CUPS commands:

service cups status

/etc/init.d/cupsys start

/etc/init.d/cupsys restart

Some more useful commands:
To show the accepting state of printers: lpstat -a
To show printers with their attached devices: lpstat -v
To list queued print jobs: lpstat -o
To cancel all print jobs: cancel -a Okipage8z
To cancel print job 37: cancel 37
To delete a printer: lpadmin -x Okipage8z
To view the CUPS log file: cat /var/log/cups/error_log

KC

gkiagia · 09-01-2005, 09:26 AM

Well, I fixed it. I just copied cupsext.so from /usr/lib/python2.4/site-packages/ to /usr/share/hplip.
So simple!!!

orgcandman · 09-01-2005, 09:42 AM

I would remove the copied file, and put up a symlink. that way, after upgrades, you can still maintain interoperability.

gkiagia · 09-02-2005, 08:04 AM

Hmm, that's right. I'll do it.