Comment # 122 on bug 920937 from
(In reply to Johannes Meixner from comment #117)
> I cannot tell what particular USB quirk or quirks (you can have
> more than one in a line) might help for your particular USB printer
> or if it is even hopeless to use a particular USB device with the
> libusb-based 'usb' backend.
> 
> Because it had worked by using the usblp kernel module
> (i.e. with the usblp-based 'usb' backend in our CUPS 1.5.4)
> there is at least the workaround that I mentioned in comment#68

Thanks. I'd rather reinstall 1.5.4.  

As there are 2 other people in this bug list also struggling with this, (i
think they have kyocera USB printers), do we close this bug down and attribute
the problem to dodgy printer firmware on samsung and kyocera printers?  I'm
willing to continue running any tests you think need to be run in case this is
a tumbleweed specific issue.

I doubt i'll ever understand how the USB printer is identified using the
backends okay, but the actual printer control front end can't deal with it.


You are receiving this mail because: