Printer (HWModel Name) May Not Be Connected

[nullack]

Binary package hint: cups

A number of USB Printers on Jaunty are not printing. They install their drivers fine and are recognised as being online but yet fail to print. The print status que has the error message Printer (HWModel Name) May Not Be Connected and the printing job appears to stall at a processing status.

So far I have identified the following printer models as being effected:

Samsung ML-2510-Series (this is mine)
HP 940c
HP 930C
hp5550 deskjet

This list is not exhaustive and I do not have an accurate picture of how many models might be effected.

The user of the hp5550 reported he was able to get his working by reinstalling all the cups and foomatic packages that are installed by default. When I tried that for my ML-2510 it did not fix the problem.

Steve Langalsek requested I create a new bug for this, separate to the info I added to a similarly symptomatic bug, bug #314106.

[nullack (nullack)]

Architecture: amd64
CupsErrorLog:
 E [25/Mar/2009:15:34:57 +1100] Resume-Printer: Unauthorized
 E [25/Mar/2009:17:56:07 +1100] Pause-Printer: Unauthorized
 E [25/Mar/2009:18:13:31 +1100] Resume-Printer: Unauthorized
DistroRelease: Ubuntu 9.04
Lpstat: device for ML-2510-Series: usb://Samsung/ML-2510%20Series?serial=3V54BKEL510850E.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: cups 1.3.9-15
PackageArchitecture: amd64
Papersize: a4
PpdFiles: ML-2510-Series: Samsung ML-2510, SpliX V. 2.0.0
ProcCmdLine: root=UUID=77ea2a78-4863-49aa-805c-f68d8068d1a4 ro quiet
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-11.37-generic
Uname: Linux 2.6.28-11-generic x86_64
UserGroups:

[Joel Goguen (jgoguen)]

Architecture: amd64
CupsErrorLog:

DistroRelease: Ubuntu 9.04
MachineType: Hewlett-Packard HP Pavilion dv2500 Notebook PC
NonfreeKernelModules: nvidia
Package: cups 1.3.9-15
PackageArchitecture: amd64
Papersize: letter
ProcCmdLine: root=UUID=775df9a2-1535-42cf-9799-0a70ff607204 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_CA.UTF-8
 LANGUAGE=en_CA:en
ProcVersionSignature: Ubuntu 2.6.28-11.37-generic
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin audio cdrom dialout disk lpadmin mail plugdev sambashare

[nullack (nullack)]

Added regression-potential flag as my samsung laser works fine under Intrepid.

[Lean Fuglsang (lean-ubuntu-cd)]

I can also confirm this bug. HP psc 1210.
The behaviour I experience is a little bit different. Instead of showing an error, it just says 'Job completed'.
On the printerdialog it looks like it is is printing all the pages, but just very fast, and nothing comes out of the printer.

[Lean Fuglsang (lean-ubuntu-cd)]

Okay,
I godt mine working. I installed foomatic* and cups* and rebooted. Now I could choose psc 1200 (hpijs) from the list.

[Lean Fuglsang (lean-ubuntu-cd)]

Multiple comments confirms this bug

[nullack (nullack)]

Noting that the recent updates to cups, foomatic, HPLip, AppArmor etcetc since the Jaunty beta release has not fixed this regression bug as of yet.

[cabernet54 (alex81emy)]

Lukly for me, after the upgrade to beta version (with the last update) the problem is solved ^_^

[Kevin Oberle (kevin.oberle)]

Confirmed on a HP LaserJet P1005

[Till Kamppeter (till-kamppeter)]

For me it seems that the USB CUPS backend has problems to communicate with the printer.

Do

cancel -a
cupsctl LogLevel=debug

The print another job and wait for the job getting into "Stopped" state or to disappear. This can take several minutes, as probably the USB backend of CUPS waits for a response from the printer and times out sooner or later. Then extract the error_log

sudo cp /var/log/cups/error_log ~
sudo chmod 777 ~/error_log

and attach it ~/error_log to this bug report.

Please execute "lsusb -vvv" and "ls -l /dev/bus/usb/*/*" as soon as the job is stuck and another time when it has gone into "Stopped" state or disappeared from the queue.

You can try a workaround as follows:

Run

sudo usb_printerid /dev/usb/lp0

and see whether the output contains your printer's model name. If so, do

cupsctl FileDevice=yes
lpadmin -p <name of your print queue> -E -v file:/dev/usb/lp0

If not, try the same with /dev/usb/lp1, /dev/usb/lp2, ...

Now try to print. Does it work?

Note that this is only a workaround and only works reliably if you have only one USB printer connected to your machine.

[Nick A (nickalleyne)]

Also affects me.

Running the jaunty beta on a dell D630, I have yet to figure out how to get it to print using an Epson stylus CX4800.

I have installed the "foomatic" packages from synaptic as it seems that a few recommended that in the forums.

I did what was listed above... when entering "sudo usb_printerid /dev/usb/lp0" I got:

GET_DEVICE_ID string:
MFG:EPSON;CMD:ESCPL2,BDC,D4,ESCPR1;MDL:Stylus CX4800;CLS:PRINTER;DES:EPSON Stylus CX4800;

but I could not figure out what to put for <name of your print queue> in the next command so no go printing it.

I attached the ~/error_log

[Nick A (nickalleyne)]

Strange, after re-installing everything and restarting it did not work.

I opened up the foomatic control panel (in applications>system tools) and installed it from there using the "simple" foomatic driver and it worked.

[Till Kamppeter (till-kamppeter)]

Nick A, now where you have iot working can you do the following:

Start system-config-printer (System -> Administration -> Printing), click on the "New" button and follow the wizard to create a new printer. In the end give a new name (like "test") to your new printer. Say "Yes" when you are asked to print a test page. Does it print? Independent whether it prints or not, run the troubleshooting wizard of system-config-printer (Help -> Troubleshooting). Do it once selecting the printer you have created with the Foomatic Control Panel and once selecting the new printer which you have just created with system-config-printer.

Nick A, the <name of your print queue> is the name which you give to the printer with system-config-printer or the Foomatic Control Panel and which also appears in the printing dialogs of your applications. It is Stylus-CX4800 for the printer which did not work for you in the beginning.

[Till Kamppeter (till-kamppeter)]

Can everyone here who has the problem on an amd64 (x86_64) system replace the file /usr/lib/cups/backend/usb by the attached file and then try again? Does this fix the problem?

[Till Kamppeter (till-kamppeter)]

Do not forget to make the file executable ("sudo chmod 755 /usr/lib/cups/backend/usb").

[andschuster (andreas-schuster2)]

I can confirm this bug with a HP Laserjet 1300 on an i386-system using a fresh upgrade from Intrepid to Jaunty beta.

