I think the right fix would be for systemd to add the three LSM syscalls to its
@system-service (or @privileged) built-in filter group.
And maybe apparmor should handle the SIGSYS case more gracefully, or detect
when the new syscall interface is available before committing to using it
** Changed in: pipewire (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2142428
Title:
pipewire-pulse.service crashes with signal=SYS on Ubuntu 26.04
(Resolute) – No audio, “Not connected to PulseAudio server”
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2142428/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
