Package Details: brscan4 0.4.4_1-2

Git Clone URL: https://aur.archlinux.org/brscan4.git (read-only)
Package Base: brscan4
Description: SANE drivers from Brother for brscan4 compatible models
Upstream URL: http://welcome.solutions.brother.com/bsc/public_s/id/linux/en/download_scn.html
Licenses: GPL, custom:brother
Submitter: Harey
Maintainer: Harey
Last Packager: Harey
Votes: 66
Popularity: 1.536736
First Submitted: 2011-08-01 08:43
Last Updated: 2016-10-26 09:36

Dependencies (2)

Required by (7)

Sources (3)

Latest Comments

Harey commented on 2016-10-26 09:38

DUH! Forgotten to change the checksums. Now it should work. Did not change the version for this.

dhtseany commented on 2016-10-25 19:15

mk-udev-rules ... FAILED
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build brscan4.

Harey commented on 2016-10-24 09:29

Ok, had another look into this. I guess the users that have their device attached to the network do not face the problem because of the network use. So let's have a try for changing the device node ownership to the 'lp' group. It seems that not even brother knows the final solution, because here (http://support.brother.com/g/s/id/linux/en/instruction_scn1c.html?c=us_ot&lang=en&comple=on&redirect=on) they are suggesting the 'scanner' group, except for openSUSE11.2, which has the 'lp' group.
BTW @aborigines: I would be very interested in how you managed to add a group to another. I googled my a** off but all I read said this is not possible.

pitlochry commented on 2016-10-23 11:32

Had also the problem, bhartshorn and sowieso and aborigines and others commented on. What I did:

sudo gpasswd -a USER lp
sudo sed -i 's/GROUP="scanner"/GROUP="lp"/g' /etc/udev/rules.d/brscan4.rules

This is perhaps not the perfect solution, but it works.
@Harey: What is the better solution? sudo gpasswd -a USER scanner did not work.
@aborigines: How do you add a group to another?

Can you just post the command(s), like I did above? Thanks

Harey commented on 2016-10-11 06:38

See https://wiki.archlinux.org/index.php/Users_and_groups#Group_management (and the explanations for the lp group) and https://bugs.archlinux.org/task/50009. I'd say everyone with this problem should decide what to do by himself. Appearantly there aren't that much systems affected. Besides that brscan does also work with some scan-only devices (IIRC)

bhartshorn commented on 2016-10-11 01:58

Am I the only one experiencing this issue:
https://wiki.archlinux.org/index.php/CUPS/Troubleshooting#Conflict_with_SANE
using this package? I went ahead and replaced each instance of "scanner" with "lp" in /etc/udev/rules.d/brscan4.rules and everything (including scanning) is working just fine.

It might be worth a patch in this package? Or maybe there's a better way of getting it to work?

edit: I see sowieso had this issue as well, my bad. I just don't see much reason to have the permissions set to use "scanner" group if scanning works just fine when it's set to lp. (Presumably because cups uses lp, but scanning is based upon the gorups the user is in...)

Harey commented on 2016-09-13 08:33

Updated to 0.4.4-1. SOrry for the delay - vacations ;)

herzmeister commented on 2016-07-21 09:56

works for my Brother MFC-J5320DW as per wiki, without any problems or additional steps.

timofonic commented on 2016-04-28 14:21

Why do we need to install another piece of code? It seems this is proprietary, something that doesn't attract me at all!

What about direct SANE support? This is inSANE! :(

I really don't understand why it's so messy to use a scanner on Linux!

Is the full source code available?

Maybe I need to learn more before instad complaining, but I'm unable to understand the situation. It would be nice if someone explains it ;)

sowieso commented on 2016-02-26 10:22

@aborigines: Adding a group to another is new to me too. Can you explain how this should be possible?
Setting it world readable sure solves the problem, but then everyone can print / scan. Permissions could be easily fixed with ACLs, but I don't know if udev supports them and as many filesystems are mounted without support, it's not feasible.

All comments