hplip crashes laserjet 1020 printer

Bug #1510367 reported by uski on 2015-10-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
HPLIP
Undecided
Unassigned

Bug Description

Hello,

I am using HPLIP 3.15.9

When connecting a HP LaserJet 1020 printer, it is crashed by HPLIP. No printing is possible.
The printer works fine under Windows 8.

I see the following in /var/log/syslog

Oct 27 00:18:11 yoga kernel: [ 2493.110332] usb 1-2: new high-speed USB device number 14 using xhci_hcd
Oct 27 00:18:12 yoga kernel: [ 2493.314897] usb 1-2: New USB device found, idVendor=03f0, idProduct=2b17
Oct 27 00:18:12 yoga kernel: [ 2493.314905] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 27 00:18:12 yoga kernel: [ 2493.314909] usb 1-2: Product: HP LaserJet 1020
Oct 27 00:18:12 yoga kernel: [ 2493.314912] usb 1-2: Manufacturer: Hewlett-Packard
Oct 27 00:18:12 yoga kernel: [ 2493.314915] usb 1-2: SerialNumber: JL22T4F
Oct 27 00:18:12 yoga kernel: [ 2493.318117] usblp 1-2:1.0: usblp1: USB Bidirectional printer dev 14 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17
Oct 27 00:18:12 yoga logger: loading HP Device 001 014
Oct 27 00:18:12 yoga python: io/hpmud/musb.c 2165: [18524] hpmud_make_usb_uri() bus=001 dev=014
Oct 27 00:18:12 yoga python: io/hpmud/musb.c 2262: hpmud_make_usb_uri() uri=hp:/usb/HP_LaserJet_1020?serial=JL22T4F bytes_read=39
Oct 27 00:18:12 yoga python: io/hpmud/musb.c 2165: [18528] hpmud_make_usb_uri() bus=001 dev=014
Oct 27 00:18:12 yoga python: io/hpmud/musb.c 2262: hpmud_make_usb_uri() uri=hp:/usb/HP_LaserJet_1020?serial=JL22T4F bytes_read=39
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 426: Found interface conf=0, iface=0, altset=0, index=1
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 388: Active kernel driver on interface=0 ret=1
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 392: Detaching kernel driver on interface=0 ret=0
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 531: claimed 7/1/2 interface
Oct 27 00:18:15 yoga kernel: [ 2496.675088] usblp1: removed
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 775: read actual device_id successfully fd=1 len=82
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 557: released 7/1/2 interface
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 426: Found interface conf=0, iface=0, altset=0, index=1
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 388: Active kernel driver on interface=0 ret=0
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 531: claimed 7/1/2 interface
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 775: read actual device_id successfully fd=1 len=82
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 557: released 7/1/2 interface
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 426: Found interface conf=0, iface=0, altset=0, index=1
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 388: Active kernel driver on interface=0 ret=0
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 531: claimed 7/1/2 interface
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 775: read actual device_id successfully fd=1 len=82
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 557: released 7/1/2 interface
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 426: Found interface conf=0, iface=0, altset=0, index=1
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 388: Active kernel driver on interface=0 ret=0
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 531: claimed 7/1/2 interface
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 775: read actual device_id successfully fd=1 len=82
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 557: released 7/1/2 interface
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 955: new PRINT channel=2 clientCnt=1 channelCnt=1
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 426: Found interface conf=0, iface=0, altset=0, index=1
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 388: Active kernel driver on interface=0 ret=0
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 531: claimed 7/1/2 interface
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 557: released 7/1/2 interface
Oct 27 00:18:15 yoga python: io/hpmud/musb.c 970: removed PRINT channel=2 clientCnt=0 channelCnt=0
Oct 27 00:18:15 yoga udev-configure-printer: add /devices/pci0000:00/0000:00:14.0/usb1/1-2
Oct 27 00:18:15 yoga udev-configure-printer: device devpath is /devices/pci0000:00/0000:00:14.0/usb1/1-2
Oct 27 00:18:15 yoga udev-configure-printer: Device vendor/product is 03F0:2B17

Then I see the printer doing something (motor starts, LEDs blink).
And after a few seconds :

Oct 27 00:18:21 yoga udev-configure-printer: Failed to fetch Device ID
Oct 27 00:18:21 yoga colord: Device added: sysfs-Hewlett-Packard-HP_LaserJet_1020

And then nothing. From now one, the printer will no longer enumerate on the USB bus.
If I disconnect and reconnect it, all I get is :
usb 1-2: new high-speed USB device number 15 using xhci_hcd
and that's it. And lsusb hangs until I unplug the printer (yes this is a USB 3.0 port and I tried on a USB 2.0 port, same result)

I have to power off and power on the printer again, so it can enumerate, but printing is not possible.
I can reproduce this as much as I want and the printer does work under Windows.

I have removed foo2zjs driver, it did not help.

Kernel is 4.3.0 amd64
Distro is ubuntu 14.04.3

I have used this printer in the past on this exact computer. Not sure what caused the malfunction.

After finishing the above text I tried uninstalling hplip, reinstalling foo2zjs, I was able to install the printer, but I still can't print (that's probably a different issue). But at least it does not crash the printer firmware.

It looks like HPLIP does something that crashes the printer internal firmware.

uski (ba-cykian) wrote :

Just tested 3.12.10 and guess what, it works.

So there is a regression somewhere.
3.15.4 did not work either so it's between 3.12.10 and 3.15.4

This confirms my setup is correct and this is a hplip bug.

uski (ba-cykian) wrote :

3.13.2 works too.
3.14.6 has a "communication error" (might be the same issue as with the latest driver)
Going back to 3.13.5 : it works.

I'm staying there.

The developpers might want to take a look at the changes since 3.13.5, the regression is somewhere there.

goutam (goutamkk) wrote :

Hi uski,

Thank you for reporting this issue.
We will look into it.

Thanks,
goutam

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers