power as well. IMVHO it's really just inputs and outputs that should
be seat-specific. Restricting the shared resources available to a
given seat, allocating them fairly, etc., is a different problem (and
arguably one that I'd tackle per user and not per seat).
Anyway, thanks for getting back to me. Have a nice weekend!
Christian Pernegger
Am Do., 31. Aug. 2023 um 21:55 Uhr schrieb Andrei Borzenkov
:
>
> On 31.08.2023 19:22, Christian Pernegger wrote:
> There is no ID_SEAT, so this device [/dev/rfkill] ]belongs to seat0 by
> default.
It makes no sense for /dev/rfkill to belong to a specific seat,
though. GNOME at least
can just override the permissions or use the old
group way of doing things, but I'd prefer to fix things properly. The
symptoms of wrong device permissions can be insidious.
Kind regards,
Christian Pernegger
nothing changes,
there's still just the one ACL for the greeter's user (and obviously the
GNOME BT panel is broken).
Obviously I could just override the regular permissions via udev rule, give
it to an "rfkill" group or something, but I'd rather do it properly.
Kind regard
Anyway, would appreciate a few pointers,
Kind regards,
Christian Pernegger
