Bug#502504: hplip: None of the applications will start
Package: hplip
Version: 2.8.6.b-3
Severity: grave
Justification: renders package unusable
None of the hp-* applications in the package will start. All fail with the
same message:
$ hp-check
error: CUPSEXT could not be loaded. Please check HPLIP installation.
This is the case for almost a year or so. Purging and reinstalling doesn't
help.
$ locate cupsext
/usr/lib/python-support/hplip/python2.5/cupsext.so
/var/lib/python-support/python2.5/cupsext.so
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (120, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages hplip depends on:
ii adduser 3.110 add and remove users and groups
ii coreutils 6.10-6 The GNU core utilities
ii cups 1.3.8-1lenny2 Common UNIX Printing System(tm) -
ii hplip-data 2.8.6.b-3 HP Linux Printing and Imaging - da
ii libc6 2.7-15 GNU C Library: Shared libraries
ii libcups2 1.3.8-1lenny2 Common UNIX Printing System(tm) -
ii libdbus-1-3 1.2.1-3 simple interprocess messaging syst
ii libsnmp15 5.4.1~dfsg-10 SNMP (Simple Network Management Pr
ii libssl0.9.8 0.9.8g-13 SSL shared libraries
ii libusb-0.1-4 2:0.1.12-13 userspace USB programming library
ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip
ii python 2.5.2-2 An interactive high-level object-o
ii python-dbus 0.83.0-1 simple interprocess messaging syst
ii python-imaging 1.1.6-3 Python Imaging Library
ii python-support 0.8.6 automated rebuilding support for P
Versions of packages hplip recommends:
ii cups-client 1.3.8-1lenny2 Common UNIX Printing System(tm) -
pn hpijs <none> (no description available)
pn hplip-gui <none> (no description available)
Versions of packages hplip suggests:
pn hplip-doc <none> (no description available)
ii kdeprint 4:3.5.9.dfsg.1-5 print system for KDE
pn openprinting-ppds <none> (no description available)
-- no debconf information
Reply to: