From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] pipewire-0.3.55_2 required changes to /etc/sv/pipewire-pulse for systemwide pipewire-pulse to work
Date: Tue, 14 Nov 2023 02:12:43 +0100 [thread overview]
Message-ID: <20231114011243.K0a8np0qvEkFn7a60OS82CYYOyQb9zYdqWr2neW0w5s@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38189@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
Closed issue by datenwolf on void-packages repository
https://github.com/void-linux/void-packages/issues/38189
Description:
After updating to pipewire-0.3.55_2 `pipewire-pulse` unconditionally sets `chmod("/run/pulse", 0700);` thereby shutting out any PA client not running as `PID == _pipewire`. To mitigate this I changed `/etc/sv/pipewire-pulse/run` to this:
```
#!/bin/sh
# this service is experimental and most setups should start pipewire as a user,
# for further information, please refer to the handbook
if [ -d /run/pulse ] ; then
chown 0:_pipewire /run/pulse
chmod 1775 /run/pulse
else
install -m 1775 -g 0 -o _pipewire -d /run/pulse
fi
umask 002
export PULSE_RUNTIME_PATH=/run/pulse
exec chpst -u _pipewire:_pipewire pipewire-pulse
```
Using this runit `run` script things work again; in my case this means I can listen to music with systemwide MPD, while having a simultaneous separate Work-from-Home user session running with WebEx meetings audio *and* OBS running as my main user recording everything (i.e. I *want* the different sessions to share audio!)
next prev parent reply other threads:[~2023-11-14 1:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 10:20 [ISSUE] " datenwolf
2022-07-22 13:44 ` paper42
2022-07-22 14:46 ` lemmi
2023-11-14 1:12 ` classabbyamp [this message]
2023-11-14 1:12 ` classabbyamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231114011243.K0a8np0qvEkFn7a60OS82CYYOyQb9zYdqWr2neW0w5s@z \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).