(In reply to Johannes Meixner from comment #125) > Retested with newest Tumbleweed and again for me everything "just works": > --------------------------------------------------------------------------- > # cat /etc/os-release > NAME=openSUSE > VERSION="20150630 (Tumbleweed)" > VERSION_ID="20150630" > PRETTY_NAME="openSUSE 20150630 (Tumbleweed) (x86_64)" > ... > > # /usr/lib/cups/backend/usb > DEBUG: Loading USB quirks from "/usr/share/cups/usb". > DEBUG: Loaded 72 quirks. > DEBUG: list_devices > DEBUG: libusb_get_device_list=5 > DEBUG2: Printer found with device ID: > MFG:Brother;CMD:PJL,PCL,PCLXL,POSTSCRIPT;MDL:HL-5150D series;CLS:PRINTER; > Device URI: usb://Brother/HL-5150D%20series?serial=F5J889574 > direct usb://Brother/HL-5150D%20series?serial=F5J889574 "Brother > HL-5150D series" "Brother HL-5150D series" "MFG:Brother; > CMD:PJL,PCL,PCLXL,POSTSCRIPT;MDL:HL-5150D series;CLS:PRINTER;" "" > --------------------------------------------------------------------------- > > I used the CUPS web frontend (http://localhost:631) to set up > a print queue and (as expected) the "Brother HL-5150D series" > from the /usr/lib/cups/backend/usb stdout output was shown there > and of course the printer device prints - both the CUPS test page > and also via "echo hello | lp -d Brother_HL-5150D_series". > > I close the issue at least for now as "worksforme" according to > https://bugzilla.suse.com/page.cgi?id=status_resolution_matrix.html > --------------------------------------------------------------------------- > The problem described cannot be duplicated. > If more information is provided, the bug can be reopened. > --------------------------------------------------------------------------- > > Regardless that it is closed, you can still add comments, > i.e. you should not reopen it only to add comments. > > I am still interested to find out what kinds of USB printer devices > cause such issues and if possible what kinds of CUPS usb quirk > or other workarounds may help in which particular case. > > Regarding what CUPS usb quirk should usually help > in case of what currently known USB printer symptoms > I asked in the CUPS upstream mailing list cups@cups.org > about "Documentation about CUPS usb quirks usage?" > and I got this reply: > http://cups.org/pipermail/cups/2015-July/026924.html > (excerpt): > ---------------------------------------------------------------------------- > The original quirks come directly from the old usblp kernel driver. > > Generally speaking, "soft-reset" is used for printers that work once > but not for a second job. "unidir" is used for printers that don't > properly support back-channel data (either hung or slow printing). > And "no-reattach" is often needed for MFPs with scanner drivers. > > "usb-init" is used by Gutenprint to know whether to send a USB init > string. > ---------------------------------------------------------------------------- > > FYI: > > This time I used a Brother HL-5150D USB printer because > my EPSON Stylus Photo R360 tells me that its ink is empty > (more precisely it tells me that I must replace its ink) > and that crap device now refuses to do anything unless > it got new ink (I cannot even send printing data to it) > so that I will now throw that piece of crap into our > trash can for hardware scrap. > > I recommend to do this with any piece of hardware that > turns out to have been made by its manufacturer against > the basic ideas of the Free Software Foundation. > In this case the EPSON Stylus Photo R360 does not > respect my freedom to use it regardless that the device > thinks one or more of its ink-units are empty. > Accordingly I do not respect such kind of devices > and just kick them out of my environment. okay, thanks for your efforts. i'll have to throw away my USB printer cable, maybe thats what Apple wants.. :o)