cups backends don't recognize printer URI

Bug #356142 reported by andschuster
2
Affects Status Importance Assigned to Milestone
cups (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: cups

After upgrading from Intrepid to Jaunty Beta the automatic construction of the device URI works well:

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:/

But the backends don't recognize the printer:

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

Printing doesn't work. If I try to start printing nothing happens. The printer is listed:

root@darkstar:~# lsusb
Bus 002 Device 005: ID 0bf8:100f Fujitsu Siemens Computers
Bus 002 Device 010: ID 1267:0103 Logic3 / SpectraVideo plc G-720 Keyboard
Bus 002 Device 009: ID 046d:c510 Logitech, Inc. Cordless Mouse
Bus 002 Device 008: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 002 Device 007: ID 046d:c03d Logitech, Inc. M-BT69a Pilot Optical Mouse
Bus 002 Device 006: ID 03f0:1017 Hewlett-Packard LaserJet 1300
Bus 002 Device 004: ID 07b8:e004 D-Link Corp. Mass Storage Device
Bus 002 Device 003: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub / D-Link DUB-H4 USB 2.0 Hub
Bus 002 Device 002: ID 05e3:0605 Genesys Logic, Inc. USB 2.0 Hub [ednet]
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
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 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 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 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Using the same printer with Intrepid installed on the same computer printing works well and the URI automatically constructed is the same reported by the backends.

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

Can you at first do a full system update? This should pull in CUPS 1.3.9-17.

If this still does not help, can you please post the output of

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

Revision history for this message
andschuster (andreas-schuster2) wrote :

I already did a full upgrade.

After rebooting "lpstat -v" gives the same listing as above, but "lpinfo -v" now shows (the difference to the situation above is that the printer was turned on during booting):

root@darkstar:~# 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

That means that there are two different URIs.

I attached the output of "lsusb -vvv" as lsusbvvv.txt

root@darkstar:~# ls -l /dev/bus/usb/*/*
crw-rw-r-- 1 root root 189, 0 2009-04-06 12:05 /dev/bus/usb/001/001
crw-rw-r-- 1 root root 189, 128 2009-04-06 12:05 /dev/bus/usb/002/001
crw-rw-r-- 1 root root 189, 129 2009-04-06 12:05 /dev/bus/usb/002/002
crw-rw-r-- 1 root root 189, 130 2009-04-06 12:05 /dev/bus/usb/002/003
crw-rw-r-- 1 root root 189, 131 2009-04-06 12:05 /dev/bus/usb/002/004
crw-rw-r-- 1 root root 189, 132 2009-04-06 12:05 /dev/bus/usb/002/005
crw-rw-r-- 1 root root 189, 133 2009-04-06 12:05 /dev/bus/usb/002/006
crw-rw-r-- 1 root root 189, 134 2009-04-06 12:05 /dev/bus/usb/002/007
crw-rw-r-- 1 root root 189, 135 2009-04-06 12:06 /dev/bus/usb/002/008
crw-rw-r-- 1 root root 189, 136 2009-04-06 12:05 /dev/bus/usb/002/009
crw-rw-r--+ 1 root lp 189, 137 2009-04-06 12:05 /dev/bus/usb/002/010
crw-rw-r-- 1 root root 189, 256 2009-04-06 12:05 /dev/bus/usb/003/001
crw-rw-r-- 1 root root 189, 384 2009-04-06 12:05 /dev/bus/usb/004/001
crw-rw-r-- 1 root root 189, 512 2009-04-06 12:05 /dev/bus/usb/005/001
crw-rw-r-- 1 root root 189, 640 2009-04-06 12:05 /dev/bus/usb/006/001
crw-rw-r-- 1 root root 189, 768 2009-04-06 12:05 /dev/bus/usb/007/001
crw-rw-r-- 1 root root 189, 896 2009-04-06 12:05 /dev/bus/usb/008/001

root@darkstar:~# ls -l /dev/usb/lp*
crw-rw----+ 1 root lp 180, 0 2009-04-06 12:00 /dev/usb/lp0

Revision history for this message
TJ (tj) wrote :

Apparently I have a system experiencing the same cause, originally reported via bug #348316 "Printer (HWModel Name) May Not Be Connected".

The printer is connected to a remote hub. The remote hub is never connected during start-up for operational reasons.

Repeat of information posted to the other bug:

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/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

Monitoring udev whilst connecting *just* the printer directly to the PC shows the usb/lp* node being removed immediately after it is added. I've attached the full udevadm log, but here's the 'interesting' bit:

UEVENT[1239040462.833940] remove /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/usb/lp0 (usb)
UDEV_LOG=3
ACTION=remove
DEVPATH=/devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/usb/lp0
SUBSYSTEM=usb
SEQNUM=2140
MAJOR=180
MINOR=0

UEVENT[1239040462.834010] remove /class/usb (class)
UDEV_LOG=3
ACTION=remove
DEVPATH=/class/usb
SUBSYSTEM=class
SEQNUM=2141

UDEV [1239040462.835168] remove /class/usb (class)
UDEV_LOG=3
ACTION=remove
DEVPATH=/class/usb
SUBSYSTEM=class
SEQNUM=2141

UDEV [1239040462.839525] remove /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/usb/lp0 (usb)
UDEV_LOG=3
ACTION=remove
DEVPATH=/devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/usb/lp0
SUBSYSTEM=usb
SEQNUM=2140
DEVNAME=/dev/usb/lp0
MAJOR=180
MINOR=0
DEVLINKS=/dev/char/180:0 /dev/usblp0

Revision history for this message
andschuster (andreas-schuster2) wrote :

Do you need further informations?

Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. Ubuntu 9.04 is no longer supported, it would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect -p cups 356142 and other relevant information.

Changed in cups (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for cups (Ubuntu) because there has been no activity for 60 days.]

Changed in cups (Ubuntu):
status: Incomplete → Expired
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.