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

Bug#456812: marked as done (HPLIP cannot communicate with HP OfficeJet 5510 printer)

Your message dated Sun, 10 Feb 2008 22:50:48 -0600
with message-id <ac5335900802102050k212d0c9amb2e5b189f20b0cda@mail.gmail.com>
and subject line Not a bug!
has caused the Debian Bug report #456812,
regarding HPLIP cannot communicate with HP OfficeJet 5510 printer
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
456812: http://bugs.debian.org/cgi-bin//456812
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- Package: hplip
Version: 2.7.10-5


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.

Here are the errors I see in /var/log/syslog.

Dec 15 13:32:14 fwy-li officejet_5500_series?serial
=MY55DG135K96: io/hpmud/musb.c 549: invalid product id string: Operation not permitted
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
Dec 15 13:32:14 fwy-li officejet_5500_series?serial=MY55DG135K96: INFO: open device failed; will retry in 30 seconds...


Here are relevant installed packages.

fwy-li:/home/fwy# dpkg -l "hp*" cupsys
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
ii  cupsys         1.3.4-2        Common UNIX Printing System(tm) - server
pn  hp-ppd         <none>         (no description available)
pn  hp2xx          <none>         (no description available)
pn  hp48cc         <none>         (no description available)
ii  hpijs          2.7.10+2.7.10- HP Linux Printing and Imaging - gs IJS drive
ii  hpijs-ppds     2.7.10+2.7.10- HP Linux Printing and Imaging - HPIJS PPD fi
pn  hping2         <none>         (no description available)
ii  hplip          2.7.10-5       HP Linux Printing and Imaging System (HPLIP)
pn  hplip-base     <none>         (no description available)
ii  hplip-data     2.7.10-5       HP Linux Printing and Imaging - data files
un  hplip-doc      <none>         (no description available)
ii  hplip-gui      2.7.10-5       HP Linux Printing and Imaging - GUI utilitie
pn  hplip-ppds     <none>         (no description available)
pn  hpoj           <none>         (no description available)
un  hpoj-xojpanel  <none>         (no description available)
pn  hpscanpbm      <none>         (no description available)
pn  hpsockd        <none>         (no description available)


Here is the output of the 'lsusb' command, where is appears that the device is recognized properly.

fwy-li:/home/fwy# lsusb
Bus 001 Device 002: ID 03f0:3a11 Hewlett-Packard OfficeJet 5510
Bus 001 Device 001: ID 0000:0000 


Here is the output of the 'hp-probe' command, which also looks correct.

fwy-li:/home/fwy# hp-probe -busb

HP Linux Imaging and Printing System (ver. 2.7.10)
Printer Discovery Utility ver. 4.0

Copyright (c) 2001-7 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.


--------------------
| DEVICE DISCOVERY |
--------------------

  Device URI                                         Model                  
  -------------------------------------------------  ------------------------
  hp:/usb/officejet_5500_series?serial=MY55DG135K96  HP officejet 5500 series

Found 1 printer(s) on the 'usb' bus.



Here is the output of the '/usr/lib/cups/backend/hp' command.

fwy-li:/home/fwy# /usr/lib/cups/backend/hp
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;"


And finally, here is the output of the 'lpinfo -l -v' command.

fwy-li:/home/fwy# lpinfo -l -v
Device: uri = socket
        class = network
        info = AppSocket/HP JetDirect
        make-and-model = Unknown
        device-id =
Device: uri = beh
        class = network
        info = Backend Error Handler
        make-and-model = Unknown
        device-id =
Device: uri = hpfax
        class = direct
        info = HP Fax (HPLIP)
        make-and-model = Unknown
        device-id =
Device: uri = hp
        class = direct
        info = HP Printer (HPLIP)
        make-and-model = Unknown
        device-id =
Device: uri = http
        class = network
        info = Internet Printing Protocol (http)
        make-and-model = Unknown
        device-id =
Device: uri = ipp
        class = network
        info = Internet Printing Protocol (ipp)
        make-and-model = Unknown
        device-id =
Device: uri = lpd
        class = network
        info = LPD/LPR Host or Printer
        make-and-model = Unknown
        device-id =
Device: uri = parallel:/dev/lp0
        class = direct
        info = LPT #1
        make-and-model = Unknown
        device-id =
Device: uri = scsi
        class = direct
        info = SCSI Printer
        make-and-model = Unknown
        device-id =
Device: uri = smb
        class = network
        info = Windows Printer via SAMBA
        make-and-model = Unknown



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.


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.

Is this a bug in the Debian hplip 2.7.10 package?


Thx in advance,
fwy

--- End Message ---
--- Begin Message --- Please close this bug report, as I have just fixed the problem.  It was a permissions problem on the USB printer device, which on my 2.6.10 kernel is located at /proc/bus/usb/001/*.  On this system, I am unable to upgrade to udev (can't remember why at the moment), although in most respects I track the Debian sid (unstable) distribution.  All the HPLIP documentation I was able to find at the sourceforge site, as well as all the web postings I could find about my symptoms, presume that the target system is using udev and can therefore manage the printer device through the rules files in /etc/udev/rules.d/.  As I am using only hotplug without udev to manage device permissions, these hints did not work for me.  However, I dug into hotplug and wrote a simple custom script and hplip.usermap file to allow hotplug to do this at the time the printer is plugged in and turned on.  Everything is now working again.

However, I still don't know exactly what the upgrade to hplip 2.7.10-5 did to change my system configuration.  I see that the device's group is now scanner, but this change would not have caused my problem.  Did the older hplip releases contain hotplug scripts that were obsoleted and purged from my system by the upgrade?  In any case, a sentence or two in the release notes and the technical documentation would help others avoid this problem.


--- End Message ---
Reply to: