hplip not working after jaunty upgrade
Bug #349781 reported by
Thomas Kluyver
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hplip (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Jaunty |
Fix Released
|
High
|
Unassigned | ||
python-defaults (Ubuntu) |
Invalid
|
Critical
|
Unassigned | ||
Jaunty |
Invalid
|
Critical
|
Unassigned |
Bug Description
Binary package hint: hplip
After upgrading to Jaunty, the HP (hp-systray, -toolbox, -check...) programs refuse to start, with an error message:
"warning: CUPSEXT could not be loaded. Please check HPLIP installation."
Debugging reveals that the scripts are failing to import the file /usr/lib/
Changed in hplip (Ubuntu Jaunty): | |
status: | Triaged → In Progress |
Changed in hplip (Ubuntu Jaunty): | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
There is aknown issue with Python in Jaunty and you should update your system immediately. Please see the posting from James Westby below.
------- ------- ------- ------- ------- ------- --
This morning python2.6 version 2.6.1-1ubuntu5 made it in to Jaunty after DecodeUTF8" . Most importantly update-manager was affected,
being held for a few days for the freeze. Unfortunately this package
contained an ABI break that meant some python extensions no longer
worked, most notably pygtk. In other words if you installed this version
you would see some apps fail to start with a message "undefined symbol:
PyUnicodeUCS4_
making it harder to upgrade to a fixed version.
https:/ /bugs.launchpad .net/ubuntu/ +source/ python2. 6/+bug/ 349467/
Access to the bad packages was blocked, which is why you might have
seen 403 errors if you attempted to upgrade this morning, and fixed
packages have been uploaded as version 2.6.1-1ubuntu5.1.
To find out if you have the bad version of the package installed you
can run
dpkg -l python2.6 | cat
If the version is not 2.6.1-1ubuntu5 then you are unaffected, you should
just be sure that you don't install that version if it is still
accessible on your mirror.
If you do have the bad version installed then you can upgrade using
apt-get.
sudo apt-get update
sudo apt-get upgrade
The fixed packages have only just been made available on the primary
mirror, so you may need to wait a few hours before they can become
available.
Thanks,
James