pipewire-pulse "silently" fails
If you are filing this issue with a regular release please try master as it might already be fixed.
Version, Distribution, Desktop Environment: git ec331f4e , Ubuntu 20.10 (Groovy Gorilla)
Description of Problem: when pipewire-pulse is run from systemd it fails with the following in the journalctl log: pipewire-pulse: [W][000012722.601155][pulse-server.c:6313 pw_protocol_pulse_new()] pulse-server 0x564570a93f50: can't create server for unix:native: Device or resource busy
When run at the command line using the following: /usr/bin/pipewire-pulse
things run just fine.
How Reproducible: It happens every time pipewire-pulse is run from systemd
Steps to Reproduce:
- systemctl start --user pipewire
- systemctl start --user pipewire-media-session
- systemctl start --user pipewire-pulse
Actual Results: After running the following: journalctl -xe --user --unit=pipewire-pulse.service
The "warning" appears in the log. Expected Results: The warning should not appear
Additional Info Eg.
pw-dump -N > file (As Attachment Please):
When this warning appears, nothing can connect and utilize the sound system. At least nothing as far as X or even the system preferences can connect to the sound system. From what I can gather, pulse-server.c line 5894 fails with EAGAIN, which is changed in reporting to EBUSY (I had to add a few extra logs to the source to figure that out). I am not sure why the "connect" call is returning EAGAIN, but I can't easily use this with systemd unless someone can point me to where things might be going wrong. I pretty much have to stop the process, and run it from bash in order to get sound to work.