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

some hplip components non-functional after python changes?



Before I start the e-mail, let me apologize for having first accidentally posted this message from an e-mail alias. That one (jpwallen_at_comcast.net) can be ignored. That address isn't subscribed to the list and is used mostly for commercial communications for my company.

Now, to the point of the post:

Two clean installations of daily build of Debian Squeeze are unable to run hp-setup.

I am using an Officejet 6310 connected to router on home network. All systems are Debian Squeeze. Two of them were installed a few months ago. At that time I was able to run "hp-setup -i xxx.xxx.xxx.xxx" to set up the MFP so that its scanner could be used by those systems. When I tried the same setup procedure on the two new systems I got the following output from hp-setup:

Traceback (most recent call last):
  File "/usr/bin/hp-setup", line 45, in <module>
    from base import device, utils, tui, models, module
  File "/usr/share/hplip/base/device.py", line 37, in <module>
    import status
  File "/usr/share/hplip/base/status.py", line 40, in <module>
    import hpmudext
ImportError: No module named hpmudext

When I checked the older systems, they also failed to run hp-setup interactively with the same error. Their access to the scanner was no affected -- until I fiddled around with them by removing cups and hplip and then re-installing them. Now all four systems are similar in that they can use the printing functions of the OfficeJet 6310 just fine, but there's no way that I can find to make the scanner work.

I ran hp-check -r and got about 23 errors and the suggestion in the summary to install python-qt4-dbus and python-reportlab. Their descriptions in the package manager didn't fill me with hope that installing them would be fruitful, but I did it anyway. The only improvement in hp-check after installing the packages is that hp-check isn't asking for them any more. But cupsext, pcardext, hpmudext, and scanext are not being found and are not loading.

I performed the following checks after reading a FAQ (http://hplipopensource.com/node/323) I found from a link in a Question posted at the hplip launchpad site.

python -V
Python 2.6.5+

I used locate to find the four modules that hp-check says aren't loading (cupsext, pcardext, hpmudext, and scanext) with the following results:
/usr/lib/python2.5/site-packages/cupsext.la
/usr/lib/python2.5/site-packages/cupsext.so
/usr/lib/python2.5/site-packages/pcardext.la
/usr/lib/python2.5/site-packages/pcardext.so
/usr/lib/python2.5/site-packages/hpmudext.la
/usr/lib/python2.5/site-packages/hpmudext.so
/usr/lib/python2.5/site-packages/scanext.la
/usr/lib/python2.5/site-packages/scanext.so

ls -l /usr/lib/ | grep python
lrwxrwxrwx 1 root root 32 Jun 18 06:12 libpyglib-2.0-python2.5.so.0 -> libpyglib-2.0-python2.5.so.0.0.0 -rw-r--r-- 1 root root 12332 Jun 7 14:43 libpyglib-2.0-python2.5.so.0.0.0 lrwxrwxrwx 1 root root 32 Jun 18 06:12 libpyglib-2.0-python2.6.so.0 -> libpyglib-2.0-python2.6.so.0.0.0 -rw-r--r-- 1 root root 12096 Jun 7 14:43 libpyglib-2.0-python2.6.so.0.0.0 lrwxrwxrwx 1 root root 19 Apr 27 06:24 libpython2.5.so.1 -> libpython2.5.so.1.0
-rw-r--r--  1 root root      1232788 Apr 21 06:26 libpython2.5.so.1.0
lrwxrwxrwx 1 root root 19 Jul 3 06:59 libpython2.6.so.1 -> libpython2.6.so.1.0
-rw-r--r--  1 root root      2394804 Jun 30 21:26 libpython2.6.so.1.0
drwxr-xr-x  3 root root         4096 Feb  5 14:51 python2.4
drwxr-xr-x 21 root root        20480 Apr 27 07:15 python2.5
drwxr-xr-x 23 root root        20480 Jul  3 15:05 python2.6
drwxr-xr-x  3 root root         4096 Mar 10 06:20 python3.1

I could see that the system is using Python 2.6.5 and that the missing modules are located at /usr/lib/python2.5/site-packages. I started to copy the modules to /usr/lib/python2.6/site-packages, but the site-packages subdirectory doesn't exist.

I'm guessing that this is an issue with Debian Squeeze / Testing and the ongoing Python version migration. Right now I'm not sure whether to try to fix the systems in their current state or wait for developments in the Python migration.

I also wasn't sure whether I should ask about this on the hplip launchpad site or on the Debian user list. (So I'm doing both.)


Reply to: