cups reports it can't open device, but the rights on the device are ok. Enabling debug output of cups didn't tell which device it can't open. In mga5 the printer was working fine. Here is some output, please tell if anything is missing: [root@localhost marc]# /usr/lib/cups/backend/usb DEBUG: Loading USB quirks from "/usr/share/cups/usb". DEBUG: Bad line: Vim�UnDo DEBUG: Loaded 134 quirks. DEBUG: list_devices DEBUG: libusb_get_device_list=9 DEBUG2: Printer found with device ID: MFG:Brother;CMD:PJL,PCL,PCLXL;MDL:DCP-8060;CLS:PRINTER; Device URI: usb://Brother/DCP-8060?serial=000G9J899943 direct usb://Brother/DCP-8060?serial=000G9J899943 "Brother DCP-8060" "Brother DCP-8060" "MFG:Brother;CMD:PJL,PCL,PCLXL;MDL:DCP-8060;CLS:PRINTER;" "" [root@localhost marc]# lsusb Bus 001 Device 004: ID 04f9:01a3 Brother Industries, Ltd Composite Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 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 004 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 002 Device 003: ID 192f:0416 Avago Technologies, Pte. ADNS-5700 Optical Mouse Controller (3-button) Bus 002 Device 002: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard G230 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub [root@localhost marc]# ll /dev/bus/usb/004/001 crw-rw-rw- 1 root lp 189, 384 Dez 28 16:30 /dev/bus/usb/004/001 [root@localhost marc]# journalctl -r|head -- Logs begin at Fr 2015-10-09 14:18:13 CEST, end at Mi 2016-12-28 17:06:26 CET. -- Dez 28 17:06:26 localhost cupsd[5083]: Warte darauf dass der Drucker verfügbar wird. Dez 28 17:06:26 localhost cupsd[5083]: Failed to open device, code: -3 Dez 28 17:06:26 localhost cupsd[5083]: Expiring subscriptions... Dez 28 17:06:26 localhost cupsd[5083]: libusb_get_device_list=9 Dez 28 17:06:22 localhost cupsd[5083]: Expiring subscriptions... Dez 28 17:06:21 localhost cupsd[5083]: Warte darauf dass der Drucker verfügbar wird. Dez 28 17:06:21 localhost cupsd[5083]: Failed to open device, code: -3 [root@localhost marc]# grep DeviceURI /etc/cups/printers.conf DeviceURI usb://Brother/DCP-8060?serial=000G9J899943
CC: (none) => marja11Assignee: bugsquad => thierry.vignaud
is there anything I can do to make the printer work again?
(In reply to Marc K from comment #1) > is there anything I can do to make the printer work again? I suppose you could always try to debug the driver if it's open source.
CC: (none) => hamnisdude
this is not the driver it is libusb backend which has the problem I did some builds and keep you informed about it. Nevertheless I suggest to disable silent output of libusb_open (will post this in a ticket).
Ok, found it. /usr/lib/udev/rules.d/60-libsane.rules modifies all "scanners" to be in group "scanner". This is true for all MultiFunctionPrinters too. So I expect all MFP devices will have trouble after update. For me I added a rule which gave full access to all users on the device. I think this might work, if lp is a member of group scanner too. For libusb I suggest to generally enable debug output of libusb_open : function _get_usbfs_fd parameter "silent" (from op_open) which states the device which can't be opened. I think this output would be MUCH more help than "Failed to open device, code: -3 "
Thanks for debugging the issue, M K :-) @ Zézinho CC'ing you, because, sane-backends provides /usr/lib/udev/rules.d/60-libsane.rules and afaik you're the maintainer.
Summary: USB printers not detected => USB MFP printers not detected, because /usr/lib/udev/rules.d/60-libsane.rules modifies all "scanners", including MFPs, to be in group "scanner"Source RPM: cups-2.2.1-1.mga6.src.rpm => cups-2.2.1-1.mga6.src.rpm, sane, libusbCC: (none) => lists.jjorge
Blocks: (none) => 18367
CC: (none) => doktor5000
See also bug 25660 (re scanner access rights).
CC: (none) => lewyssmith
I have an old Samsung SCX-4200 USB printer/scanner. I don't use it as a printer, so that's not a problem. Here's what happens when I use it as a scanner. If I try using a scanning program (Xsane, for example) the scanner is only detected as soon as the scanner comes to the "ready" state. (scanner is set NOT to go into energy saving mode) After about 10 minutes, Xsane (or other scanning programs) do not find the scanner (there are no devices) For a test, I have another computer with Windows 11 installed. I also have VirtualBox for Windows (6.1.38) installed on it. I installed Fedora Spin KDE-Live 37 beta under VirtualBox. The scanner works perfectly with Xsane and the other scanning programs, no matter how long it sits at the "ready" state.
CC: (none) => lloyd.osten
Anything better with update in Bug 30703 - Update the complete sane stack ?
CC: (none) => fri
I have discovered a simple workaround that fixed my problem. I simply added myself to the groups "usb" and "scanner." It worked perfectly after that....even if the scanner was in power-saving mode.
Thank you for the quick reply and the tip :) First thought is if this should be needed or automated, leaving for someone who knows better before closing. Second thought is we should have wiki pages with tips for scanners and printers...
I know pretty much zero about programming. But it seems to me that if that's really the cause, then the scanner installation program should handle that automatically. As for your second suggestion, I totally agree with you. The goal is to make Mageia as user-friendly and bug-free as possible.
Regarding the original bug, doesn't the patch for bug #17593, which add the group lp in RW to the device fix the issue? (see: http://svnweb.mageia.org/packages/cauldron/sane/current/SOURCES/sane-backends-1.0.25-udev-add-lp-group-rw.patch?view=log )
CC: (none) => julien.moragny