Re: [udev] Scanner rule not applied during boot

[Lennart Poettering <lennart@xxxxxxxxxxxxxx>]

On Mo, 19.10.20 21:19, Marcin Kocur (marcin2006@xxxxxxxxx) wrote:

>
> Hello systemd devs and users,
>
> I need an advice regarding USB scanner which rule is not(?) processed at
> boot time. When I trigger it manually, the scanner device file gets proper
> permissions.
>
> Here's the rule:
>
> cat /usr/lib/udev/rules.d/49-sane.rules |grep -A1 '1200 TA'
> # Mustek BearPaw 1200 CS | Mustek BearPaw 1200 TA
> ATTRS{idVendor}=="055f", ATTRS{idProduct}=="021e", MODE="0664",
> GROUP="scanner", ENV{libsane_matched}="yes"
>
> Here it is how it looks like directly after the boot:
>
> lsusb
> Bus 001 Device 003: ID 055f:021e Mustek Systems, Inc. BearPaw 1200 TA/CS
>
>
> getfacl /dev/bus/usb/001/003
> # file: dev/bus/usb/001/007
> # owner: root
> # group: scanner
> user::rw-
> group::rw-
> other::r--
>
> And this is how it looks after triggering manually:
> udevadm trigger -c add /dev/bus/usb/001/003:
>
> getfacl /dev/bus/usb/001/003
> # file: dev/bus/usb/001/007
> # owner: root
> # group: scanner
> user::rw-
> user:mk:rw-   <<<<<<<< NOW MY USER IS HERE

And?

It's still owned by the "scanner" group like before, which the line
three up shows you.

The extra ACL entry probably comes from some "uaccess" rule somebody
sets on the device. But I don#t now what rules you added or what sane
sets there precisely.

Lennart

--
Lennart Poettering, Berlin
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel