Arch Linux User Repository

@ Harvey i'm working with a MFC-J470DW wifi scanner. I installed brscan4 then tried to add my scanner with: brscan4 -a brsaneconfig4 -a name=MFC-J470DW model=MFC-J470DW ip=192.168.x.x

brscan4 complains for missing libavahi-client.so.3 and don't let my add my scanner i installed avahi to solve the problem now i have removed avahi and i can anyway add new scanner, but the brsaneconfig4 -q problem persist brsaneconfig4 -q /opt/brother/scanner/brscan4/brscan_cnetconfig: error while loading shared libraries: libavahi-client.so.3: cannot open shared object file: No such file or directory installing again avahi fix it. sudo brsaneconfig4 -q * MFC-J470DW [ 192.168.x.x] MFC-J470DW

@maxfranco: Please provide more information. Network or USB scanner, scanner model, which frontend do you use, are there any error messages, which steps did you take to use your scanner. Without this I can only tell that for me it works without avahi...

There is a missing dependency, without avahi (libavahi-client.so.3) it's impossible add or query scanners.

Systemd developers seem to be unsure about this case subject too: https://github.com/systemd/systemd/issues/5642 ☺

@ettavolt

Thanks, the workaround did the trick, though now it's fixed :)

@Harvey

I removed the udev rule, updated the package and rebooted for good measure, now I can confirm it's working perfectly, so the suspicions may have been correct.

Thank you both!

@Sondeluz, sorry, I've copy-n-pasted != for the idProduct check in the proposed rule. It should have been

ACTION=="add" ATTR{idVendor}=="04f9" ATTR{idProduct}=="041f" ENV{libsane_matched}="yes"

@Sondeluz: Please try again with -5 (Converted to uppercase as used in 20-sane.hwdb)

Hello!

The command returns libsane_matched=yes

Yes, I am the only user on a Plasma/X session with systemd indeed.

I had no luck with the udev rule, the (same) error keeps appearing.

Oh, this is much better!

Thank you for testing the change, I'm sorry that it disrupted your system even though that everything is seem to be correct.

What does the following command return in your environment?

systemd-hwdb query usb:v04f9p041f

Just to reconfirm: when you try to scan, you're the only user in the system and have a graphical session, driven by systemd, correct?

For an immediate remedy I suggest creating /etc/udev/rules.d/20-dcp-l2510d.rules with the following contents:

ACTION=="add" ATTR{idVendor}=="04f9" ATTR{idProduct}!="041f" ENV{libsane_matched}="yes"

I'm planning to have a testing session myself in a couple of days, maybe I find the package bug actually. My suspicion is that we need uppercase HEX in the hwdb in contrary to rules…

Sorry! I wasn't specific enough. This comes directly from the desktop scanner application, the printer itself was and is working nicely using brscan4 on Fedora, for example. It's a DCP-L2510D connected via USB, nothing fancy.

Both skanlite, simple-scan and xsane report I/O errors since the update. Here's what simple-scan complains about for example when running it with --debug:

[+3,50s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD

[+3,50s] DEBUG: scanner.vala:353: Device: name="brother4:bus2;dev3" vendor="Brother" model="DCP-L2510D" type="USB scanner"

[+3,61s] DEBUG: app-window.vala:2080: Saving state to /home/sam/.cache/simple-scan/state

[+10,53s] DEBUG: app-window.vala:2080: Saving state to /home/sam/.cache/simple-scan/state

[+10,64s] DEBUG: simple-scan.vala:1819: Requesting scan at 300 dpi from device 'brother4:bus2;dev3'

[+10,64s] DEBUG: scanner.vala:1704: Scanner.scan ("brother4:bus2;dev3", dpi=300, scan_mode=ScanMode.COLOR, depth=8, type=single, paper_width=0, paper_height=0, brightness=0, contrast=0, delay=0ms)

[+10,64s] DEBUG: scanner.vala:837: Processing request

[+10,64s] DEBUG: scanner.vala:898: sane_open ("brother4:bus2;dev3") -> SANE_STATUS_IO_ERROR

[+10,64s] WARNING: scanner.vala:902: Unable to open device: Error during device I/O