pulseaudio over network ends in "connection refused" due to module access starting at 0.3.41
Description of Problem:
Commit 23ac9e5f breaks pulseaudio via tcp:localhost.
How Reproducible:
Always
Steps to Reproduce:
- set in pipewire-pulse.conf:
{ name = libpipewire-module-protocol-pulse
args = {
# the addresses this server listens on
server.address = [
"unix:native"
#"unix:/tmp/something" # absolute paths may be used
#"tcp:4713" # IPv4 and IPv6 on all addresses
#"tcp:[::]:9999" # IPv6 on all addresses
"tcp:127.0.0.1:4713" # IPv4 on a single address
]
- run pipewire (after said commit - e.g. 0.3.41)
- su -l someuser
- have
cat /home/someuser/.config/pulse/client.conf
default-server = tcp:localhost
autospawn = no
- start some audio, e.g.
mplayer x.wav
Actual Results:
Client hangs and times out.
Expected Results:
Play audio.
Additional Info (as attachments):
Pipewire LOG-3:
[I][50567.854863] mod.protocol-native | [module-protocol-: 451 client_new()] server 0x55870ba47bf0: security label not available
[I][50567.854946] mod.access | [ module-access.c: 259 context_check_access()] client 0x55870bcbe110 has trusted pid 2558185
[I][50567.854972] mod.access | [ module-access.c: 337 context_check_access()] 0x55870ba539a0: client 0x55870bcbe110 wait for 'restricted' permissions
I found no documentation on how to get the old "access granted" behavior. E.g. setting access.allowed=.. in pipewire.conf to /usr/bin/pactl still gets the above output when running "pactl info" as "someuser".