How to Remove PipeWire from a Linux Audio Setup

Before you start

Removing PipeWire affects how applications reach cameras, microphones, speakers and other audio or video devices. Check which audio server is installed on your distribution before changing packages. On many current systems PipeWire provides the session manager and replacement services for PulseAudio and JACK, so an uninstall can leave desktop applications without sound until another server is configured.

Run the package manager query for your distribution to identify the installed PipeWire packages. The main process normally runs as a user service, not only as a system service. A local restart of the desktop session is usually enough after replacement, but removal still requires administrator rights to change packages.

Step-by-step instructions

The exact package names depend on the distribution. On Debian-based systems, pipewire, pipewire-pulse, pipewire-audio-client-libraries and wireplumber may be present. On Fedora, the packages are pipewire, pipewire-pulseaudio and wireplumber. Open a terminal and inspect what is installed rather than removing a fixed list.

On a Debian or Ubuntu system, first list the relevant packages with:

dpkg -l | grep -E 'pipewire|wireplumber'

On Fedora, use:

rpm -qa | grep -E 'pipewire|wireplumber'

Stop the user services before removing packages if the session manager is still running. For a systemd user session, disable and stop the PipeWire services:

systemctl --user stop pipewire pipewire-pulse wireplumber 2>/dev/null
systemctl --user disable pipewire pipewire-pulse wireplumber 2>/dev/null

The service names can vary between versions. Older setups may use pipewire-media-session instead of wireplumber. A failed stop for a service that does not exist is not harmful.

If the goal is to return to PulseAudio, install its packages before or immediately after removing PipeWire. On Debian or Ubuntu this normally means installing pulseaudio and, for Bluetooth audio, pulseaudio-module-bluetooth. On Fedora the equivalent package is pulseaudio. Replacing the server while the desktop is running can leave the session without an active audio service until you log out and back in.

Remove the identified PipeWire packages. On Debian or Ubuntu, use:

sudo apt remove pipewire pipewire-pulse pipewire-audio-client-libraries wireplumber

On Fedora, use:

sudo dnf remove pipewire pipewire-pulseaudio wireplumber

Do not add packages to the command unless the package query confirmed they are installed. Removing an uninstalled name may produce an error, but removing the wrong package can delete a desktop dependency.

After the package operation, restart the user session. Log out and back in, or restart the system. This gives the replacement audio service a clean start and lets applications reconnect to the correct server.

Check the output

Open the sound settings in the desktop environment and confirm that the expected input and output devices are listed. Play a test sound through the output device and speak into the microphone while watching the input level. The exact test controls depend on the desktop, so use the controls shown on your system.

In a terminal, check whether PipeWire is still reported as the active server. With PulseAudio running, pactl info can show the server name and default sink. A command that only works with PipeWire should no longer succeed:

pactl info | grep 'Server Name'

If the server name still mentions PipeWire, the user service or a leftover configuration may be keeping the old server active. A logout and login is usually required before the check is meaningful.

Common problems and next steps

No sound devices appear after restart. This usually means no replacement service is enabled. Check that PulseAudio or another intended server is installed and enabled for the user session, then log out and back in.

An application still reports PipeWire. Some applications start a server automatically if one is missing, while others hold a connection to the old socket. Close the affected application completely after restarting the session, then open it again.

Audio plays but the input level is low or contains background noise. This is an audio setting problem, not evidence that PipeWire is still installed. Select the correct input device, move the microphone closer, reduce the input level if it is clipping, and lower nearby noise sources.

Package removal refuses to continue because another package depends on PipeWire. The package manager will normally list the dependency. Do not force the removal. Review the listed packages and install a supported replacement first, or keep the existing PipeWire service.

The desktop environment depends on PipeWire for audio. Some current desktop or compositor packages treat PipeWire as a required component. In that case uninstalling it may remove parts of the desktop. The package manager will show what would be removed before confirming; cancel the operation if the list includes essential desktop packages.