Audio Not Working In Ubuntu | No-Sound Fixes That Work

Most Ubuntu sound failures come from output selection, mute states, or drivers; quick checks and clean resets usually restore audio.

When sound drops out on Ubuntu, the cause is usually simple: the wrong device, a muted level, or a stuck audio service. This guide walks you through fast checks first, then reliable fixes. Each step is safe to run, reversible, and uses tools already on your system. You’ll test output, reset the sound stack, and confirm drivers without hunting random forum threads.

Audio Not Working In Ubuntu: Fast Triage

Quick check: Confirm the output device and volume before anything deeper. Open Settings → Sound. Pick the speaker or headset you’re actually using, then slide Output Volume up. Tap the built-in test sound. If you hear tones, apps may be routing audio elsewhere; jump to the app fixes below.

Pick The Correct Output — In Settings ▸ Sound ▸ Output, switch between HDMI, Speakers, and Headphones; test each one.
Unmute Everywhere — Click the panel volume icon, raise the slider, then check per-app sliders in Settings ▸ Sound.
Set The Right Input — Microphone loops and echo cancelers can downmix audio; pick the intended input under Input.
Reconnect The Device — Reseat the 3.5 mm jack or USB plug. For Bluetooth, toggle it off and on, then reconnect.
Try Another App — Play a local file with Videos or Rhythmbox. If that works, the issue is isolated to one app.

For quick command-line verification, list sound cards and sinks. Open a terminal and run:

aplay -l
pactl list short sinks

If you see devices but still hear nothing, the sound server may be stuck. Move to the resets below.

Fixes For Ubuntu Sound Not Working Issues

Work through these fixes in order. Each one addresses a frequent root cause. Stop as soon as audio returns.

Reset The Active Sound Server

Restart PipeWire (Newer Ubuntu) — If your system uses PipeWire, restart the user services:
```
systemctl --user restart pipewire pipewire-pulse wireplumber
```
Restart PulseAudio (Older Ubuntu) — If PulseAudio is in use, reload it:
```
pulseaudio -k
pulseaudio --start
```

Clear Stuck Levels With Alsamixer

Open The Mixer — Run alsamixer. Use the arrows to pick the correct sound card with F6.
Unmute Channels — Press M to unmute Master, Speaker, and Headphone. Raise levels with the up arrow.
Write The State — Save settings:
```
sudo alsactl store
```

Rebuild Sound Devices After A Wake Or Dock Switch

Rescan The Bus — Power-cycle USB hubs and docks. Then reload USB audio:
```
sudo modprobe -r snd_usb_audio && sudo modprobe snd_usb_audio
```
Replug HDMI — Unplug the HDMI cable, wait five seconds, and reconnect; select the new HDMI output in Settings ▸ Sound.

Reset Per-User Sound Config

Move Old Config Out — Rename user audio folders so Ubuntu rebuilds clean defaults:

mv ~/.config/pulse ~/.config/pulse.bak 2>/dev/null
mv ~/.config/wireplumber ~/.config/wireplumber.bak 2>/dev/null

Restart Services — Start PipeWire or PulseAudio again using the commands above.

Device, App, And Permission Pitfalls

Even when the system is fine, one app can grab the wrong sink or block the device. Fix app-level routing and outputs here.

Web Browsers

Pick The Right Tab Output — Right-click a playing tab and pick the output device if the browser offers one. Some Chromium builds expose per-tab routing.
Check Site Mute — Click the lock icon in the address bar and allow sound for the site.
Close Extra Tabs — Media sessions can collide; pause other streams.

Video Editors And DAWs

Match The Backend — In app preferences, set the backend to PulseAudio or PipeWire as your system uses.
Pick The Device — Select the exact output device inside the app; avoid “default” if it keeps switching.
Nudge Buffer/Rate — If playback crackles, raise buffer size or align sample rate (44.1 kHz vs 48 kHz).

Flatpak And Snap Sandboxing

Update The Runtime — Pull fresh permissions and fixes:
```
flatpak update
snap refresh
```

Grant Sound Access — For Flatpak apps:

flatpak override --user --socket=pulseaudio

Bluetooth Quirks

Remove And Re-Pair — In Settings ▸ Bluetooth, remove the headset, then pair again.
Pick The Right Profile — Use the Headphones profile (A2DP) for music, not the Headset profile (HSP/HFP).
Disable Power Save — Some dongles idle too hard; keep the adapter on a direct USB port, not a low-power hub.

Driver And Kernel Checks That Matter

When new hardware stays silent, confirm the driver and kernel line-up. You don’t need to compile modules or chase nightly builds; Ubuntu ships helpers for most chipsets.

Identify Your Audio Hardware