[Martin Pitt (pitti)]

Does your printer appear in "lpinfo -v"? Can you please copy&paste the output of that?

Can you please also attach /var/log/kern.log? Does it work again if you do

  sudo aa-complain cups

? After trying this, please revert the change with "sudo aa-enforce cups".

[Till Kamppeter (till-kamppeter)]

Can everyone of you also try the following command sequence, independent whether the printer is from HP or not:

sudo chmod -x /usr/lib/cups/backend/hp*
sudo rmmod usblp
sudo modprobe usblp

Does printing work now? Does printing still work after a reboot?

For returning to the original state do

sudo chmod +x /usr/lib/cups/backend/hp*

[Alessandro Ghersi (alessandro-ghersi)]

After these commands:
sudo chmod -x /usr/lib/cups/backend/hp*
sudo rmmod usblp
sudo modprobe usblp

Doesn't work and doesn't work after reboot.

After apparmor-utils command doesn't work.

lpinfo -v

network socket
network beh
direct hal:///org/freedesktop/Hal/devices/usb_device_4b8_811_L67010501261444460_if1_printer_noserial
direct usb://EPSON/Stylus%20Photo%20RX620
direct hpfax
direct hp
network http
network ipp
network lpd
direct scsi
serial serial:/dev/ttyS0?baud=115200
network smb

[Martin Pitt (pitti)]

I can reproduce this, taking.

[Martin Pitt (pitti)]

Sorry, I have a completely different bug after all (will report in a minute), I cannot reproduce this one.

I'll still watch it, it'll be interesting to see testing of Till's new proposed backend (comment 26)

[Alessandro Ghersi (alessandro-ghersi)]

In my system with epson RX620, new /usr/lib/cups/backend/usb file (comment 26) doesn't resolve the problem, see bug #350107

[Alessandro Ghersi (alessandro-ghersi)]

I forgot...workaround in comment #22 works fine.

[andschuster (andreas-schuster2)]

I tried Till's advice:

sudo chmod -x /usr/lib/cups/backend/hp*
sudo rmmod usblp
sudo modprobe usblp

But printing using my HP Laserjet 1300 doesn't work. In the HP device manager I get an "Device communication error".

lpinfo -v

network socket
network beh
file cups-pdf:/
direct hal:///org/freedesktop/Hal/devices/usb_device_3f0_1017_00CNBD032941_if0_printer_noserial
direct hpfax
direct hp
network http
network ipp
network lpd
direct scsi
serial serial:/dev/ttyS0?baud=115200
serial serial:/dev/ttyS1?baud=115200
network smb

[Till Kamppeter (till-kamppeter)]

Thank you all for the additional logs and info of your situation.

Note: The attached binary file is NOT the libusb-based USB backend of CUPS 1.4.x. It is the unpatched USB backend of CUPS 1.3.9, with a bug fix patch which was added between Intrepid and Jaunty removed.

It looks very much like a slight change in the kernel which breaks compatibility with the USB backend of CUPS. So most probably you could work around the problem by using the HPLIP backend (most HP printers) or the HAL backend. When creating new print queues system-config-printer selects the HPLIP backend automatically wherever possible. The HAL backend can be selected maually by clicking "Connection" at the bottom of the right part of "Select Device" step of the new printer wizard, when in the tree view on the left a USB printer is selected.

Next step to try to fix this problem is to replace the CUPS USB backend by the libusb-based one of CUPS 1.4, as it accesses the printer through another entrance point in the kernel, the same ways as the HPLIP backend does but for printers of all manufacturers. The automatic printer discovery/setup via HAL (hal-cups-utils) is already prepared for this backend.

[andschuster (andreas-schuster2)]

Till,

I use the HPLIP backend, but I am confronted with the same problem using a HP Laserjet 1300.

[andschuster (andreas-schuster2)]

I tried the HAL-backend: The result is the same, printing doesn't work.

[Facundo Batista (facundo)]

I'm using a HP LaserJet P1005, have the detailed bug 352431.

With my printer created, but not working, I did

  sudo aa-complain cups

Then went to print a test page, but again, nothing happened (the job gets into the printer queue and then disappears, but no page is printed).

I revoked that with "sudo aa-enforce cups".

Also tried the rmmod/modprobe usblp trick (with the -/+x change). Nothing.

Then I put the connection through HAL:

  hal:///org/freedesktop/Hal/devices/usb_device_3f0_3d17_0_if0_printer_noserial

And again, nothing happens.

The printer just doesn't print anything...

$ lpinfo -v
network socket
network beh
direct hal:///org/freedesktop/Hal/devices/usb_device_3f0_3d17_0_if0_printer_noserial
direct hpfax
direct usb://HP/LaserJet%20P1002
direct hp
network http
network ipp
network lpd
direct parallel:/dev/lp0
direct scsi
serial serial:/dev/ttyS0?baud=115200
network smb

[Michele Nasti (artlover)]

Hi all. I can confirm that workaround in #22 works fine. I have a Samsung ML-2010 on ubuntu 9.04 32bit, with a Dell XPS m1330. I did the following:

           sudo usb_printerid /dev/usb/lp0

this outputs:

          GET_DEVICE_ID string:
          MFG:Samsung;CMD:GDI;MDL:ML-2010;CLS:PRINTER;STATUS:BUSY;

So I did the commands
          cupsctl FileDevice=yes
          lpadmin -p ML-2010 -E -v file:/dev/usb/lp0

and the process that I had stuck in the queue was soon deleted, but not printed. So I sent to print another job and it went good. Obviously, I have only one printer connected to my computer.

[Michele Nasti (artlover)]

Do I have to do something everytime I reboot? And do you need some log file from my computer, since it works?

[Till Kamppeter (till-kamppeter)]

Another thing worth trying is the following:

cancel -a
sudo chown root.root /usr/lib/cups/backend/usb
sudo chmod 700 /usr/lib/cups/backend/usb

Now try again to print through a queue which uses the "usb" backend (with "usb://..." URI). Does it work now?

The above commands make the "usb" CUPS backend always be executed as root. This overcomes any permission problem.

You get back into the original state via

sudo chmod 755 /usr/lib/cups/backend/usb

[Till Kamppeter (till-kamppeter)]

If the workaround presented in my previous comment does not work for you, try the following:

Get cups_1.3.9-16ubuntu1~ppa1 from my PPA. It contains a USB backend which is based on libusb, taken from CUPS 1.4.x. Note that the package is only for testing and therefore not perfect. You have to do the following manual steps:

1. The AppArmor configuration is not prepared for the access via libusb, deactivate AppArmor for CUPS with

sudo aa-complain cupsd

