OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
audio-input high very-common DISPUTE

Fix no sound at all when PipeWire reports no audio sinks

omarchyarchendeavouroscachyosmanjarohyprlandwaylandpipewirelaptopdesktop
AUDITED Audited against its sources and confirmed accurate.

Symptom

No sound at all. wpctl status shows no Sinks, or apps error out: [ao/pipewire] PipeWire does not have any audio sinks, skipping / [ao] Failed to initialize audio driver 'pipewire', and pactl info prints Connection failure: Connection refused. Volume keys do nothing.

Cause

PipeWire is socket-activated, so nothing starts until a client connects. If the client races WirePlumber, or if pipewire-pulse.service / wireplumber.service are not running (common after a fresh install, after removing pulseaudio, or after killing the daemons), there is no session manager to create the nodes and no PulseAudio shim for apps that speak the Pulse protocol.

Fix

Check what is actually running and what devices exist:


systemctl --user status pipewire pipewire-pulse wireplumber
wpctl status
pactl info

Make sure the compat packages are installed (pipewire-pulse replaces pulseaudio and pulseaudio-bluetooth, and pipewire-audio is required for Bluetooth audio):


pacman -Qs '^pipewire|^wireplumber'
sudo pacman -S --needed pipewire pipewire-audio pipewire-pulse pipewire-alsa wireplumber

Enable them explicitly instead of relying on socket activation:


systemctl --user enable --now pipewire.service pipewire-pulse.service wireplumber.service

If they were already running, restart the whole stack:


systemctl --user restart pipewire.service pipewire-pulse.service wireplumber.service

Verify

wpctl status lists at least one entry under Sinks with a * next to it, pactl info prints Server Name: PulseAudio (on PipeWire x.y.z), and speaker-test -c2 -twav -l1 produces sound.

Sources

pipewire-no-sinks-service-not-started