Audio Not Working On Ubuntu | Fixes That Actually Work

Guide / By

No sound on Ubuntu? Follow these steps to select the right device, restart audio, and fix HDMI, Bluetooth, mic, and driver issues.

When sound drops out on a Linux desktop, you lose more than music. System prompts go silent, meetings stall, and videos feel broken. This guide gives you a clean path to bring audio back on Ubuntu. You’ll start with fast checks, then move to device selection, service restarts, and port-specific fixes for HDMI, Bluetooth, and USB headsets. Every step is safe to try and easy to undo.

Audio Not Working On Ubuntu — Root Causes And Quick Map

Quick map: most “no sound” cases come down to the wrong output device, muted channels, or a stuck audio service. Cable and codec quirks show up with HDMI and Bluetooth. Input problems are often a privacy toggle or level setting. The table below links common symptoms to the first fix you should try.

Symptom Likely Cause Fast Try
No audio from speakers Wrong output picked or muted sink Open Sound Settings → choose speakers → raise Volume
Headphones quiet or silent Auto-switch failed or low app volume Re-select headphones → check app’s volume slider
HDMI screen plays video, no sound HDMI device not set as output Pick the HDMI output → enable TV speakers
Bluetooth pairs but no audio Profile stuck on “Hands-Free” Switch profile to “A2DP” in Bluetooth settings
Mic not detected Input muted or wrong source Select the mic under Input → raise Input Volume
Sound dies after sleep Service hung or driver hiccup Restart audio services from terminal

Quick Checks That Solve Most Sound Issues

Before changing deeper settings, run these short checks. Each step rules out a common blocker and often restores audio in seconds.

  1. Check Physical Volume — Tap the top-right menu, slide Volume up, then press the keyboard volume keys. Some laptops keep a separate hardware mute.
  2. Test With Another App — Play a local audio file, then a web video. If one works and the other doesn’t, fix the app’s own audio output setting first.
  3. Replug Or Reboot Peripherals — Unplug and reconnect headphones, speakers, docks, and USB hubs. Switch the 3.5 mm jack between ports if available.
  4. Try A Fresh User Session — Log out and back in. A new session clears a stuck audio graph without a full reboot.
  5. Reboot Once — A full restart reloads devices and often clears stale routes after kernel updates or sleep.

Fix Output Selection And Volume On Ubuntu

Goal: make sure the system is sending sound to the device you expect. Ubuntu can add or lose outputs as you plug cables, pair headsets, or switch displays.

  1. Open Sound Settings — Click the system menu → Settings → Sound. Keep this window open while you test.
  2. Pick The Correct Output Device — Under Output, click through each listed device (Speakers, Headphones, HDMI, USB DAC) and play test audio after each switch.
  3. Raise System And App Levels — Raise the main Output Volume. Then open your player’s own volume slider and turn it up as well.
  4. Unmute Hidden Channels — Some devices have separate left/right or PCM channels. If you see tiny sliders, bring them up evenly.
  5. Disable Audio Enhancers — If you installed an equalizer or effects tool, turn it off to rule out misroutes.

Tip: if switching outputs inside Settings works only until the next reboot, delete stale device profiles so Ubuntu rebuilds them the next time the hardware appears. Use the “fresh config” step later in this guide.

Restart Audio Services And Drivers

When levels look right but sound is still missing, restart the audio stack. This refresh clears most post-update and post-sleep issues.

  1. Restart PipeWire Fast — Press Ctrl+Alt+T and run: 
    systemctl --user restart wireplumber pipewire pipewire-pulse

    Play audio again. If it returns, you’re done.

  2. Fallback To PulseAudio — On older releases you may be on PulseAudio. Try: 
    pulseaudio -k

    It will respawn. Test sound right after.

  3. Reload ALSA Devices — This refreshes the kernel sound layer: 
    sudo alsa force-reload

    Wait a few seconds, then test again in Sound Settings.

  4. Rebuild User Audio State — If restarts work only once, clean user configs: 
    mv ~/.config/pulse ~/.config/pulse.bak 2>/dev/null
mv ~/.config/pipewire ~/.config/pipewire.bak 2>/dev/null
systemctl --user restart wireplumber pipewire pipewire-pulse

    Re-select your output device after the rebuild.

Heads-up: these commands touch user-space services and cached profiles only. They don’t change drivers or kernel modules. If nothing changes, move to the device-specific steps below.

Microphone Not Working On Ubuntu — Input Fixes That Stick

Input devices can be muted by privacy toggles, per-app permissions, or a low gain setting. This section restores voice for calls, screen recordings, and voice chat.

  1. Select The Right Input — Settings → Sound → Input. Pick the mic you’re using (built-in, USB, webcam, or headset boom).
  2. Raise Input Volume — Speak while watching the level meter. Slide Input Volume until the meter peaks near the yellow range without clipping.
  3. Grant App Access — Open the app’s audio settings and pick the same mic. Some browsers and meeting apps hold their own device list.
  4. Disable “Hands-Free” When You Want Quality — Bluetooth mics switch to a call profile that cuts quality and can break output. For music and clear input, set the device profile to A2DP for output and use a wired mic for input, or switch profiles only during calls.
  5. Test In A Simple Recorder — Try Sound Recorder or a minimal app. If this works while a browser doesn’t, reset the site’s mic permission and re-choose the device.

HDMI, Bluetooth, And USB Audio — Connection-Specific Fixes

Different ports add different quirks. Use the path that matches your setup.

