I was looking at bug 801601 as I was wondering about the sound access when switching the users in one of the systems I maintained. When I was reading ebuild instructions I saw: It is recommended to raise RLIMIT_MEMLOCK to 256 for users using PipeWire. Do it either manually or add yourself to the 'audio' group: For us I am still running ok without raising the limit, but I was wondering about how to raise the limit manually... I would then suggest too about how to do that. I have found some solutions in Gentoo and Arch wikis: https://wiki.gentoo.org/wiki/PipeWire#Increasing_RLIMIT_MEMLOCK_for_PulseAudio_clients_.28systemd_specific.29 I would be tempted to try the systemd solution, but reading: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/692 I am unsure about if all this RLIMIT_MEMLOCK modifications are really needed or, if they are still needed, why don't enable it by default in the systemd unit Thanks a lot
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=18d85ef89d55d7337b463ff6a04e74b173283589 commit 18d85ef89d55d7337b463ff6a04e74b173283589 Author: Sam James <sam@gentoo.org> AuthorDate: 2023-02-22 22:47:46 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-02-22 22:55:30 +0000 media-video/pipewire: add 0.3.66 Bug: https://bugs.gentoo.org/791847 Closes: https://bugs.gentoo.org/892822 Signed-off-by: Sam James <sam@gentoo.org> media-video/pipewire/Manifest | 1 + media-video/pipewire/pipewire-0.3.66.ebuild | 466 ++++++++++++++++++++++++++++ media-video/pipewire/pipewire-9999.ebuild | 22 +- 3 files changed, 482 insertions(+), 7 deletions(-)