2. The usblp kernel module blocks the access for the new USB backend. You need to deactivate it. Add a line "blacklist usblp" to the /etc/modprobe.d/blacklist.conf file and run

sudo rmmod usblp

Now the module is unloaded and will not get reloaded if you plug in or power-cycle a USB printer or if you reboot.

With all this done, try setting up your printer with the "usb" backend (not HPLIP or HAL, nor my first workaround) and see whether it prints or not.

This is the last mean. If this does not work, the only cause of the bug can be the kernel. We tried so many backends now.

[Till Kamppeter (till-kamppeter)]

My PPA you find here:

https://launchpad.net/~till-kamppeter/+archive/ppa

There you also find the lines which you have to add to your /etc/apt/sources.list so that you can update/get packages from my PPA.

[Till Kamppeter (till-kamppeter)]

Michele Nasti, my file:/dev/usb/lpX workaround does not need any manual action after rebooting. Only take care to never connect more than one USB printer (use network or parallel connection if you need a second printer).

[Till Kamppeter (till-kamppeter)]

We need more info to find out why the CUPS backends are hanging when printing via USB. Clear the print queues with

cancel -a

Make also sure that you do not run your USB backend as root:

sudo chmod 755 /usr/lib/cups/backend/usb

Then send a new print job and as soon as you have sent it do

ps auxwww | grep '^lp '

Look for the process entry which contains the URI of the print queue to which you have printed. This is the backend process. The process number of the process is the number following right after the "lp" in the beginning of the line. Attach strace to the backend:

sudo strace -o /tmp/trace -fv -p <process number>

Replace <process number> by the process number which you have found.

Post the /tmp/trace file here. Do not compress it.

[Till Kamppeter (till-kamppeter)]

Thank you for the strace, can you now install the CUPS package from my PPA, follow the instructions of my comment about the package, clear the queue, and try to print again? If it still does not work, do another strace, this time with the new CUPS installed.

[Till Kamppeter (till-kamppeter)]

As it does not work with all CUPS backends (CUPS USB, HPLIP, HAL) in Jaunty and worked in Intrepid this one is most probably a kernel problem. Added kernel task.

Can everyone who has this problem and has updated from Intrepid (or older) to Jaunty boot the last Intrepid (or non-Jaunty) kernel (the update does not uninstall old kernels) and see whether this solves the problem.

[Alessandro Ghersi (alessandro-ghersi)]

@Till
I added your ppa and I updated the packages. I attach the trace

[Till Kamppeter (till-kamppeter)]

Alessandro, have you followed all the instructions in my comment

https://bugs.launchpad.net/ubuntu/jaunty/+source/linux/+bug/348316/comments/44

When you have really completed these instructions (deactivating AppArmor, blacklisting and unloading usblp), please post or attach the output of

lsusb
ls -l /dev/bus/usb/*/*
lsusb -vvv

and then take the strace again and attach it. Thanks. Tell also whether it prints or not.

[Alessandro Ghersi (alessandro-ghersi)]

lsusb
Bus 002 Device 003: ID 04b8:0811 Seiko Epson Corp. Stylus Photo RX620 all-in-one
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

ls -l /dev/bus/usb/*/*
crw-rw-r-- 1 root root 189, 0 2009-04-02 02:12 /dev/bus/usb/001/001
crw-rw-r-- 1 root root 189, 128 2009-04-02 02:12 /dev/bus/usb/002/001
crw-rw-r-- 1 root root 189, 130 2009-04-02 16:10 /dev/bus/usb/002/003
crw-rw-r-- 1 root root 189, 256 2009-04-02 02:12 /dev/bus/usb/003/001
crw-rw-r-- 1 root root 189, 384 2009-04-02 02:12 /dev/bus/usb/004/001
crw-rw-r-- 1 root root 189, 512 2009-04-02 02:12 /dev/bus/usb/005/001
crw-rw-r-- 1 root root 189, 640 2009-04-02 02:12 /dev/bus/usb/006/001
crw-rw-r-- 1 root root 189, 768 2009-04-02 02:12 /dev/bus/usb/007/001
crw-rw-r-- 1 root root 189, 896 2009-04-02 02:12 /dev/bus/usb/008/001
crw-rw-r-- 1 root root 189, 897 2009-04-02 02:12 /dev/bus/usb/008/002

I attach also lsusb -vvv. But, I have to do lsusb -vvv or sudo lsusb -vvv ?

[Alessandro Ghersi (alessandro-ghersi)]

Doesn't print.

[Till Kamppeter (till-kamppeter)]

Can you do the following:

chmod 666 /dev/bus/usb/*/*
cancel -a

and then follow the instructions of my previous comment again?

Anyone has already tried to boot an old kernel (Intrepid or older) to see whether printing works then?

[Till Kamppeter (till-kamppeter)]

One more important thing:

Do not turn off or unplug the printer between running the "sudo chmod 666 /dev/bus/usb/*/*" command and finishing to follow all the instructions.

[m.lp.ql.m (mteixeira-berkeley)]

Trying to print on a Epson Stylus Photo R260 from a Dell D620. FWIW, I just tried printing with the 2.6.28.3-rt kernel, and it still didn't work.

[Till Kamppeter (till-kamppeter)]

Thanks, m.lp.ql.m, seems to be that all 2.6.28 kernels have the problem.

Can someone boot Jaunty with an Intrepid (or older Kernel), version 2.6.27 or older?

[Alessandro Ghersi (alessandro-ghersi)]

I did this:

sudo chmod 666 /dev/bus/usb/*/*
cancel -a
sudo chmod 755 /usr/lib/cups/backend/usb
ps auxwww | grep '^lp '
sudo strace -o /tmp/trace -fv -p 12220

It doesn't work.

[Alessandro Ghersi (alessandro-ghersi)]

ls -l /dev/bus/usb/*/*
crw-rw-rw- 1 root root 189, 0 2009-04-02 23:21 /dev/bus/usb/001/001
crw-rw-rw- 1 root root 189, 128 2009-04-02 23:21 /dev/bus/usb/002/001
crw-rw-rw- 1 root root 189, 130 2009-04-03 02:03 /dev/bus/usb/002/003
crw-rw-rw- 1 root root 189, 256 2009-04-02 23:21 /dev/bus/usb/003/001
crw-rw-rw- 1 root root 189, 384 2009-04-02 23:21 /dev/bus/usb/004/001
crw-rw-rw- 1 root root 189, 512 2009-04-02 23:21 /dev/bus/usb/005/001
crw-rw-rw- 1 root root 189, 640 2009-04-02 23:21 /dev/bus/usb/006/001
crw-rw-rw- 1 root root 189, 768 2009-04-02 23:21 /dev/bus/usb/007/001
crw-rw-rw- 1 root root 189, 896 2009-04-02 23:21 /dev/bus/usb/008/001
crw-rw-rw- 1 root root 189, 897 2009-04-02 23:21 /dev/bus/usb/008/002

