Comment # 10 on bug 1205640 from Bart Verhagen

@Takashi Iwai: Restarting wireplumber does not work for me. Before writing this
pull request, I tried restarting pipewire.service and pipewire-pulse.service,
but this did not work either.

@Antonio Larrosa: The system seems to think it is playing sound, but there is
no sound to be heard from the device. It is not the volume (neither the system
volume nor the volume on the device itself).

The ~/.config/pipewire folder was not present. After adding the pipewire.conf
file, the issue was not resolved (not even after a reboot).

After playing `paplay /usr/share/sounds/alsa/test.wav`, the output is:

```
$ cat /proc/asound/card*/pcm0p/sub0/hw_params
closed
closed
```

Some more logs:

$ journalctl --user -u wireplumber
Nov 22 20:57:36 eriador systemd[3528]: Started Multimedia Service Session
Manager.
Nov 22 20:57:36 eriador wireplumber[3773]: Can't find xdg-portal: (null)
Nov 22 20:57:36 eriador wireplumber[3773]: found session bus but no portal
Nov 22 20:59:56 eriador systemd[3528]: Stopping Multimedia Service Session
Manager...
Nov 22 20:59:56 eriador wireplumber[3773]: stopped by signal: Terminated
Nov 22 20:59:56 eriador wireplumber[3773]: disconnected from pipewire
Nov 22 20:59:56 eriador systemd[3528]: Stopped Multimedia Service Session
Manager.
Nov 22 20:59:56 eriador systemd[3528]: Started Multimedia Service Session
Manager.


$ journalctl --user -u pipewire
Nov 22 20:57:36 eriador systemd[3528]: Started PipeWire Multimedia Service.
Nov 22 20:57:36 eriador pipewire[3772]: pw.context: 0x560a63e3a6c0: no modules
loaded from context.modules
Nov 22 20:57:36 eriador pipewire[3772]: default: acquire_rt
thread:0x7ffb3ec546c0 prio:-1 not implemented

$ journalctl --user -u pipewire-pulse
Nov 22 20:57:56 eriador systemd[3528]: Started PipeWire PulseAudio.
Nov 22 20:58:26 eriador pipewire-pulse[4242]: Connection failure: Timeout