HDMI Output To A TV Or Monitor

  • Select The HDMI Sink — Settings → Sound → choose the HDMI device that matches your display model.
  • Enable TV Speakers — Open the TV’s audio menu and set speakers to “TV” or “External” as needed. Some sets default to ARC devices.
  • Wake The Link — Unplug and replug the HDMI cable while the TV is on the active input. Then re-pick HDMI in Settings.
  • Match Sample Rates — If you hear pops or silence on 5.1 tracks, switch the app to stereo and test again. Add surround only after stereo works.

Bluetooth Headsets And Earbuds

  • Forget And Pair Cleanly — Settings → Bluetooth → remove the headset → pair again while it’s in pairing mode.
  • Pick The Music Profile — In the device details, select the A2DP profile for audio playback. Avoid “Hands-Free” unless you’re in a call.
  • Block App Auto-Switching — Meeting apps can snap the profile to call mode and mute music. Close the app when you’re done to return to A2DP.
  • Charge The Headset — Low battery can drop the link or lock the mic. Charge to full and test again.

USB DACs, USB Mics, And Docks

  • Plug Directly First — Connect to a primary USB port, then test. Reintroduce hubs or docks after you confirm sound works.
  • Check Port Speed — Some DACs behave better on USB-A than on certain USB-C hubs. Try another port or a short certified cable.
  • Re-Rank Devices — After plugging a DAC, return to Sound Settings and pick it as Output and, if it has one, as Input.

Deeper Fixes: Drivers, Kernels, And Fresh Config

When basic steps fail, dig a layer deeper. These actions don’t change your files, but they reset how the system discovers and routes audio.

  1. List Devices The Kernel Sees — Run: 
    aplay -l
arecord -l

    If your card is missing here, the problem sits below the desktop. Check cables and BIOS audio settings, then continue.

  2. Reset User Audio Config — Rebuild per-user audio state: 
    mv ~/.config/pulse ~/.config/pulse.bak 2>/dev/null
mv ~/.config/pipewire ~/.config/pipewire.bak 2>/dev/null
systemctl --user restart wireplumber pipewire pipewire-pulse

    Pick your devices again in Settings.

  3. Install Missing Codecs — If media files are silent in one player only, install the standard media extras: 
    sudo apt update
sudo apt install ubuntu-restricted-extras

    Try the same file again after install.

  4. Update The System — Kernel and firmware updates often include sound fixes: 
    sudo apt update
sudo apt upgrade

    Reboot once and test all outputs.

  5. Try The Latest LTS HWE Stack — On LTS releases, install newer hardware enablement bits: 
    sudo apt install linux-generic-hwe-22.04

    Replace the version with your LTS line. Reboot and test.

When Nothing Works: Clean Slate And Logs

Stubborn cases need a clean slate and a quick look at logs. The steps below keep risk low while giving you useful signals.

  1. Create A New Test User — Add a temporary user, log in, and test audio. If it works, the issue sits in your main profile’s settings.
  2. Check Dmesg For Driver Errors — Run: 
    dmesg | grep -iE 'snd|hda|audio'

    Look for errors around your last boot. A missing firmware message points to a package you can install.

  3. Check Journal For Service Issues — Run: 
    journalctl --user -u pipewire -u wireplumber -u pipewire-pulse --since -2h

    Reproduce the issue while this runs. Errors here guide the next step.

  4. Reinstall The Audio Stack — Refresh desktop audio packages: 
    sudo apt install --reinstall pipewire wireplumber pipewire-pulse

    If you’re on older PulseAudio-only systems, reinstall pulseaudio and pavucontrol instead.

  5. Roll Back A Breaking Change — If audio died after a driver or kernel bump, boot the previous kernel from the GRUB “Advanced options” menu and test.

Make Fixes Stick After Reboots

Once you’ve fixed the problem, lock in stable behavior so it doesn’t slip again.

  • Set Your Preferred Devices — Keep your daily output and input selected in Sound Settings. Re-pick them once after major updates.
  • Limit Auto-Switching — Disconnect Bluetooth headsets you don’t use often. Disable any background app that grabs the mic on login.
  • Update On A Calm Day — Run system updates when you have time to test audio right after. It’s easier to spot what changed.
  • Keep A Rescue Script — Save the restart commands in a text file. Run it when sound dies after sleep or a dock reconnect.

Where This Guide Fits Your Exact Case

Different machines surface problems in different spots. Laptops can mute speakers when a headset leaves a ghost device behind. Desktops often shuffle outputs when you swap GPUs or docks. If your case reads like “audio not working on ubuntu right after I switched displays,” start with the HDMI steps. If it reads like “audio not working on ubuntu only in my browser,” reset the site’s permissions, then try the service restart path. The structure above keeps fixes scoped so you can move fast without breaking working parts.

One-Screen Checklist You Can Bookmark

  • Pick The Right Output — Settings → Sound → Output → test each device.
  • Raise Volumes — System slider up, app slider up, hidden channels unmuted.
  • Restart Audio — systemctl --user restart wireplumber pipewire pipewire-pulse
  • Refresh ALSA — sudo alsa force-reload then re-pick output.
  • Fix HDMI — Select HDMI sink, wake TV input, try stereo first.
  • Fix Bluetooth — Forget, re-pair, pick A2DP profile, charge the headset.
  • Fix Mic — Pick the right input, raise Input Volume, grant app access.
  • Rebuild Config — Move ~/.config/pipewire and ~/.config/pulse out, restart services.
  • Update System — sudo apt update && sudo apt upgrade

Follow the sections in order. You’ll either restore sound right away or gather clear clues for the next move. Once stable, keep the service restart line handy and updates tested, and your desktop will stay quiet only when you want it to.