Fixing "Audio Only Works for One Program" on Ubuntu

In the Ubuntu of multimedia troubleshooting, few things are as frustrating as "audio locking." This occurs when one application (like a web browser or a game) takes exclusive control of your sound card, preventing any other program from making noise. In 2026, with Ubuntu 24.04 LTS and 25.10 primarily using PipeWire, this issue usually stems from a configuration mismatch or a legacy app bypassing the modern sound server. This guide will help you restore multi-stream audio mixing.

1. The Primary Cause: ALSA Exclusive Mode

The most common reason for this "one-app" limit is an application accessing ALSA (Advanced Linux Sound Architecture) directly. ALSA is a low-level driver that, by default, does not support mixing multiple streams. Modern sound servers like PipeWire and PulseAudio sit on top of ALSA to allow multiple apps to share the hardware. If an app bypasses them, it locks the "door" behind it.

• Common Culprits: Professional audio tools (DAWs), older games running via Wine, or misconfigured media players.
• The Fix: Check the application’s settings and ensure the "Audio Output" or "Driver" is set to PulseAudio, PipeWire, or Default rather than "ALSA" or "Hardware Device."

2. Restarting the PipeWire Sound Server

If your sound was working fine and suddenly became "locked" to one program, the PipeWire or WirePlumber session manager may have crashed or stalled. In 2026, Ubuntu relies on these services to handle all audio routing.

1. Open your terminal (Ctrl+Alt+T).
2. Run the following command to restart the user-level audio services:
   systemctl --user restart pipewire pipewire-pulse wireplumber
3. Restart your applications. This should force them to re-handshake with the mixer.

3. Managing Audio Streams with Pavucontrol

Sometimes the audio isn't "locked," but rather the system has incorrectly assigned a specific app to a "Dummy Output" or a different hardware device. The best way to visualize this in Ubuntu Categories is using the PulseAudio Volume Control (pavucontrol) utility, which still works perfectly with PipeWire in 2026.

4. Fixing "Exclusive" Professional Audio (JACK)

If you use Ubuntu Studio or professional software like Ardour or Bitwig, you might be using JACK. Historically, JACK required exclusive control. In 2026, PipeWire acts as a bridge for JACK, but if you have a legacy "JACK Bridge" or "Studio Controls" setup enabled, it might still be seizing control of the hardware.

• The Solution: If you are an enthusiast, ensure you have the pipewire-jack package installed. This allows your professional apps to "play nice" with Firefox, Spotify, and other desktop apps simultaneously.
• Command: sudo apt install libspa-0.2-jack pipewire-jack

5. Troubleshooting "Busy" Devices

If you see an error in the terminal like "Device or resource busy," you can identify exactly which process is holding the audio lock. Run this command:

sudo fuser -v /dev/snd/

This will list the PID (Process ID) of the program currently using the sound card. You can then close that program or kill it using kill -9 [PID] to free up the audio for the rest of the system.

Conclusion

Audio locking on Ubuntu is almost always a result of an application bypassing the PipeWire mixing layer. By ensuring your apps are set to use the system default output and keeping your wireplumber service healthy, you can enjoy multiple streams at once. In the 2026 Ubuntu Categories landscape, the shift to PipeWire has made these issues rarer, but a quick service restart is still the most reliable fix. For those pursuing performance in their media setups, always verify that your user is part of the audio group using groups $USER.

Keywords

Ubuntu audio only one program at a time fix, PipeWire audio mixing issues Ubuntu 24.04, fix exclusive audio mode Linux 2026, Ubuntu 25.10 sound locked to one app, systemctl restart pipewire wireplumber, Linux device or resource busy audio fix, PulseAudio vs PipeWire mixing, Ubuntu Categories audio help.