On 2022-03-12 14:32, David Ward wrote:
> Yes, that is what I meant by physically logged in.
>
> You shouldn't need to be in the scanner group (or the lp group) in
> that case.
The lp group still (21.10) makes a difference for my combined printer and scanner.
$ lsusb | grep Brother
Bus 001 Device 004: ID 04f9:01ab Brother Industries, Ltd MFC-240C
$ ls -l /dev/bus/usb/001/004
crw-rw-r-- 1 root lp 189, 3 mar 12 11:01 /dev/bus/usb/001/004
> If you remove yourself from both of those groups, does this stop
> working?
Yes, both simple-scan and xsane stop working; please see attached screenshots.
> If so, what is the output of "sudo scanimage -L"?
"scanimage -L" keeps working without the lp group (also without sudo) but apparently there is more into it.
On 2022-03-12 14:32, David Ward wrote:
> Yes, that is what I meant by physically logged in.
>
> You shouldn't need to be in the scanner group (or the lp group) in
> that case.
The lp group still (21.10) makes a difference for my combined printer and scanner.
$ lsusb | grep Brother usb/001/ 004 usb/001/ 004
Bus 001 Device 004: ID 04f9:01ab Brother Industries, Ltd MFC-240C
$ ls -l /dev/bus/
crw-rw-r-- 1 root lp 189, 3 mar 12 11:01 /dev/bus/
> If you remove yourself from both of those groups, does this stop
> working?
Yes, both simple-scan and xsane stop working; please see attached screenshots.
> If so, what is the output of "sudo scanimage -L"?
"scanimage -L" keeps working without the lp group (also without sudo) but apparently there is more into it.