On 11/09/2020 09.46, tomas.kuchta.lists@gmail.com wrote:
On Fri, 2020-09-11 at 12:52 +0930, Simon Lees wrote:
On 9/11/20 10:05 AM, tomas.kuchta.lists@gmail.com wrote:
If someone could explain this in a few sentences - I would really appreciate it.
https://wiki.ubuntu.com/Audio/TheAudioGroup except instead of using consolekit it now uses parts of the systemd/logind stack. In short a user who is logged in graphically will gain access to audio / keyboard / mouse / display devices. A user logged in remotely should generally not have access as a security feature.
Thank you Simon - I am starting to connect the dots - this is real deep rabbit hole though.
Carlos mentioned seats - I thought that it is just bad translation for user account - I am slowly starting to remember the old mainframes and Vax's and their system topology.
No, it refers to the user that is seated at the machine. It is assumed that the user that has the currently active local session has the seat. ...
My early guess is that I will not be able to come up with anything better than the audio group membership with all its possible side effects - within a day or two before I giving up.
Unless somebody documents (doc.opensuse.org or wiki.opensuse.org) how it is actually done and how can we modify it, the groups is the only practical way. And not always, because in my machine I want root to make sounds from cron scripts, and he gets no permissions. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)