Package: hplip<br>Version: 2.7.10-5<br><br><br>I am running Debian Sid with a 2.6.10 kernel and an HP OfficeJet 5510
All-In-One printer attached through a USB port, using CUPS for all
printing. Since upgrading my entire installation recently to the current Sid, I have not
been able to communicate with the printer, although it was working
previously. The problem exists whether I use the CUPS admin
webapp or the HPLIP utilities. In web searches of
the HPLIP web site and various email forums, I have found information
about previous similar problems in HPLIP, but most are regarding old
problems that have been fixed, and none of the more recent suggestions
have worked for me.
<br><br>Here are the errors I see in /var/log/syslog.<br><br>Dec 15 13:32:14 fwy-li officejet_5500_series?serial<div id="1f0c" class="ArwC7c ckChnd">=MY55DG135K96: io/hpmud/musb.c 549: invalid product id string: Operation not permitted
<br>Dec 15 13:32:14 fwy-li officejet_5500_series?serial=MY55DG135K96: io/hpmud/musb.c 1003: unable to open hp:/usb/officejet_5500_series?serial=MY55DG135K96
<br>Dec 15 13:32:14 fwy-li officejet_5500_series?serial=MY55DG135K96: INFO: open device failed; will retry in 30 seconds...<br><br><br>Here are relevant installed packages.<br><br>fwy-li:/home/fwy# dpkg -l "hp*" cupsys
<br>Desired=Unknown/Install/Remove/Purge/Hold<br>| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed<br>|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)<br>||/ Name Version Description
<br>+++-==============-==============-============================================<br>ii cupsys 1.3.4-2 Common UNIX Printing System(tm) - server<br>pn hp-ppd <none> (no description available)
<br>pn hp2xx <none> (no description available)<br>pn hp48cc <none> (no description available)<br>ii hpijs 2.7.10+2.7.10- HP Linux Printing and Imaging - gs IJS drive
<br>ii hpijs-ppds 2.7.10+2.7.10- HP Linux Printing and Imaging - HPIJS PPD fi<br>pn hping2 <none> (no description available)<br>ii hplip 2.7.10-5 HP Linux Printing and Imaging System (HPLIP)
<br>pn hplip-base <none> (no description available)<br>ii hplip-data 2.7.10-5 HP Linux Printing and Imaging - data files<br>un hplip-doc <none> (no description available)
<br>
ii hplip-gui 2.7.10-5 HP Linux Printing and Imaging - GUI utilitie<br>pn hplip-ppds <none> (no description available)<br>pn hpoj <none> (no description available)<br>
un hpoj-xojpanel <none> (no description available)<br>pn hpscanpbm <none> (no description available)<br>pn hpsockd <none> (no description available)<br><br><br>Here is the output of the 'lsusb' command, where is appears that the device is recognized properly.
<br><br>fwy-li:/home/fwy# lsusb<br>Bus 001 Device 002: ID 03f0:3a11 Hewlett-Packard OfficeJet 5510<br>Bus 001 Device 001: ID 0000:0000 <br><br><br>Here is the output of the 'hp-probe' command, which also looks correct.
<br><br>fwy-li:/home/fwy# hp-probe -busb<br><br>HP Linux Imaging and Printing System (ver. 2.7.10)<br>Printer Discovery Utility ver. 4.0<br><br>Copyright (c) 2001-7 Hewlett-Packard Development Company, LP<br>This software comes with ABSOLUTELY NO WARRANTY.
<br>This is free software, and you are welcome to distribute it<br>under certain conditions. See COPYING file for more details.<br><br><br>--------------------<br>| DEVICE DISCOVERY |<br>--------------------<br><br> Device URI Model
<br> ------------------------------------------------- ------------------------<br> hp:/usb/officejet_5500_series?serial=MY55DG135K96 HP officejet 5500 series<br><br>Found 1 printer(s) on the 'usb' bus.<br><br>
<br><br>Here is the output of the '/usr/lib/cups/backend/hp' command.<br><br>fwy-li:/home/fwy# /usr/lib/cups/backend/hp<br>direct hp:/usb/officejet_5500_series?serial=MY55DG135K96
"HP officejet 5500 series" "HP officejet 5500 series USB MY55DG135K96
HPLIP" "MFG:HP;MDL:officejet 5500 series;CLS:PRINTER;DES:officejet 5500 series;SN:MY55DG135K96;"
<br><br><br>And finally, here is the output of the 'lpinfo -l -v' command.<br><br>fwy-li:/home/fwy# lpinfo -l -v<br>Device: uri = socket<br> class = network<br> info = AppSocket/HP JetDirect<br> make-and-model = Unknown
<br> device-id = <br>Device: uri = beh<br> class = network<br> info = Backend Error Handler<br> make-and-model = Unknown<br> device-id = <br>Device: uri = hpfax<br> class = direct
<br> info = HP Fax (HPLIP)<br> make-and-model = Unknown<br> device-id = <br>Device: uri = hp<br> class = direct<br> info = HP Printer (HPLIP)<br> make-and-model = Unknown<br> device-id =
<br>Device: uri = http<br> class = network<br> info = Internet Printing Protocol (http)<br> make-and-model = Unknown<br> device-id = <br>Device: uri = ipp<br> class = network<br> info = Internet Printing Protocol (ipp)
<br> make-and-model = Unknown<br> device-id = <br>Device: uri = lpd<br> class = network<br> info = LPD/LPR Host or Printer<br> make-and-model = Unknown<br> device-id = <br>Device: uri = parallel:/dev/lp0
<br> class = direct<br> info = LPT #1<br> make-and-model = Unknown<br> device-id = <br>Device: uri = scsi<br> class = direct<br> info = SCSI Printer<br> make-and-model = Unknown
<br> device-id = <br>Device: uri = smb<br> class = network<br> info = Windows Printer via SAMBA<br> make-and-model = Unknown<br><br><br><br>The
HPLIP Toolbox application (hp-toolbox) sees the printer with the
correct URL, but cannot communicate with it. It displays the message
'ERROR: Device not found. Please check connection and power-on
device.' I have tried setting up the printer using both hp-setup and
CUPS, with the same results. Yet the physical USB connection is fine
and the power is on.
<br><br><br>Based on similar postings I have seen on the web, I have tried changing the URL from the default hp:/usb/officejet_5500_series?serial=MY55DG135K96 to usb://hp/officejet%205500%20series?serial=MY55DG135K96,
but this caused CUPS to think that the printer was disconnected. Other
postings suggested that permissions or other information set in the
udev rules files (/etc/udev/rules.d/*) were causing problems. However,
I am not using udev, so I don't think these points are relevant.
<br><br>Is this a bug in the Debian hplip 2.7.10 package?<br><br><br>Thx in advance,<br>fwy<br></div>