| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Pipewire shares memory with its clients using open file
descriptors (memfd or shared memory file) which are created within
pipewire and therefore they have the same smack label as the
pipewire process. Clients must be able to read and write to this
memory, therefore they need rw acess to that smack label.
Since all AGL apps have only write access to the System label,
we need to use a different smack label which can be granted rw
access from the applications that need to use audio.
"System::Pipewire" is chosen here to follow the "System::Sub"
pattern that is described in the documentation.
Bug-AGL: SPEC-2554
Change-Id: I81cbf82adfde3ef4f67872bd91293370339b18d7
Signed-off-by: George Kiagiadakis <george.kiagiadakis@collabora.com>
|
|
This allows granting pipewire additional permissions, most notably
the permission to access the alsa devices (SupplementaryGroups=audio)
and therefore fixes pipewire for the "running as non-root" setup
Bug-AGL: SPEC-2554
Change-Id: Ie9192a7f42f4929f70114ddc39a23d94f9ba84fc
Signed-off-by: George Kiagiadakis <george.kiagiadakis@collabora.com>
|
|
Add a bbappend to the pipewire recipe to create the required symlink
in /etc/systemd/user/sockets.target.wants to enable per-user socket
activation. A bbappend is used as this change is likely to be AGL
specific (for now?).
Bug-AGL: SPEC-2521
Change-Id: I4b349ab8151eabfb933f2dcfcf9d293fcb3ea321
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
|
George Kiagiadakis
Scott Murray