[John Vivirito (gnomefreak)]

On 04/02/2009 08:02 PM, Alessandro Ghersi wrote:
> I did this:
>
> sudo chmod 666 /dev/bus/usb/*/*
> cancel -a
> sudo chmod 755 /usr/lib/cups/backend/usb
> ps auxwww | grep '^lp '
> sudo strace -o /tmp/trace -fv -p 12220
>
> It doesn't work.
>
> ** Attachment added: "trace"
> http://launchpadlibrarian.net/24729052/trace
>
Does Till's package in the PPA fix this issue?

--
Sincerely Yours,
    John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246

"How can i get lost, if i have no where to go"
    -- Metallica from Unforgiven III

[Alessandro Ghersi (alessandro-ghersi)]

John, no it doesn't

[Leann Ogasawara (leannogasawara)]

As Till has previously mentioned, can anyone who experiences this issue with a 2.6.28 Jaunty kernel also test a 2.6.27 Intrepid kernel? It would be great to confirm if this is indeed a kernel related regression. Thanks.

[Facundo Batista (facundo)]

Hi! I installed the PPA's package and followed the instructions in comment #44.

I tried to add the printer, but the system didn't found it! (System -> Administration -> Printers .... "New").

I unplugged it:

$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0d8c:0201 C-Media Electronics, Inc. CM6501
Bus 002 Device 002: ID 056a:0065 Wacom Co., Ltd
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Then replugged it:

$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 022: ID 03f0:3d17 Hewlett-Packard
Bus 002 Device 003: ID 0d8c:0201 C-Media Electronics, Inc. CM6501
Bus 002 Device 002: ID 056a:0065 Wacom Co., Ltd
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

It even appears in the /dev/bus/usb...

$ ls -l /dev/bus/usb/*/*
crw-rw-r-- 1 root root 189, 0 2009-03-31 10:56 /dev/bus/usb/001/001
crw-rw-r-- 1 root root 189, 128 2009-03-31 10:56 /dev/bus/usb/002/001
crw-rw-r-- 1 root root 189, 129 2009-03-31 10:56 /dev/bus/usb/002/002
crw-rw-r-- 1 root root 189, 130 2009-03-31 10:56 /dev/bus/usb/002/003
crw-rw----+ 1 lp lp 189, 149 2009-04-03 12:13 /dev/bus/usb/002/022

(full "lsusb -vvv" attached)

I also tried setting "chmod 666" to the printer:

