You are not logged in.
Ie. the wireplumber upddate causes pipewire-pulse errors but pipewire fails silently (ie. no sound but also no errors)?
I had a quick look through my journal and, though I see some errors relating to pipewire, pipewire-pulse, and wireplumber, none of them really seem to correlate with whether or not I hear audio. Also they show in logs months ago. Maybe my audio setup is just sort of held together with duct-tape in general.
So I guess it kind of failed silently, because the no-audio issue doesn't correspond to a clear error message as far as I can tell, and it didn't make any programmes visibly crash.
Anyway, I'm not trying to troubleshoot right now since my audio works after a downgrade. Maybe this information will be useful to others trying to figure out what's going on, though.
EDIT: Wait, was what I quoted a response to me? It's hard to tell, because it's above the part where you quoted me, but some people on forums put responses above quotes instead of below them.
Last edited by 256 (2026-10-04 16:34:39)
"Don't comment bad code - rewrite it." - The Elements of Programming Style (1978), Brian W. Kernighan & P. J. Plauger, p. 144.
Offline
Ie. the wireplumber upddate causes pipewire-pulse errors but pipewire fails silently (ie. no sound but also no errors)?
So, all the time we think it's wireplumber but it's actually pipewire
. Thank you for sharing all the information, and good to know that they already identify it and work on it. Hopefully, it will fix soon.
Offline
No, that sentence just summarizes the symptoms on your system.
Wireplumber is a session and policy manager for pipewire, its update breaks it so it's wireplumber's fault.
Offline
seth wrote:Since there seems a pattern of WP 5.17 breaking setups,
This is weird, because my system broke due to an upgrade to 0.5.18, and downgrading to 0.5.17 fixed it. I suppose recent WirePlumber versions have just been buggy in general. My personal plan is to just wait for a few more versions until threads about audio problems stop showing up, then upgrade.
My last system upgrade I ran out of space on `/` partway through. Downgrading WP from 0.5.18 to 0.5.17 fixed it for me, but afterwards I was able to upgrade to 0.5.18 and things are still working.
My downgrade to 0.5.17 also replaced pulseaudio (from aur?) with pipewire-pulse:
$ sudo pacman -U *.zst
loading packages...
warning: downgrading package libwireplumber (0.5.18-1 => 0.5.17-2)
warning: downgrading package wireplumber (0.5.18-1 => 0.5.17-2)
warning: downgrading package wireplumber-docs (0.5.18-1 => 0.5.17-2)
resolving dependencies...
looking for conflicting packages...
:: pipewire-pulse-1:1.6.9-1 and pulseaudio-17.0+r98+gb096704c0-1 are in conflict. Remove pulseaudio? [y/N] y
Packages (7) pipewire-pulse-1:1.6.9-1 pipewire-system-services-1:1.6.9-1 pulseaudio-17.0+r98+gb096704c0-1 [removal]
libwireplumber-0.5.17-2 wireplumber-0.5.17-2 wireplumber-docs-0.5.17-2
wireplumber-system-services-0.5.17-2I have no idea why `pulseaudio-17.0+r98+gb096704c0-1` was installed...
It seems pretty obvious in my case that downgrading itself wasn't the fix but that rather downgrading just happened to pull in the correct packages (pipewire-pulse) and maybe fixed a broken install. Maybe some of the other "downgrade fixed it" were also "other problems were fixed during the downgrade".
Offline