Re: cups on wheezy problem
On Wed, 10 Aug 2011 12:57:13 -0400, Wayne Topa wrote:
> On 08/10/2011 10:27 AM, Camaleón wrote:
>> And "ls -l /dev/usblp1" returns...?
> ls -l /dev/usb/lp1
Well, your log said "usblp1":
Aug 8 13:52:38 dj kernel: [14830.034204] usblp1: USB Bidirectional printer dev 3 if 0 alt 1 proto 2 vid 0x067B pid 0x2305
>> And "ls -l /usr/lib/cups/backend/" shows what available backends?
> As of this mornings upgrade shows the same as below but includes usb
How voluble is this USB thingy.
>>> Why would no one else be having this problem? Make no sense to me.
>> I would review the current open bugs for cups:
> I don't usually go to the bugs page on debian.org directly but by the
> Google links when I am searching for the 'error of the day' :-(
> I do however, maybe wrongly, rely on listbugs so here is what it has
> been saying for days now.
> Fixed: cups/1.4.8-1
> I am running 4.8-2 and an attempt to downgrade reports it could not find
> An attempt to print shows
> Aug 10 12:28:13 dj kernel: [ 1029.762136] usb 3-1: USB disconnect, device number 2
> Aug 10 12:28:13 dj kernel: [ 1029.762391] usblp1: removed
> Aug 10 12:28:19 dj kernel: [ 1036.244036] usb 3-1: new full speed USB device number 3 using ohci_hcd
> Aug 10 12:28:19 dj kernel: [ 1036.411106] usb 3-1: New USB device found, idVendor=067b, idProduct=2305
> Aug 10 12:28:19 dj kernel: [ 1036.411115] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> Aug 10 12:28:19 dj kernel: [ 1036.411122] usb 3-1: Product: IEEE-1284 Controller
> Aug 10 12:28:19 dj kernel: [ 1036.411127] usb 3-1: Manufacturer: Prolific Technology Inc.
> Aug 10 12:28:19 dj kernel: [ 1036.422224] usblp1: USB Bidirectional printer dev 3 if 0 alt 1 proto 2 vid 0x067B pid 0x2305
> Aug 10 12:28:19 dj mtp-probe: checking bus 3, device 3: "/sys/devices/pci0000:00/0000:00:12.0/usb3/3-1"
> Aug 10 12:28:20 dj mtp-probe: bus: 3, device: 3 was not an MTP device
That's the same log report you got before, right? Nothing has changed.
> There is a 'something ?' causing weird mtp-probe call. I'll keep
> looking to see if I can figure out just what.
> Funny thing is that the same thing is happening on Sid. I wonder how
> this got to wheezy in this condition??
One of the Debian bugs I posted before links to this one (directly to CUPS):
At least you are not alone on this...