$ ls -l /dev/bus/usb/*/*
crw-rw-r-- 1 root root 189, 0 2009-03-31 10:56 /dev/bus/usb/001/001
crw-rw-r-- 1 root root 189, 128 2009-03-31 10:56 /dev/bus/usb/002/001
crw-rw-r-- 1 root root 189, 129 2009-03-31 10:56 /dev/bus/usb/002/002
crw-rw-r-- 1 root root 189, 130 2009-03-31 10:56 /dev/bus/usb/002/003
crw-rw-rw-+ 1 lp lp 189, 149 2009-04-03 12:14 /dev/bus/usb/002/022

But still not working.

Note that the problem now is not that I print and nothing happens, now I can not even add the printer!

[Till Kamppeter (till-kamppeter)]

Facundo Batista, have you followed ALL instructions in

https://bugs.launchpad.net/ubuntu/jaunty/+source/cups/+bug/348316/comments/44

especially deactivating AppArmor?

[Till Kamppeter (till-kamppeter)]

It looks very much like a kernel issue, as up to now all CUPS backends for USB, independent whether based on libusb or the usblp kernel module show the problem: standard USB backend, USB backend of CUPS 1.4, HPLIP backend, HAL backend.

So please try booting your Jaunty with an Intrepid kernel. Thanks.

[Steve Beattie (sbeattie)]

Hi Till,

I am able to reproduce the problem with a system installed with today's alt image (20090403) and a brother HL5250-DN; usb_printer /dev/usb/lp0 reports:

  GET_DEVICE_ID string:
  MFG:Brother;CMD:PJL,PCL,PCLXL,POSTSCRIPT;MDL:HL-5250DN series;CLS:PRINTER;

If I plug in the printer via usb and let the autodetection set up the print queue, printing via the usb:// device URI fails as described by the above (Printer 'HL-5250-DN-series' May Not Be Connected). However, if I then go into the printer admin configuration, delete the printer, re-add it, and print via the usb:// device URI, it prints.

  [ubuntu ~ ]$ lpinfo -v
  network socket
  network beh
  direct hal:///org/freedesktop/Hal/devices/usb_device_4f9_2b_J7J272419_if0_printer_noserial
  network socket://192.168.1.150
  direct usb://Brother/HL-5250DN%20series
  direct hpfax
  direct hp
  network http
  network ipp
  network lpd
  direct parallel:/dev/lp0
  direct scsi
  serial serial:/dev/ttyS0?baud=115200
  serial serial:/dev/ttyS1?baud=115200
  network smb

  [ubuntu ~ ]$ lsusb
  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 006: ID 04f9:002b Brother Industries, Ltd Printer
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

lsusb -vvv output attached; there's no difference in the working/non-working situation

There's also no difference when the printer works and when it doesn't work in the permissions of /dev/bus/usb/*/*/; in either situation it looks like:

  [ubuntu ~ ]$ ls -l /dev/bus/usb/*/*
  crw-rw-r-- 1 root root 189, 0 2009-04-03 13:03 /dev/bus/usb/001/001
  crw-rw-r-- 1 root root 189, 128 2009-04-03 13:03 /dev/bus/usb/002/001
  crw-rw-r-- 1 root root 189, 134 2009-04-03 13:09 /dev/bus/usb/002/007

[Steve Beattie (sbeattie)]

Attaching the combined /var/log/cups/error_log{.O} after setting cupsctl LogLevel=debug and then first attaching the printer, failing to print, deleting the printer, re-adding the printer, and printing the test page successfully.

[Steve Beattie (sbeattie)]

Here the output of strace -v -s 128 -F attaching to the cupsd process and then reproducing the print failure (I'd let the system autodetect the printer first, before starting the strace).

[Steve Beattie (sbeattie)]

Here's the output of strace -v -s 128 -F attaching to the cupsd process and then succesfully printing the test page, after having deleted the printer from the admin interface and then re-adding it.

[Steve Beattie (sbeattie)]

I should point out that I also get almost exactly the same behavior -- autodetect fails to print; deleting and setting up workls -- while running the exact same desktop booted with the following kernel:

  $ cat /proc/version_signature
  Ubuntu 2.6.27-11.27-generic

I am not convinced this is a kernel issue.

[Steve Beattie (sbeattie)]

Also, I note that every printer I've looked at listed in this bug has a space (%20) encoded in the usb:// URI as reported by lpinfo -v. Martin, you said your printer was working correctly; does yours also contain a space? Is it possible we're hitting another of the "hal converting whitespaces into something else" issues (a la bug 347370) and that's breaking printing autodetection here?

Thanks. Sorry for all the noise.

[Facundo Batista (facundo)]

Ignore my assertion in comment #64, about not seeing the printer anymore (I installed only the cups package from the PPA, forgot the libcups one).

With both packages, I saw the printer, and the behaviour changed: now it gets stuck trying to print: I send a test page to print, it's never printed, but now it also doesn't disappear from the queue.

Furthermore, a process takes all the processor: "usb://HP/HP%20Laserjet.... 152 facundo Test Page 1 job-...

I want to try with an older kernel, but I need to install it (the upgrade to Jaunty removed the old kernels).

[Steve Langasek (vorlon)]

I have an HP PSC750 here (USB-connected) which is working fine under jaunty. I have the hplip backend installed, but the printer is configured to use the USB backend:

  direct usb://HP/PSC%20750?serial=MY2ASD4157WB

as verified in the Device URI field of system-config-printer.

[Till Kamppeter (till-kamppeter)]

Steve Langasek, the problem you are describing is another problem. Please report as separate bug for it. But please tell anyway whether your printer prints. Does it print with the "usb:/..." URI? Does it print if you create the printer via the "New" button in system-config-printer and taking care that the HPLIP URI gets selected?

What is the output of "lpinfo -v" for you?

[Till Kamppeter (till-kamppeter)]

I can reproduce the problem now, but not with print queue which got created by hal-cups-utils or system-confiog-printer.

I have the HP PhotoSmart C8100:

till@till-laptop:~/ghostscript/gpl/testfiles$ /usr/lib/cups/backend/usb 2>/dev/null
direct usb://HP/Photosmart%20C8100%20series?serial=MY7B5F70P704YH&interface=1 "HP Photosmart C8100 series" "HP Photosmart C8100 series" "MFG:HP;MDL:Photosmart C8100 series;CMD:MLC,PCL,PML,DW-PCL,DESKJET,DYN;1284.4DL:4d,4e,1;CLS:PRINTER;DES:L2526;SN:MY7B5F70P704YH;S:038088C4840010210078cb0000041b8001b46b8002b47b8006444b8006448b8005a45b80038;Z:0102,05000009016a81013241013241013241013241013241,0600,070000000000000000000000000000,0b000000000000000097ce97e9000097e99804000097ea981a000097e89812000097e99811000097e99809,0c0;" ""

Now I do not take the device URI reported by the backend in discovery mode (no arguments) but intendedly mistype it when creating a queue (in the example I clone the PPD file from my auto-created working queue for the printer):

till@till-laptop:~/ghostscript/gpl/testfiles$ lpadmin -p test -v usb://HP/Photosmart_C8100_series?serial=MY7B5F70P704YH -E -P /etc/cups/ppd/Photosmart_C8100_series.ppd

lpadmin exits without errors (it should give an error for the invalid URI) and creates the queue. If I print into this queue I get exactly the behavior as reported here.

This gives me the impression that hal-cups-utils "mistypes" USB URIs in certain cases.

So, Steve Beattie, to see whether the problem is really as you and me assumed, please post the printer URI which you get by Plug'n'Print and which does not work and the URI which you get for a queue created with system-config-printer via the "New" button. Use system-config-printer or "lpstat -v" to display the URIs of your print queues.

[Till Kamppeter (till-kamppeter)]

Possible fix committed to hal-cups-utils upstream, GIT rev 885556d.

[Till Kamppeter (till-kamppeter)]

I have uploaded hal-cups-utils_0.6.19+git20090217-0ubuntu6 which does not create CUPS URIs on its own but runs the USB relevant CUPS backends in discovery mode (without arguments) and takes the URIs from there. So it is assured that the URIs in the auto-generated queues are correct.

I have done the upload already yesterday night, buit it seems that the upload server is down as the package did not arrive up to now.

Please test as soon as you get the new package and tell whether it solves this problem.

[Launchpad Janitor (janitor)]

This bug was fixed in the package hal-cups-utils - 0.6.19+git20090217-0ubuntu6

---------------
hal-cups-utils (0.6.19+git20090217-0ubuntu6) jaunty; urgency=low

  * debian/patches/20_do-not-create-cups-uris-artificially.patch: Do not
    create CUPS URIs artificially any more, but always use the URIs
    reported by the CUPS backends in discovery mode, as if the queues are
    set up with slightly different URIs, the printers get not identified
    on the USB and the jobs get stuck (LP: #348316).

 -- Till Kamppeter <email address hidden> Sat, 4 Apr 2009 23:59:59 +0200

[Martin Pitt (pitti)]

Hello Till,

just wanted to say a big "thank you!" for tracking this down so
thoroughly and patiently. Kudos!

[andschuster (andreas-schuster2)]

I installed the new hal-cups-utils package. Now hptoolbox can see the status of the printer. But printing still doesn't work. As before there is a communication error if I try to print an nothing happens.

[Martin Pitt (pitti)]

andschuster [2009-04-05 15:52 -0000]:
> I installed the new hal-cups-utils package. Now hptoolbox can see the
> status of the printer. But printing still doesn't work. As before there
> is a communication error if I try to print an nothing happens.

Did you remove and reinstall your printer after the upgrade? The
upgrade cannot fix existing printer queues, just newly created ones.

[Till Kamppeter (till-kamppeter)]

Everyone who has the problem, please do the following test:

1. Updatee hal-cups-utils (or do a full system update).

2. If you are running with an old kernel from previous tests, reboot to get back to the current Jaunty kernel.

3. Remove ALL queues for your USB printer(s) (for example with system-config-printer.

4. Power-cycle or unplug and plufg again your USB printer's

5. Wait the printer configuration window(s) of system-config-printer popping up, one per printer.

6. Click the "Print test page" button(s) in the configuration window(s).

7. Your printer(s) print(s) a test page? If so, all is OK. Please report here so that we can close the kernel task.

[tibber (tibber)]

This solved for me, finally. Thx. Btw I had to restart cups between steps 3 and 4.
Brother dcp-135c, kubuntu, (the print queue was deleted w/ cups web interface)

[fewyun (fewyun)]

Did full system update on 9.04 beta amd64. Rebooted. Still showed up as "Your printer may not be connected" after trying to print a document.

Then, "sudo apt-get install cups* foomatic*" as mentioned above and it worked.

(Epson CX3810)

[Steve Beattie (sbeattie)]

Till, updating hal-cups-utils, deleting the queue, and replugging the
printer in via usb now results in a printer that prints successfully.
Great work, thanks so much!

[Till Kamppeter (till-kamppeter)]

Then it seems to be really fixed by the change in hal-cups-utils. Thank you for testing.

Steve Beattie, thank you for the hint with the problem only occuring for Plug'n'Print and not for printers set up with system-config-printer

https://bugs.edge.launchpad.net/ubuntu/jaunty/+source/hal-cups-utils/+bug/348316/comments/68

and with the URIs

https://bugs.edge.launchpad.net/ubuntu/jaunty/+source/hal-cups-utils/+bug/348316/comments/72

this lead me to hal-cups-utils.

Closing kernel task.

[andschuster (andreas-schuster2)]

I followed Till's advice. If I tried to print a testpage and did "lpq" I saw that my Laserjet 1300 ist ready and printing, but nothing happened. In syslog I found the following message:

6 10:13:08 darkstar hp_LaserJet_1300?serial=00CNBD032941: prnt/backend/hp.c 676: INFO: open device failed stat=12; will retry in 30 seconds...

Starting thena hp-toolbox I got an "communication error".

[andschuster (andreas-schuster2)]

I changed the backend to "hal". Result is the same.

[Till Kamppeter (till-kamppeter)]

andschuster, is the printer URI which your printer gets by the automatic setuo when plugging it ("lpstat -v") exactly the same as one of the URIs suggested by the CUPS backends ("lpinfo -v")? In this case your problem is not the one described by this bug. Please open a new bug on it.

[andschuster (andreas-schuster2)]

root@darkstar:~# lpstat -v
Gerät für hp-LaserJet-1300: hp:/usb/hp_LaserJet_1300?serial=00CNBD032941
Gerät für PDF: cups-pdf:

root@darkstar:~# lpinfo -v
network socket
network beh
file cups-pdf:/
direct hal
direct hpfax
direct hp
network http
network ipp
network lpd
direct scsi
serial serial:/dev/ttyS0?baud=115200
serial serial:/dev/ttyS1?baud=115200
network smb

So the cups backends don't seem to find the printer at all. A new bug?

[Till Kamppeter (till-kamppeter)]

Does "lsusb -vvv" show your printer? Please attach the output.

After having tested this please check the connection of the printer (bad USB cable, USB hub, ...).

[andschuster (andreas-schuster2)]

The printer works fine in Intrepid installed on another partition of the same computer - so there can't be any physical problems. lsusb shows my printer:

Bus 002 Device 017: ID 03f0:1017 Hewlett-Packard LaserJet 1300

[andschuster (andreas-schuster2)]

I filed a new bug: 356142

[Till Kamppeter (till-kamppeter)]

bug 356142

[John Vivirito (gnomefreak)]

On 04/05/2009 02:58 PM, Till Kamppeter wrote:
> Everyone who has the problem, please do the following test:
>
> 1. Updatee hal-cups-utils (or do a full system update).
>
> 2. If you are running with an old kernel from previous tests, reboot to
> get back to the current Jaunty kernel.
>
> 3. Remove ALL queues for your USB printer(s) (for example with system-
> config-printer.
>
> 4. Power-cycle or unplug and plufg again your USB printer's
>
> 5. Wait the printer configuration window(s) of system-config-printer
> popping up, one per printer.
>
> 6. Click the "Print test page" button(s) in the configuration window(s).
>
> 7. Your printer(s) print(s) a test page? If so, all is OK. Please report
> here so that we can close the kernel task.
>
once i get to step 5 the printer window doesn't come up unless i run
system-config-printer but than still doesn't print a test page it still
says not connected. i tried rebooting unpluging USB and cycling the
print on/off a few times. Info below:

Distributor ID: Ubuntu
Description: Ubuntu jaunty (development branch)
Release: 9.04
Codename: jaunty

gnomefreak@Development:~$ policy hal-cups-utils
hal-cups-utils:
  Installed: 0.6.19+git20090217-0ubuntu6
  Candidate: 0.6.19+git20090217-0ubuntu6
  Version table:
 *** 0.6.19+git20090217-0ubuntu6 0
        500 http://gb.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

--
Sincerely Yours,
    John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246

"How can i get lost, if i have no where to go"
    -- Metallica from Unforgiven III

[John Vivirito (gnomefreak)]

On 04/05/2009 02:58 PM, Till Kamppeter wrote:
> Everyone who has the problem, please do the following test:
>
> 1. Updatee hal-cups-utils (or do a full system update).
>
> 2. If you are running with an old kernel from previous tests, reboot to
> get back to the current Jaunty kernel.
>
> 3. Remove ALL queues for your USB printer(s) (for example with system-
> config-printer.
>
> 4. Power-cycle or unplug and plufg again your USB printer's
>
> 5. Wait the printer configuration window(s) of system-config-printer
> popping up, one per printer.
>
> 6. Click the "Print test page" button(s) in the configuration window(s).
>
> 7. Your printer(s) print(s) a test page? If so, all is OK. Please report
> here so that we can close the kernel task.
>
sorry forgot to add printer in
HP photo smart 7850

--
Sincerely Yours,
    John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246

"How can i get lost, if i have no where to go"
    -- Metallica from Unforgiven III

[Till Kamppeter (till-kamppeter)]

John, can you please supply:

1. The output of "lpstat -v"

2. The output of "lpinfo -v"

3. The output of "lsusb"

4. The output of "lsusb -vvv"

5. The output of "ls -l /dev/bus/usb/*/* /dev/usb/lp* /dev/usblp*"

