Comment 14 for bug 335116

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Checked with hp-levels:

hp:/net/Photosmart_C8100_series?ip=192.168.2.101: OK
hp:/net/Photosmart_Pro_B9100_series?ip=192.168.2.108: Gives Traceback "ValueError: invalid literal for long() with base 16: ''", with 2.8,12 it showed the ink levels correctly
hp:/usb/Photosmart_A710_series?serial=CN6B92118304R4: Printer not connected, gives "Unable to communicate with device" OK
hp:/usb/Officejet_H470?serial=CN7BU18154: Printer not connected, gives "Unable to communicate with device" OK
hp:/usb/HP_LaserJet_3390?serial=00CNMJP81545: OK
hp:/net/HP_Color_LaserJet_3600?ip=192.168.2.103: OK
hp:/usb/Photosmart_C5200_series?serial=MY7C3FD0XZ0559: Printer not connected, gives "Unable to communicate with device" OK

hp-systray gives the "ValueError: invalid literal for long() with base 16: ''" on startup, but I do not know which device triggers it. The right click menu of the hp-systray shows correct status for all devices before the HP PhotoSmart B9100 and beginning from this printer to the end of the list no status is shown. Seems that the B9100 crashes the status reporting process with said segfault.

Note that the B9100 is not officially supported, but it reported status and ink levels correctly with HPLIP 2.8.12. In general an unsupported device should not crash the whole framework but at least give a decent error message.

Within the hp-toolbox the Supplies tab says "Supplies information not available for this device." and the Status tab says "Status information not available for this device.", independent which printer I choose (but no traceback appears). Perhaps this is caused due to the crashed status reporting process in hp-systray.

When I start the hp-toolbox I am on the "Action" tab of the HP Color LaserJet 3600 and the tab stays empty. It gets only filled if I go to another printer and then back to the HP Color LaserJet 3600. Seems that it gets only filled by changing between printers but not by starting hp-toolbox.

The same happens even with the B9100 not plugged in. So the traceback happens already before communicating with the B9100.

If I remove the print queue for the B9100 all problems disappear.