List PCI Devices — For onboard audio:
```
lspci | grep -i audio
```
List USB Devices — For USB headsets and DACs:
```
lsusb | grep -i audio
```

Check Loaded Modules

Show Kernel Modules — Look for snd_hda_intel (HDA), snd_usb_audio (USB), or device-specific entries:
```
lsmod | grep -E 'snd|sound'
```
Dmesg For Audio Errors — Scan for codec init lines:
```
dmesg | grep -iE 'snd|hda|audio|alsa'
```

Refresh Drivers

Use Ubuntu Drivers — For systems with vendor options:

sudo ubuntu-drivers list
sudo ubuntu-drivers autoinstall

Update The Kernel Via HWE — On LTS releases, get newer hardware support:

sudo apt update
sudo apt install --install-recommends linux-generic-hwe-22.04

Common Symptoms Mapped To Likely Causes

This table links what you hear (or don’t) to fast tests that confirm the path forward.

Symptom	Likely Cause	Quick Test Or Fix
No sound after wake	Stuck PipeWire/PulseAudio	Restart user services; reselect output
Only HDMI is silent	Wrong HDMI sink picked	Select HDMI output; replug cable
Headphones quiet, speakers fine	Muted headphone channel	Unmute in alsamixer; save state
Bluetooth choppy voice	Headset profile (HSP/HFP)	Switch to A2DP profile
Browser silent, others ok	Per-app routing or site mute	Pick device in browser; allow sound
USB DAC not detected	Power-saving or hub issues	Use a direct port; reload module

Deep Clean: Reinstall Sound Packages Without Reimaging

If resets and mixer tweaks don’t stick, refresh the core audio packages. This keeps your files and apps intact.

Refresh PipeWire Stack

Install/Reinstall PipeWire Extras — Pull the PulseAudio compatibility layer and session manager:
```
sudo apt update
sudo apt install pipewire pipewire-pulse wireplumber
```

Enable On Boot — Make sure services start for your user:

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

Refresh ALSA Utilities

Install Tools — Ensure mixer and controls are present:
```
sudo apt install alsa-utils
```
Rebuild The ALSA State — Remove a bad cache and rescan:
```
sudo rm -f /var/lib/alsa/asound.state
sudo alsactl init
```

Repair Broken Packages

Fix Dependencies — Clean up partial installs:
```
sudo apt -f install
sudo apt full-upgrade
```
Reboot Once — A single reboot after package refresh helps the kernel pick up any module changes.

Edge Cases: Virtual Machines, Pro Audio, And Multi-User Setups

Some setups need one extra step. These are the frequent edge patterns and the fix that clears them.

Running Ubuntu In A VM

Use The Host Audio Bridge — In VirtualBox or VMware, enable the PulseAudio/ALSA host driver and the AC97/HDA virtual device.
Install Guest Additions — Audio support improves once guest tools match the host version.

Low-Latency Audio For Recording

Use The Low-Latency Kernel — Reduce dropouts:
```
sudo apt install linux-lowlatency
```
Start JACK Through PipeWire — PipeWire can present a JACK layer without complex routing:
```
pw-jack 
```

Multiple Users On One Machine

Run Audio In The Active Session — Log out other users. Only the active desktop user should own the sound server.
Reset The Current Session — If switching users mutes sound, run the PipeWire restart commands again after the switch.

Keep Sound Stable After You Fix It

Once audio plays, lock in small habits that prevent silent boots. These take seconds and save repeat work.

Update On A Schedule — Apply updates weekly:
```
sudo apt update && sudo apt upgrade
```
Limit Random Tweaks — Avoid mixing third-party PPA audio stacks unless you need hardware support they provide.
Stick To One Stack — Don’t run PulseAudio and PipeWire at the same time beyond the compatibility layer.
Label Cables — Tag HDMI and USB audio lines so you pick the right sink after a replug.
Back Up Good Config — After you get a stable mix, copy the audio config so you can roll back:
```
tar -czf ~/audio-config-backup.tgz ~/.config/pulse ~/.config/wireplumber 2>/dev/null || true
```

If you still face silence after all steps, gather a brief report before asking for help. Save the outputs of aplay -l, pactl list short sinks, and the last 50 lines of dmesg. Share both the hardware model and the Ubuntu release you’re on. This context speeds up a fix.

Two phrases often surface when people search for help: audio not working in ubuntu and device mismatch. The checks above target both. If a headset works but HDMI does not, test each sink and restart the sound server tied to your release. If no device outputs anything, focus on drivers and ALSA state. A small reset usually beats a full reinstall.

When the phrase audio not working in ubuntu pops up, the root cause tends to be a small setting change. Pick the right output, unmute the right slider, restart the sound server, and test again. These steps restore most systems in minutes without deep tweaks.