If the URI assigned to the printer by the automatic setup (result of 1.) is the same as one of the URIs listed by CUPS (result of 2.), boot the Intrepid kernel (but still running the Jaunty OS) and see whether your printer works then.

[Facundo Batista (facundo)]

With the system fully updated I can't print, and I don't even see the printer (Till, if I downgrade cups to your PPA version, I see the printer again... it still doesn't print, but I least I see it).

I attach all the info you're asking to John in the previous comment, plus the result (none) of /usr/lib/cups/backend/usb.

[Till Kamppeter (till-kamppeter)]

If someone has used the CUPS package from my PPA and after that has done a system update (getting CUPS 1.3.9-17), he must remove the blacklist entry against the usblp module in /etc/modprobe.d/blacklist.conf again. Otherwise CUPS will not detect non-HP USB printers at all.

[Facundo Batista (facundo)]

Thanks Till! I removed the blacklist and loaded the module.

Now I see the printer, but there's no printing at all when sending the test page (it says it's printing, the job gets into the queue, disappears from there, and I even get a notification that the job was printed), but no printing at all.

Attached here are all the normal info (seeing the permissions in /dev stuff, I even tried relaxing the permission in the devices, but the behaviour is the same).

[Till Kamppeter (till-kamppeter)]

Facundo Batista, your printer is identifying itself as an HP LaserJet P1002. This model is not (yet) known to HPLIP (see /usr/share/hplip/data/models/models.dat) nor to foo2zjs (see output of "getweb"). Also "lpinfo -m" does not show a suitable PPD or driver for this model. As the other models of the HP LaserJet P series all need a firmware file to be loaded from the computer into the printer this one probably needs also one but the file is not yet available for download. So you are probably out of luck with this printer for some months until one of HPLIP or foo2zjs starts to support this model.

