HP LaserJet 1000 still doesn't print

Bug #450513 reported by ilf
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cups (Ubuntu)
Fix Released
High
Unassigned
Karmic
Fix Released
High
Unassigned

Bug Description

Binary package hint: cups

After https://bugs.launchpad.net/ubuntu/+source/cups/+bug/420015 and https://bugs.launchpad.net/ubuntu/+source/foo2zjs/+bug/425300 my HP LaserJet 1000 still doesn't print.

CUPS sees it correctly, the firmware is uploaded, addind a job to the queue works, I get no error in the logs, but nothing is printed!

Actually there is one line in /var/log/cups/error_log:
W [13/Oct/2009:18:54:23 +0200] [Job 23] If you have more than one HP LaserJet 1000 printer connected to this machine, please unload (and blacklist) the "usblp" kernel module as otherwise CUPS will not be able to distinguish your printers.

Taking it literally, this doesn't concern me, since i don't have multiple printers attached.

All taking place on an up-to-date Karmic. Works on my Jaunty box.

Related branches

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

Can you please run the following commands and post the output here:

lsmod | grep usblp
ls -l /dev/usb/lp* /dev/bus/usb/*/*
sudo /usr/lib/cups/backend/usb
/usr/lib/cups/backend/hp
lpinfo -l -v
lpstat -v
lpstat -p

Can you also attach the files

/etc/cups/printers.conf
/etc/cups/ppd/*.ppd

Please also attach an error_log of a failed job, following the instructions in the section "CUPS error_log" on

https://wiki.ubuntu.com/DebuggingPrintingProblems

Changed in cups (Ubuntu):
status: New → Incomplete
importance: Undecided → High
milestone: none → ubuntu-9.10
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

I also need the output of

lsusb
lsusb -vvv

Please DO NOT turn off or unplug the printer between running these commands and running the commands of my previous comment.

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

Can you also attach the following files

/var/log/syslog
/var/log/kern.log
/var/log/messages

and also the output of the "dmesg" command?

Revision history for this message
ilf (ilf) wrote :

$ lsmod | grep usblp
usblp 15136 0

$ ls -l /dev/usb/lp* /dev/bus/usb/*/*
crw-rw-r-- 1 root root 189, 0 2009-10-14 11:05 /dev/bus/usb/001/001
crw-rw-r-- 1 root root 189, 5 2009-10-14 18:55 /dev/bus/usb/001/006
crw-rw-r-- 1 root root 189, 128 2009-10-14 11:05 /dev/bus/usb/002/001
crw-rw-r-- 1 root root 189, 129 2009-10-14 11:05 /dev/bus/usb/002/002
crw-rw-r-- 1 root root 189, 130 2009-10-14 11:05 /dev/bus/usb/002/003
crw-rw---- 1 root lp 189, 135 2009-10-14 18:59 /dev/bus/usb/002/008
crw-rw-rw- 1 root lp 180, 0 2009-10-14 18:59 /dev/usb/lp0

$ sudo /usr/lib/cups/backend/usb
DEBUG: list_devices_libusb
DEBUG: usb_find_busses=2
DEBUG: usb_find_devices=6
direct usb://HP/LaserJet%201000 "HP LaserJet 1000" "HP LaserJet 1000" "MFG:Hewlett-Packard;MDL:hp LaserJet 1000;CMD:ZJS;CLS:PRINTER;DES:hp LaserJet 1000;FWVER:20011207;" ""

$ /usr/lib/cups/backend/hp
bash: /usr/lib/cups/backend/hp: No such file or directory

$ lpstat -v
device for HP_LaserJet_1000: usb://HP/hp%20LaserJet%201000?serial=?

$ lpstat -p
printer HP_LaserJet_1000 is idle. enabled since Wed 14 Oct 2009 06:59:50 PM CEST
        If you have more than one HP LaserJet 1000 printer connected to this machine, please unload (and blacklist) the "usblp" kernel module as otherwise CUPS will not be able to distinguish your printers.

$ lsusb
Bus 001 Device 006: ID 05ac:1301 Apple, Inc. iPod Shuffle 2.Gen
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 046a:0011 Cherry GmbH G83 (RS 6000) Keyboard
Bus 002 Device 002: ID 045e:0047 Microsoft Corp. IntelliMouse Explorer 3.0
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

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

Thank you for all the files. I have found the problem. Your print queue was created by an old CUPS version which has put "serial=?" into the printer's URI. The current version of CUPS does not support this. I have patched CUPS now for appropriate backward compatibility.

The new CUPS version will get uploaded tomorrow and so in Karmic it will be fixed.

Changed in cups (Ubuntu Karmic):
status: Incomplete → Fix Committed
Revision history for this message
ilf (ilf) wrote :

I edited /etc/cups/printers.conf and took out "serial=?" and restarted CUPS, but it still doesn't print.
dmesg is still flooded with "usb 2-3: usbfs: interface 0 claimed by usblp while 'usb' sets config #1" messages.
Sure this was the problem? What am I diong wrong?

Revision history for this message
ilf (ilf) wrote :

Ah, the DeviceURI entry in /etc/cups/printers.conf was still wrong. Taking the one from "lpinfo -v" works.
Finally! Thank you :)

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cups - 1.4.1-5ubuntu1

---------------
cups (1.4.1-5ubuntu1) karmic; urgency=low

  * debian/patches/usb-backend-both-usblp-and-libusb.dpatch: Fixed a bug
    of modifying the URI of the current print queue when comparing it with
    discovered URIs. Made the USB backend also compatible with URIS generated
    by old versions of CUPS, without serial number or with "serial=?"
    (LP: #450513).
  * debian/cups.init.d: Make cold-plugging of USB printers also correctly
    work if the usblp kernel module is loaded.

 -- Till Kamppeter <email address hidden> Thu, 15 Oct 2009 18:32:20 +0200

Changed in cups (Ubuntu Karmic):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.