You’re kidding, right? To accomplish what, exactly?
I’m using PulseAudio with a Xorg GNOME session using NVIDIA graphics on my main laptop and PipeWire with a Wayland GNOME session using AMD graphics on my other laptop. There’s a reason for that. Both work wonderfully.
Either way, this subject is off-topic now that we sorted things with the audio server.
@manjbobWe don’t have enough information to troubleshoot your issue.
Why don’t we start with your system info?
I’m taking a break, so I may not respond until tomorrow
This was meant solely in regard to this issue - installing manjaro-pipewire would probably “fix” this as well. We’ll see in next stable update if this is a single occurrence.
I don’t advise using the 5.9 kernel until it’s stable–especially on the stable branch. 5.19-rc5 is out now and should be in the unstable branch in the next day or so.
If the tried and true, stable PulseAudio sound server is working fine for him (which by his first post it is), switching to PipeWire is illogical.
Indeed. And until this moment I thought inxi is just reporting it wrongly, since all those people with problems, on PulseAudio, most probably didn’t enable PipeWire manually.
Well, it turns out pipewire.socket happily starts it for you, even though user never asked for it.
Illogical is a bit strong word here. If you replaced “PulseAudio/PipeWire” with “X11/Wayland”, you probably wouldn’t say the same for people switching to Wayland.
I’d argue that - IF - PipeWire (or Wayland) doesn’t cause you any problems, then it is logical to switch to it. I do understand however that this isn’t the case for everyone.
As long as I can play videos, games, etc reasonably reliably, I’m not too bothered whether it’s using Pipewire or Pulseaudio. I’m more concerned whether a forthcoming Wireplumber update might mess things up again, although I accept that’s one of the risks in using the unstable branch.