Were you able to print on Linux (Intrepid, non-Ubuntu distro, ...) wit this printer? If yes, with which driver?

[John Vivirito (gnomefreak)]

Till,

gnomefreak@Development:~$ lpstat -v
device for Photosmart-7800-series: usb://HP/Photosmart%207800%20Series?serial=MY59L330SQ04H9
gnomefreak@Development:~$ lpinfo -v
network socket
network beh
direct hpfax
direct hal:///org/freedesktop/Hal/devices/usb_device_3f0_c002_MY59L330SQ04H9_if0_printer_MY59L330SQ04H9
direct usb://HP/Photosmart%207800%20series?serial=MY59L330SQ04H9
direct hp:/usb/Photosmart_7800_series?serial=MY59L330SQ04H9
network http
network ipp
network lpd
direct parallel:/dev/lp0
direct scsi
serial serial:/dev/ttyS0?baud=115200
serial serial:/dev/ttyS1?baud=115200
network smb
gnomefreak@Development:~$ lsusb
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 007: ID 03f0:c002 Hewlett-Packard Photosmart 7800 Series
Bus 001 Device 003: ID 09da:0006 A4 Tech Co., Ltd Optical Mouse WOP-35 / Trust 450L Optical Mouse
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
gnomefreak@Development:~$ lsusb -vvv

Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 9 Hub
  bDeviceSubClass 0 Unused
  bDeviceProtocol 0 Full speed (or root) hub
  bMaxPacketSize0 64
  idVendor 0x1d6b Linux Foundation
  idProduct 0x0001 1.1 root hub
  bcdDevice 2.06
  iManufacturer 3
  iProduct 2
  iSerial 1
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 25
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xe0
      Self Powered
      Remote Wakeup
    MaxPower 0mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 1
      bInterfaceClass 9 Hub
      bInterfaceSubClass 0 Unused
      bInterfaceProtocol 0 Full speed (or root) hub
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0002 1x 2 bytes
        bInterval 255
can't get hub descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)

Bus 001 Device 007: ID 03f0:c002 Hewlett-Packard Photosmart 7800 Series
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 8
  idVendor 0x03f0 Hewlett-Packard
  idProduct 0xc002 Photosmart 7800 Series
  bcdDevice 1.00
  iManufacturer 1 HP
  iProduct 2 Photosmart 7800 series
  iSerial ...

[TJ (tj)]

I've not seen any improvement here using:

apt-cache policy cups
cups:
  Installed: 1.3.9-17
  Candidate: 1.3.9-17

I didn't try the PPA package or make any system changes.

The original issue was failure to connect via Bluetooth so I switched to the USB cable expecting that would solve the problem, only to meet this new one! The printer is automatically detected upon connection and system-config-printer appears and offers a test-page print, which then doesn't start, with the status reporting "Printer ... may not be connected" whilst the job shows as "processing".

uname -a
Linux hephaestion 2.6.28-11-generic #40-Ubuntu SMP Fri Apr 3 17:39:41 UTC 2009 x86_64 GNU/Linux

lpstat -v
device for DESKJET-995C: hp:/usb/deskjet_995c?serial=MY19P1C13F0L

lpinfo -v
network socket
network beh
direct hal
direct hpfax
direct hp
network http
network ipp
network lpd
direct scsi
network smb

lsusb -s 1:14
Bus 001 Device 014: ID 03f0:5004 Hewlett-Packard DeskJet 995c

ls -l /dev/bus/usb/*/* /dev/usb/lp* /dev/usblp*
ls: cannot access /dev/usb/lp*: No such file or directory
ls: cannot access /dev/usblp*: No such file or directory
crw-rw-r-- 1 root vm 189, 0 2009-04-06 15:50 /dev/bus/usb/001/001
crw-rw-r-- 1 root vm 189, 3 2009-04-06 15:50 /dev/bus/usb/001/004
crw-rw-r-- 1 root vm 189, 4 2009-04-06 15:50 /dev/bus/usb/001/005
crw-rw-r-- 1 root vm 189, 5 2009-04-06 16:40 /dev/bus/usb/001/006
crw-rw-r-- 1 root vm 189, 6 2009-04-06 16:40 /dev/bus/usb/001/007
crw-rw-r-- 1 root vm 189, 7 2009-04-06 16:40 /dev/bus/usb/001/008
crw-rw-r-- 1 root vm 189, 8 2009-04-06 16:40 /dev/bus/usb/001/009
crw-rw-r-- 1 root vm 189, 9 2009-04-06 16:40 /dev/bus/usb/001/010
crw-rw-r-- 1 root vm 189, 10 2009-04-06 16:40 /dev/bus/usb/001/011
crw-rw-r-- 1 root vm 189, 11 2009-04-06 16:40 /dev/bus/usb/001/012
crw-rw-r-- 1 root vm 189, 12 2009-04-06 16:51 /dev/bus/usb/001/013
crw-rw-r--+ 1 root vm 189, 13 2009-04-06 16:40 /dev/bus/usb/001/014
crw-rw-r--+ 1 root vm 189, 14 2009-04-06 16:40 /dev/bus/usb/001/015
crw-rw-r-- 1 root vm 189, 15 2009-04-06 16:40 /dev/bus/usb/001/016
crw-rw-r-- 1 root vm 189, 128 2009-04-06 15:50 /dev/bus/usb/002/001
crw-rw-r-- 1 root vm 189, 256 2009-04-06 15:50 /dev/bus/usb/003/001
crw-rw-r-- 1 root vm 189, 384 2009-04-06 15:50 /dev/bus/usb/004/001
crw-rw-r-- 1 root vm 189, 385 2009-04-06 15:50 /dev/bus/usb/004/002
crw-rw-r-- 1 root vm 189, 512 2009-04-06 15:50 /dev/bus/usb/005/001

/var/log/syslog shows:

Apr 6 16:40:25 hephaestion hal_lpadmin: PPD: drv:///hpijs.drv/hp-deskjet_995c-hpijs.ppd; Status: 0
Apr 6 16:40:25 hephaestion hal_lpadmin: Added printer DESKJET-995C
Apr 6 16:40:33 hephaestion deskjet_995c?serial=MY19P1C13F0L: io/hpmud/musb.c 135: unable get_string_descriptor -1: Operation not permitted
Apr 6 16:40:33 hephaestion deskjet_995c?serial=MY19P1C13F0L: io/hpmud/musb.c 603: invalid product id string ret=-1
Apr 6 16:40:33 hephaestion deskjet_995c?serial=MY19P1C13F0L: io/hpmud/musb.c 135: unable get_string_descriptor -1: Operation not permitted
Apr 6 16:40:33 hephaestion deskjet_995c?serial=MY19P1C13F0L: io/hpmud/musb.c 603: invalid product id string ret=-1
Apr 6 16:40:33 hephaestion deskjet_995c?serial=MY1...

[andschuster (andreas-schuster2)]

TJ that looks like my problem! See also bug 356142.

[Steve Beattie (sbeattie)]

John,

> I am unable to boot to Intrepid kernel on Jaunty at this time i have
> removed them normal for me. Let me know if i need to and i will install
> it if its still in Jaunty, Also let me know the version as i have
> forgotten the Intrepid version of kernel.I dont have access to my
> Intrepid install this week.

You can find links to download the current intrepid kernel from
https://launchpad.net/ubuntu/intrepid/+package/linux-image-2.6.27-11-generic
You'll want to download the kernel package that matches your arch,
and then install with either:

  sudo dpkg -i linux-image-2.6.27-11-generic_2.6.27-11.27_i386.deb

or

  sudo dpkg -i linux-image-2.6.27-11-generic_2.6.27-11.27_amd64.deb'

and reboot into it.

[Till Kamppeter (till-kamppeter)]

TJ, all your /dev/bus/usb/*/* files including the one for the printer have "vm" group ownerships. Probably VMware or some other virtual machine software is overriding the UDEV rules which set the group ownership of the printer's file to "lp". So HPLIP (the preferred CUPS backend for your printer) cannot access the printer and your job hangs.

