[ISSUE] pipewire-0.3.55_2 required changes to /etc/sv/pipewire-pulse for systemwide pipewire-pulse to work

[ISSUE] pipewire-0.3.55_2 required changes to /etc/sv/pipewire-pulse for systemwide pipewire-pulse to work

[datenwolf]

[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]

New 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!)

Re: pipewire-0.3.55_2 required changes to /etc/sv/pipewire-pulse for systemwide pipewire-pulse to work

[paper42]

[-- Attachment #1: Type: text/plain, Size: 158 bytes --]

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/38189#issuecomment-1192591234

Comment:
@st3r4g @lemmi

Re: pipewire-0.3.55_2 required changes to /etc/sv/pipewire-pulse for systemwide pipewire-pulse to work

[lemmi]

[-- Attachment #1: Type: text/plain, Size: 475 bytes --]

New comment by lemmi on void-packages repository

https://github.com/void-linux/void-packages/issues/38189#issuecomment-1192649422

Comment:
In the recent versions, the default `pipewire-pulse.conf` added a call to `pactl`. Removing that also solves the permissions problem. 
```bash
cp /usr/share/pipewire/pipewire-pulse.conf /etc/pipewire/pipewire-pulse.conf
```
Then comment out the line 
```
{ path = "pactl"        args = "load-module module-always-sink" }
```

Re: [ISSUE] [CLOSED] pipewire-0.3.55_2 required changes to /etc/sv/pipewire-pulse for systemwide pipewire-pulse to work

[classabbyamp]

[-- 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!)

Re: pipewire-0.3.55_2 required changes to /etc/sv/pipewire-pulse for systemwide pipewire-pulse to work

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 198 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/38189#issuecomment-1809384309

Comment:
we no longer ship a pipewire-pulse system service