Refer post 17. However, I’m also wondering about the bus/dev IDs reported by scanimage. It may be better to use the output from the following instead
sane-find-scanner
Sorry for my slow reply. I was so frazzled & irate at this stupid machine that i decided to take some time away from it, but i’m back now, bashing my head again at the same MFC brick wall.
Your eagle eyes are to be congratulated!! I did not notice it at the time, but looking back at all my working notes of the past few days, i can see that the lsusb of 25/9/17 reported “Bus 001 Device 010: ID 04f9:0185 Brother Industries, Ltd MFC-7220 Printer”, whereas the lsusb of 26/9/17 instead reported the “Bus 002 Device 003: ID 04f9:0185 Brother Industries, Ltd MFC-7220 Printer” that you noticed. The difference was caused * by the fact that on 26/9 i had done a backup, to my two USB3 sticks, which were still in the Tower ports by the time i had resumed fighting with this rotten MFC. For comparison, here’s the full listings, from both those days Konsole & pasting into Kate, so i am certain of this info’s accuracy / i am not merely relying on my bad memory]:
gooeygirl@linux-Tower:~> **lsusb** ###From 25/9/17:
Bus 004 Device 002: ID 8087:8001 Intel Corp.
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 8087:8009 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
**Bus 001 Device 010: ID 04f9:0185 Brother Industries, Ltd MFC-7220 Printer** #********************
Bus 001 Device 008: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
Bus 001 Device 006: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 001 Device 007: ID 413c:2010 Dell Computer Corp. Keyboard
Bus 001 Device 005: ID 413c:1003 Dell Computer Corp. Keyboard Hub
Bus 001 Device 004: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
gooeygirl@linux-Tower:~> **lsusb** ###From 26/9/17:
Bus 004 Device 002: ID 8087:8001 Intel Corp.
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8009 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 18a5:0243 Verbatim, Ltd Flash Drive (Store'n'Go)
Bus 003 Device 002: ID 0781:5588 SanDisk Corp.
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
**Bus 002 Device 003: ID 04f9:0185 Brother Industries, Ltd MFC-7220 Printer** #********************
Bus 002 Device 009: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
Bus 002 Device 007: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 002 Device 008: ID 413c:2010 Dell Computer Corp. Keyboard
Bus 002 Device 006: ID 413c:1003 Dell Computer Corp. Keyboard Hub
Bus 002 Device 005: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse
Bus 002 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 002 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Today, 28/9/17, my Tower once again does not have my USB3 sticks installed … all USB ports have the same occupancy vs empty status as on 25/9/17. However, to my further confusion, today’s lsusb gives yet another different output for the MFC [huh?]:
gooeygirl@linux-Tower:~> **lsusb** ###From 28/9/17:
Bus 004 Device 002: ID 8087:8001 Intel Corp.
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 8087:8009 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
**Bus 001 Device 009: ID 04f9:0185 Brother Industries, Ltd MFC-7220 Printer** #********************
Bus 001 Device 008: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
Bus 001 Device 006: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 001 Device 007: ID 413c:2010 Dell Computer Corp. Keyboard
Bus 001 Device 005: ID 413c:1003 Dell Computer Corp. Keyboard Hub
Bus 001 Device 004: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Conversely today’s…
gooeygirl@linux-Tower:~> **scanimage -L**
device `brother2:bus**4**;dev**1**' is a Brother MFC-7220 USB scanner
…has not changed from those of 25/9 or 26/9 [but is obviously different to the [i]lsusb*].
Why do these two commands return contradictory bus & device numbers for the one MFC? Is that correct, or symptomatic of a problem? Having noted the differences, today i tried both sets of values…
gooeygirl@linux-Tower:~> scanimage -d brother2:libusb:**004:001** --format=tiff >image.tiff # from scanimage -L
scanimage: open of device brother2:libusb:004:001 failed: Invalid argument
gooeygirl@linux-Tower:~>
gooeygirl@linux-Tower:~> scanimage -d brother2:libusb:**001:009** --format=tiff >image.tiff # from lsusb
scanimage: open of device brother2:libusb:001:009 failed: Invalid argument
gooeygirl@linux-Tower:~>
…but as usual, nothing works.
Is skanlite installed?
Yes. The first launch of it, it does launch, & looks like the normal GUI, but when i try to scan, it returns an error message in a pop-up box; “Invalid argument”. All subsequent launch attempts only result in a single new pop-up box; “Sorry Opening the selected scanner failed.”
Yes, I’ve seen that inconsistency between ‘lsusb’ and ‘scanimage -L’ with bus/device numbering reported before. I’ll try to dig up a page…
I’m not surprised to read that skanlite fails - the simple-scan log signalled an issue with communication to the scanner at a low-level via the USB interface. This is likely driver specific. FWIW, I’m using a USB-connected Brother DCP-7055 model (brother4 driver) with no issue at all. A bug report is required here. However, since you’re using a proprietary backend it may be necessary to contact Brother Industries for support first.
Post #17 was for my Leap 42.3 VM, not my Tower’s “real” TW, to which the bulk of this thread is dedicated.
Now, for my Tower’s “real” TW:
gooeygirl@linux-Tower:~> **sane-find-scanner**
# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.
# No SCSI scanners found. If you expected something different, make sure that
# you have loaded a kernel SCSI driver for your SCSI adapter.
could not open USB device 0x1d6b/0x0002 at 004:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 003:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0003 at 002:001: Access denied (insufficient permissions)
**found USB scanner (vendor=0x04f9, product=0x0185) at libusb:001:009**
could not open USB device 0x045e/0x0039 at 001:008: Access denied (insufficient permissions)
could not open USB device 0x0461/0x4d81 at 001:004: Access denied (insufficient permissions)
could not open USB device 0x05e3/0x0608 at 001:003: Access denied (insufficient permissions)
could not open USB device 0x05e3/0x0608 at 001:002: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 001:001: Access denied (insufficient permissions)
# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
# You may want to run this program as root to find all devices. Once you
# found the scanner devices, be sure to adjust access permissions as
# necessary.
gooeygirl@linux-Tower:~>
They’re the same bus/dev IDs as reported by lsusb, but [as i noted in my reply to [b]Knurpht a few minutes ago] clearly contradictory to scanimage -L . However also per my reply to Knurpht a few minutes ago, irrespective of which values i tried in the scanimage -d command, i only get “scanimage: open of device brother2:libusb:xxx:yyy failed: Invalid argument”.
Yes, ‘scanimage -L’ doesn’t reflect reality, unlike ‘lsusb’ and ‘sane-find-scanner’.
I think it is time to communicate with Brother…perhaps there have been changes with libusb that have impacted on older Brother drivers?
I’m very grateful for your & the others’ dogged help, but as for Brother, fyi in April & May 2016 i exchanged several emails with their local Technical Support, Product Support Centre [with much documentation & screenshots & Konsole output supplied to them], & had a 2 hour telecon + TeamViewer session with one of them [ie, i gave him access to my pc]. He was unable to find anything incorrect in any of my settings. I was still using Mint 17.3 x64 KDE4 back then, but almost all of the steps for that were the same as we’ve been doing here in TW & Leap. Given i have been fighting this for ~3 years, & given Brother already tried to help, i think i’ve now pretty much run out of energy & passion to continue.
Though i feel pessimistic of any chance of success, i’m now going to try conram’s last suggestion, in another of my TW VMs [which has not yet been exposed to any MFC attempts]. If i do not post back into this thread again soonish, it will mean that this also failed, If so, then my original remark would stand… “Brother MFC-7220: Scanner allergic to Linux”.
It is frustrating with situations like this I agree. Just for interest’s sake open a terminal and run
dmesg --follow
then plug in your multifinction device and report back. I want to see how it is initially reported.
This thread matches your experience…
https://forums.mauilinux.org/showthread.php?tid=24332
Definitely, something up with the driver and this particular model it appears.
Heehee, ahem, yes, i am [cough cough] extremely familiar with that thread… 
What does
zypper se libusb
give?
It gives:
gooeygirl@linux-Tower:~> **zypper se libusb**
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
---+------------------------+---------------------------------------------------------------------+--------
| libhidapi-libusb0 | Simple library for communicating with USB and Bluetooth HID devices | package
i+ | libusb-0_1-4 | libusb-1.0 Compatibility Library for libusb-0.1 | package
| libusb-0_1-4-32bit | libusb-1.0 Compatibility Library for libusb-0.1 | package
i+ | libusb-1_0-0 | USB Library | package
i+ | libusb-1_0-0-32bit | USB Library | package
| libusb-1_0-devel | USB Library | package
| libusb-1_0-devel-32bit | USB Library | package
| libusb-compat-devel | libusb-1.0 Compatibility Layer for libusb-0.1 | package
| libusbguard0 | Library for implementing USB device usage policy | package
| libusbgx-devel | Development files for the USB gadget configuration library | package
| libusbgx-tools | Utilities to show and configure USB gadget devices | package
| libusbgx1 | USB gadget device configuration library | package
| libusbmuxd-devel | Development files for libusbmuxd | package
i+ | libusbmuxd4 | A client library to multiplex connections from and to iOS devices | package
| libusbmuxd4-32bit | A client library to multiplex connections from and to iOS devices | package
| libusbprog0 | USBprog Library | package
i+ | libusbredirhost1 | A protocol for redirection USB traffic | package
i+ | libusbredirparser1 | A protocol for redirection USB traffic | package
gooeygirl@linux-Tower:~>
I’ll probably have to suspend further activity on this topic, for now, given that annoyingly my TW appears to have broken today & i still don’t know how to fix it yet… https://forums.opensuse.org/showthread.php/527372-20170924-to-20170925-dup-failed?p=2839769#post2839769
Is your regular user a member of the “lp” group?
Can you post the permissions of /dev/bus/usb/001/009 ?
Is the device connected to a USB3 or USB2 port ?
Is the blacklist re. tlp still active?
I’m also wondering about the USB host controller (XHCI vs EHCI) as that has caused problems like this in the past with some devices. Can you also run the ‘dmesg --follow’ command as explained in post #27 when you get a chance?
One more place to look-up is
usr/local/Brother/sane/setupSaneScan2
Open that file and should look something like this
#! /bin/sh
FILE_NAME=/etc/sane.d/dll.conf
LIBSANEBROTHER1="brother3"
LIBSANEBROTHER2="^""$LIBSANEBROTHER1""$"
DRV=`grep "$LIBSANEBROTHER2" $FILE_NAME`
case "$1" in
-i)
if "$DRV" = '' ];then
cat << EOF >> $FILE_NAME
$LIBSANEBROTHER1
EOF
fi
;;
-e)
mv $FILE_NAME "$FILE_NAME".tmp
cat "$FILE_NAME".tmp |\
sed s/"$LIBSANEBROTHER1"//g > $FILE_NAME
;;
*)
;;
esac
Mine is brother3 yours is brother2
Open /etc/sane.d/dll.conf and look for brother2 if it is there.
If it’s not add at the bottom of the list
Wonder also the output of
scanimage --test
The OP confirmed that already in the opening post (refer point 7).
Note to all kind Repliers since my previous post in this thread:
I am not ignoring any of your subsequent questions & advice, but have become unexpectedly “distracted” recently… https://forums.opensuse.org/showthread.php/527372-20170924-to-20170925-dup-failed?p=2839856#post2839856 Once i have recovered my system, one way or another, i shall return to this thread. Thanks to all. Never a dull moment…
Back onto this accursed problem, after an enforced hiatus.
gooeygirl@linux-Tower:~> **dmesg --follow
**[10730.413791] usb 3-5: USB disconnect, device number 3 #The MFC-7220 was still plugged in at this point, so then i unplugged it.
[10730.413978] usblp0: removed
[10740.436413] usb 3-5: new full-speed USB device number 10 using xhci_hcd #The response to me plugging it back in.
It gives:
gooeygirl@linux-Tower:~> **zypper se libusb**
Repository 'Packman Repository' is out-of-date. You can run 'zypper refresh' as root to update it.
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
---+------------------------+---------------------------------------------------------------------+--------
| libhidapi-libusb0 | Simple library for communicating with USB and Bluetooth HID devices | package
i+ | libusb-0_1-4 | libusb-1.0 Compatibility Library for libusb-0.1 | package
| libusb-0_1-4-32bit | libusb-1.0 Compatibility Library for libusb-0.1 | package
i+ | libusb-1_0-0 | USB Library | package
i+ | libusb-1_0-0-32bit | USB Library | package
| libusb-1_0-devel | USB Library | package
| libusb-1_0-devel-32bit | USB Library | package
| libusb-compat-devel | libusb-1.0 Compatibility Layer for libusb-0.1 | package
| libusbguard0 | Library for implementing USB device usage policy | package
| libusbgx-devel | Development files for the USB gadget configuration library | package
| libusbgx-tools | Utilities to show and configure USB gadget devices | package
| libusbgx1 | USB gadget device configuration library | package
| libusbmuxd-devel | Development files for libusbmuxd | package
i+ | libusbmuxd4 | A client library to multiplex connections from and to iOS devices | package
| libusbmuxd4-32bit | A client library to multiplex connections from and to iOS devices | package
| libusbprog0 | USBprog Library | package
i+ | libusbredirhost1 | A protocol for redirection USB traffic | package
i+ | libusbredirparser1 | A protocol for redirection USB traffic | package
gooeygirl@linux-Tower:~>
Whoops, a duplicate.
Yes:
gooeygirl@linux-Tower:~> **id
**uid=1000(gooeygirl) gid=100(users) groups=100(users),**7(lp)**,475(vboxusers)
gooeygirl@linux-Tower:~>
How do i do that pls? Also, that bus/device combo might no longer apply, pls see this done today [why do these seem to change so many times?]
gooeygirl@linux-Tower:~> **lsusb**
Bus 002 Device 002: ID 8087:8001 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8009 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
**Bus 003 Device 003: ID 04f9:0185 Brother Industries, Ltd MFC-7220 Printer**
Bus 003 Device 009: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
Bus 003 Device 007: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 003 Device 008: ID 413c:2010 Dell Computer Corp. Keyboard
Bus 003 Device 006: ID 413c:1003 Dell Computer Corp. Keyboard Hub
Bus 003 Device 005: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse
Bus 003 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
…and…
gooeygirl@linux-Tower:~> **sane-find-scanner**
# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.
# No SCSI scanners found. If you expected something different, make sure that
# you have loaded a kernel SCSI driver for your SCSI adapter.
could not open USB device 0x1d6b/0x0002 at 002:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 001:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0003 at 004:001: Access denied (insufficient permissions)
**found USB scanner (vendor=0x04f9, product=0x0185) at libusb:003:003**
could not open USB device 0x045e/0x0039 at 003:009: Access denied (insufficient permissions)
could not open USB device 0x0461/0x4d81 at 003:005: Access denied (insufficient permissions)
could not open USB device 0x05e3/0x0608 at 003:004: Access denied (insufficient permissions)
could not open USB device 0x05e3/0x0608 at 003:002: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 003:001: Access denied (insufficient permissions)
# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.
# Not checking for parallel port scanners.
# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
# You may want to run this program as root to find all devices. Once you
# found the scanner devices, be sure to adjust access permissions as
# necessary.
USB2.
Yes [relevant extract]:
# Exclude listed devices from USB autosuspend (separate with spaces).
# Use lsusb to get the ids.
# Note: input devices (usbhid) are excluded automatically
#USB_BLACKLIST="1111:2222 3333:4444"
#Added 26/9/17 as last-ditch attempt to get the bloody Brother MFC-7220 SCANNER to work.
#Reference1 = https://forums.opensuse.org/showthread.php/526075-Samsung-ML-1640-working-on-Leap-not-on-Tumbleweed?p=2836288#post2836288
#Reference2 = https://ubuntu-mate.community/t/printer-pauses-randomly-after-upgrade-to-16-04/5653/52
USB_BLACKLIST="04f9:0185"
Please note also these [you did not ask for them, but they’re just some additional checks i did today, to double-check that the scanner drivers are actually installed. References = Others | Brother support website …and… Others | Brother support website]
gooeygirl@linux-Tower:~> rpm -qa | grep brscan2
**brscan2-0.2.5-1.x86_64**
gooeygirl@linux-Tower:~> rpm -qa | grep brscan-skey
**brscan-skey-0.2.4-1.x86_64**