One thing that really surprises me is this: # ls -ln /var/run/pipewire/pipewire-0 srw-rw---- 1 118 65534 0 24 sept. 20:29 /var/run/pipewire/pipewire-0=
But in /etc/group I have: pipewire:x:127: So the pipewire group does exist, which is confirmed by: # addgroup pipewire fatal: The group `pipewire' already exists. Also, /usr/lib/systemd/system/pipewire.socket says: SocketUser=pipewire SocketGroup=pipewire SocketMode=0660 So the group looks good. Evenmore strange to me, if I change the SocketMode=0660 so that it becomes: SocketMode=0666 After a reboot I get: # ls -ln /var/run/pipewire/pipewire-0 srw-rw-rw- 1 118 65534 0 24 sept. 20:36 /var/run/pipewire/pipewire-0= So one can see that the permission of the socket has changed, it has become readable and writeable by others, which was not the case initially. This is a temporary fix to the bug reported here, but it also shows that the systemd socket file _is_ read. Finally, once all this will be understood and fixed, it may be helpful for users to document tat the users that are allowed to use the system-wide pipewire service should be added to the pipewire group, meaning that it won't be enough to be in the audio group. Or the service uses the audio group rather than a dedicated pipewire one, but I assume this won't be correct either as piipewire supports both audio and video.