Report a bug against your virtual machine software.

[John Vivirito (gnomefreak)]

On 04/06/2009 12:34 PM, Steve Beattie wrote:
> John,
>
>> I am unable to boot to Intrepid kernel on Jaunty at this time i have
>> removed them normal for me. Let me know if i need to and i will install
>> it if its still in Jaunty, Also let me know the version as i have
>> forgotten the Intrepid version of kernel.I dont have access to my
>> Intrepid install this week.
>
> You can find links to download the current intrepid kernel from
> https://launchpad.net/ubuntu/intrepid/+package/linux-image-2.6.27-11-generic
> You'll want to download the kernel package that matches your arch,
> and then install with either:
>
> sudo dpkg -i linux-image-2.6.27-11-generic_2.6.27-11.27_i386.deb
>
> or
>
> sudo dpkg -i linux-image-2.6.27-11-generic_2.6.27-11.27_amd64.deb'
>
> and reboot into it.
>
with 2.6.27-11 kernel no change still says not connected.

--
Sincerely Yours,
    John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246

"How can i get lost, if i have no where to go"
    -- Metallica from Unforgiven III

[TJ (tj)]

On Mon, 2009-04-06 at 18:19 +0000, Till Kamppeter wrote:
> TJ, all your /dev/bus/usb/*/* files including the one for the printer
> have "vm" group ownerships. Probably VMware or some other virtual
> machine software is overriding the UDEV rules which set the group
> ownership of the printer's file to "lp". So HPLIP (the preferred CUPS
> backend for your printer) cannot access the printer and your job hangs.

Thanks for spotting that Till.

I did wonder but didn't spot anything obvious on that. The udev rule is
one needed to allow raw USB devices to be accessed by KVM/QEMU which
I've carried since Hardy.

Unfortunately the rule is 41-vm-usb.rules which will, as you noticed,
cancel out the 40-hplip/rules.

I've renamed the vm rule to 39- and the USB printing now works.

Now back to the original bluetooth bug!

[Peter Maunder (peter-maunder)]

Adding this coment in case it is useful.

I have also had the HP D7100 Photosmart ....... may not be connected problem. In my case I also had a Brother-HL-5250DN USB connected to my primary system, LAN connected to two other computers. The printers worked fine with Windows XP.
  I seem to have solved the problem by disconnecting the Brother USB connection and using the LAN instead and only allow the HP to be USB connected. I deleted all printers, rebooted and redefined them.
 I found that if I waited with both printers connected to the USB after about 25 minutes the HP would suddenly burst into life. Ubuntu 9.04 but had the same problem on 8.10. HPLIP 3.9.2, Device Manager Version 15.0 (Qt4)

[UsedBits (s-prinz-c)]

Bottom line: My system has no /dev/usb/lp0 and, therefore, I can't find a URI: entry to manually configure my HP LaserJet 4L.

lpinfo -v does not show my printer.

lsusb displays Bus 003 Device 005: ID 04b4:4100 Cypress Semiconductor Corp.

lsusb -v displays:

Bus 003 Device 005: ID 04b4:4100 Cypress Semiconductor Corp.
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 8
  idVendor 0x04b4 Cypress Semiconductor Corp.
  idProduct 0x4100
  bcdDevice 0.02
  iManufacturer 1
  iProduct 2 USB PRINT
  iSerial 0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 50
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 4
    bmAttributes 0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower 100mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 2
      bNumEndpoints 2
      bInterfaceClass 7 Printer
      bInterfaceSubClass 1 Printer
      bInterfaceProtocol 2 Bidirectional
      iInterface 0
      ** UNRECOGNIZED: 09 21 10 01 00 01 22 25 00
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x01 EP 1 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0008 1x 8 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
cannot read device status, Broken pipe (32)

HPLIP shows print jobs hitting queue and finishing, but nothing prints.

ls -la /dev/bus/usb/003/005 displays:
crw-rw---- 1 root lp 189, 260 2010-01-07 21:51 /dev/bus/usb/003/005

All I have under /dev/usb* are entries fo usbmon0 through usbmon5

Will work with y'all in continuing to fix, but you'll have to walk me through some of the more advanced procedures.

[Paul McQuesten (mcquesten)]

Hardy (8.04 LTS) with Brother MFC-7340 via USB

Followed many Brother printer fix HowTo-s (cannot remember all of them). Finally, this:
      sudo chmod a+w /dev/usb/lp0

lets me print (and scanning still works, too).

Question: Is it reasonable to have the printer world-writable? Should this be fixed some other way?

HTH