Package Details: brscan4 0.4.11_1-2

Git Clone URL: https://aur.archlinux.org/brscan4.git (read-only, click to copy)
Package Base: brscan4
Description: SANE drivers from Brother for compatible models
Upstream URL: http://support.brother.com
Keywords: scanner
Licenses: GPL, custom:brother
Submitter: Harvey
Maintainer: Harvey
Last Packager: Harvey
Votes: 164
Popularity: 0.061662
First Submitted: 2011-08-01 08:43 (UTC)
Last Updated: 2023-03-06 12:56 (UTC)

Dependencies (2)

Required by (66)

Sources (3)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 24 Next › Last »

Harvey commented on 2021-04-21 11:23 (UTC)

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

Sondeluz commented on 2021-04-21 09:29 (UTC)

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.

ettavolt commented on 2021-04-20 15:15 (UTC)

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…

Sondeluz commented on 2021-04-20 13:19 (UTC) (edited on 2021-04-20 13:19 (UTC) by Sondeluz)

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

ettavolt commented on 2021-04-19 20:23 (UTC)

Sorry, we can't help you with the information you've provided. Our printers don't show anything like this on their dot-led displays. ☺

Maybe that is an error in the output of some application or service? Which one? How is it launched?

Sondeluz commented on 2021-04-19 20:17 (UTC) (edited on 2021-04-19 20:17 (UTC) by Sondeluz)

I honestly fail to understand these changes, but if it is of any help, my printer now throws "Failed to open device 'brother:bus4;dev1': Error during device I/O." since the last update.

egrupled commented on 2021-04-17 14:11 (UTC)

@applebloom recent version doesn't install anything /etc/udev, please update.

applebloom commented on 2021-04-17 14:06 (UTC)

Hi. I noticed that udev rules are installed in /etc (/etc/udev/rules.d/40-brscan4.rules). Shouldn't they go into /usr/lib/udev? Etc should be only for local configuration only, I think.

ettavolt commented on 2021-04-17 06:46 (UTC) (edited on 2021-04-17 07:00 (UTC) by ettavolt)

@markuschaaf, the setup with rules adding 'scanner' group is package-specific. Sane's way is to add libsane_matched=yes to scanner devices and let some 'base' rule to react to this env. Particularly, /usr/lib/udev/rules.d/66-saned.rules runs /usr/bin/setfacl -m g:saned:rw $env{DEVNAME} for these.

You should probably tweak your service launchers to start under 'saned' group instead of 'scanner'.

Alternatively, add a copy of that rule in, say, /etc/udev/rules.d/66-scanner.rules with 'saned' group replaced by 'scanner'.

Note: both tweaks will leave all scanners (not just those supported by brscan4) equally accessible.

egrupled commented on 2021-04-16 18:19 (UTC) (edited on 2021-04-16 19:21 (UTC) by egrupled)

Group based permission management is deprecated in Arch and repo packages are moving away from it. It's hard to blame AUR package for doing exactly the same what repo package did. It's more a standard than a fashion. One of the points of systemd dynamic permission model is to differentiate between local and remote user permissions. Users are free to modify this behavior as they wish.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 24 Next › Last »