[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: cups on wheezy problem

On 08/08/2011 01:10 PM, Camaleón wrote:
On Mon, 08 Aug 2011 13:00:17 -0400, Wayne Topa wrote:

On 08/08/2011 11:19 AM, Camaleón wrote:


    udevd[17007]: failed to execute '/lib/udev/mtp-probe' 'mtp-probe
/sys/devices/pci0000:00/0000:00:12.0/usb3/3-1 3 3': No such file or

udevd errors exist in wheezy and sid but the only related errors on
Google are from 2004.  These errors showed up here when /run was
introduced IIRC.

Has anyone solved this or know of a fix?

Do you think Cups is failing because of that? :-?

That meaning cups or udev?

If udev/udevd can't identify the that the printer is there, yes I think
that cups has no way to print so is not at fault.

I will re-do the question... Do you think the above error has something
to do with udev/kernel not detecting the printer?

It is not detecting the usb to parallel interface, yes.

"mtp-probe" sounds to me like another thing (used on/for USB media

That error was from wheezy when i plugged in the usb printer cable.

Here is what I see in Squeeze when I plug in that cable:
Aug 8 13:52:38 dj kernel: [14830.023088] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Aug 8 13:52:38 dj kernel: [14830.023092] usb 3-1: Product: IEEE-1284 Controller Aug 8 13:52:38 dj kernel: [14830.023095] usb 3-1: Manufacturer: Prolific Technology Inc. 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


Do you think the printer is being wrongly detected as a mass-storage USB

What's the full (I mean, the relevant part for USB stack) dmesg output
when you connect the printer? What about "lsusb"? Do other USB devices
I will have to reboot to answer this.  I'll get back to you on this.

No, they all have problems in wheezy and Sid

The "no file found error" persists after installing the libmtp-runtime

Odd thing is that a few weeks ago there way an upgrade the fixed the
problem and 2 days later a safe-upgrade downgraded to the old (not
working) version.

Then wait for the next set of updates :-P

Like I have been.  :-(


Reply to: