# Ubuntu Audio Troubleshooting Guide

> When addressing audio issues audio issues usually come down to one of the following Power something off and on restart a system service and reinstall the app

Source: https://knowledgebase.frame.work/en_us/ubuntu-audio-issues-Bkw2Wlf2o

Last updated: 2025-09-17T06:45:32.944Z

**Compatibility:** This guide works with PulseAudio, PipeWire, ALSA for Ubuntu and Ubuntu-based distributions.

  

### Table of Contents

*   📋 [Overview & Common Issues](#overview)
*   🔍 [Step 1: Run the Diagnostic Script](#diagnostic)
*   ⚙️ [Step 2: Check Basic Configuration](#basic-config)
*   🔧 [Step 3: Quick Fixes Based on Results](#quick-fixes)
*   🔄 [Step 4: Service Management](#service-management)
*   🎤 [Microphone Troubleshooting](#microphone)
*   💤 [Step 5: After Suspend/Resume Issues](#suspend-resume)
*   📊 [Step 6: Generate Full Diagnostic Report](#full-report)[](#still-issues)

##   

## Overview & Common Issues

  

When addressing audio issues, problems usually come down to one of the following:

*   **Power cycling** - Turning hardware or services off and on
*   **Restarting system services** - Refreshing audio daemons
*   **Configuring the correct audio profile** - Ensuring proper device selection
*   **Reinstalling appropriate libraries** - Fixing corrupted packages
*     
    

**Important:** Sometimes the audio IS working despite what you may see or hear. Often it's merely something on the user configuration side that is causing the issue.

  

**Common Quick Checks:**

*   No audio with YouTube/media? Check your Ubuntu sound settings to see if the sound meter shows activity
*   If the meter doesn't move, you may be muted - press the Volume Up key on your keyboard
*   Check for attached USB headsets and 3.5mm jack connections to earbuds
*   Verify the video/media isn't muted in the browser

![Ubuntu Sound Settings](https://cdn.kustomerhostedcontent.com/media/6047cd84502177bce9fccae2/bed86ed8db1964d9725f56db9952fc0f.png)

## Step 1: Run the Diagnostic Script

  

### 🚀 Quick Start: Automated Diagnosis

  

**First,** [**download and use**](https://github.com/FrameworkComputer/linux-docs/tree/main/misc/audio-diagnostic#-linux-audio-diagnostic-script) **our diagnostic script to identify the exact issue:**

\# One-line download and run
sudo apt update && sudo apt install curl -y && curl -s https://raw.githubusercontent.com/FrameworkComputer/linux-docs/refs/heads/main/misc/audio-diagnostic/audio-diagnostic.sh -o audio-diagnostic.sh && chmod +x audio-diagnostic.sh && bash audio-diagnostic.sh

  

**Alternative step-by-step approach:**

\# 1. Download the script
curl -s https://raw.githubusercontent.com/FrameworkComputer/linux-docs/refs/heads/main/misc/audio-diagnostic/audio-diagnostic.sh -o audio-diagnostic.sh

# 2. Make it executable
chmod +x audio-diagnostic.sh

# 3. Run basic diagnostic
./audio-diagnostic.sh

# 4. Run with test tone to verify audio output
./audio-diagnostic.sh -t

# 5. Check recent issues (useful after suspend/resume)
./audio-diagnostic.sh --since "10 minutes ago"

# 6. Verbose mode for detailed information
./audio-diagnostic.sh -v

**Note:** The audio-diagnostic.sh script is a comprehensive universal audio diagnostic tool that checks your audio services, defaults, routing, profiles, and logs. Works with both PulseAudio and PipeWire.

  

**Understanding the script output:**

✅ Green checkmarks = Working correctly

⚠️ Yellow warnings = Potential issues to investigate

❌ Red X marks = Problems found

ℹ️ Info icons = Important information

##   

## Step 2: Check Basic Configuration

  

**Before diving into terminal commands, check these common issues:**

1.  **Check System Sound Settings**
    *   Open Settings → Sound → Output Device
    *   Verify the correct output device is selected
    *   Check that volume is not muted or at zero
    *   Watch the visual meter while playing audio
2.  **Verify Physical Connections**
    *   Ensure headphones/speakers are properly connected
    *   Check USB connections for external audio devices
    *   Try different ports if available
3.  **Test with Different Applications**
    *   Try playing audio from different sources
    *   Test system sounds (Settings → Sound → Sound Effects)
    *   Use `speaker-test -c 2` in terminal for basic test

##   

## Step 3: Quick Fixes Based on Script Results

###   

### If script shows "Dummy Output" or "No Default Sink":

  

#### Ubuntu Quick Fix:

\# For PipeWire (Ubuntu 22.10+):
systemctl --user restart wireplumber pipewire pipewire-pulse

# For PulseAudio (Ubuntu 20.04/22.04):
systemctl --user restart pulseaudio

# Check if services are running
systemctl --user status pipewire pipewire-pulse wireplumber

# Or for PulseAudio:
systemctl --user status pulseaudio

# Check audio system info via PulseAudio layer  
pactl info

###   

### If script shows wrong device selected:

\# List sinks
pactl list short sinks

# Set default (use the NAME from the list)
pactl set-default-sink alsa\_output.pci-0000\_00\_1f.3.analog-stereo

# For PipeWire systems, you can also use:
wpctl status
wpctl set-default 67  # Replace 67 with your device ID

# Or use GUI: Settings → Sound → Output Device

###   

### If script shows profile is OFF:

\# Check device profiles
pactl list cards

# Or use GUI: Settings → Sound → Configuration → Select "Analog Stereo Duplex"

###   

### Dummy audio or no sound card detected fix:

\# Common fix for dummy output issue
echo "options snd-hda-intel dmic\_detect=0" | sudo tee -a /etc/modprobe.d/alsa-base.conf

# Followed by:
echo "blacklist snd\_soc\_skl" | sudo tee -a /etc/modprobe.d/blacklist.conf

# Then REBOOT your system

# If this doesn't help, you can undo with:
sudo sed -i 's/options snd-hda-intel dmic\_detect=0//' /etc/modprobe.d/alsa-base.conf
sudo sed -i 's/blacklist snd\_soc\_skl//' /etc/modprobe.d/blacklist.conf

##   

## Step 4: Service Management - UBUNTU SPECIFIC

  

**⚠️ UBUNTU ONLY:** Ubuntu uses PulseAudio (20.04/22.04) or PipeWire (22.10+). These commands are specific to Ubuntu.

###   

### Restarting Audio Services on Ubuntu

  

**Recap of above:** Most Ubuntu audio issues can be resolved with:

\# For PipeWire (Ubuntu 22.10+):
systemctl --user restart wireplumber pipewire pipewire-pulse

# For PulseAudio (Ubuntu 20.04/22.04):
systemctl --user restart pulseaudio

\# UBUNTU: Restart PipeWire services (Ubuntu 22.10+)
systemctl --user restart wireplumber pipewire pipewire-pulse

# UBUNTU: Restart PulseAudio (Ubuntu 20.04/22.04)
systemctl --user restart pulseaudio

# UBUNTU: Check service status
# For PipeWire:
systemctl --user status pipewire pipewire-pulse wireplumber

# For PulseAudio:
systemctl --user status pulseaudio

# UBUNTU: Enable services to start on boot
# For PipeWire:
systemctl --user enable pipewire pipewire-pulse wireplumber

# For PulseAudio:
systemctl --user enable pulseaudio

###   

### Ubuntu Package Reinstallation Commands

####   

#### Reinstall PipeWire on Ubuntu (22.10+):

\# UBUNTU: Complete PipeWire reinstallation
sudo apt install --reinstall libpipewire-0.3-0 libpipewire-0.3-common libpipewire-0.3-modules

# UBUNTU: Reinstall all PipeWire components
sudo apt install --reinstall pipewire pipewire-audio-client-libraries pipewire-bin pipewire-pulse wireplumber

# UBUNTU: Install additional PipeWire packages if missing
sudo apt install pipewire-alsa pipewire-jack

# UBUNTU: Force reinstall with all dependencies
sudo apt install --reinstall pipewire\* wireplumber\*

####   

#### Reinstall PulseAudio on Ubuntu (20.04/22.04):

\# UBUNTU: Complete PulseAudio reinstallation
sudo apt install --reinstall libpulse0 libpulsedsp pulseaudio pulseaudio-module-bluetooth pulseaudio-utils

# UBUNTU: Install missing modules
sudo apt install pulseaudio-module-jack pulseaudio-equalizer

# UBUNTU: Reinstall all PulseAudio packages
sudo apt install --reinstall pulseaudio\*

####   

#### Reinstall ALSA on Ubuntu (All versions):

\# UBUNTU: Reinstall ALSA packages
sudo apt install --reinstall alsa-base alsa-utils linux-sound-base libasound2

# UBUNTU: Install firmware if missing
sudo apt install firmware-sof-signed

# UBUNTU: Reinstall all ALSA-related packages
sudo apt install --reinstall alsa\*

# UBUNTU: Reload ALSA after reinstall
sudo alsactl restore

####   

#### Additional Ubuntu-Specific Troubleshooting:

\# UBUNTU: Check for package conflicts
sudo apt check

# UBUNTU: Update all audio-related packages
sudo apt update
sudo apt upgrade pipewire\* pulseaudio\* alsa\* wireplumber\*

# UBUNTU: Clean APT cache and reinstall
sudo apt clean
sudo apt install --reinstall pipewire pipewire-pulse wireplumber alsa-base
# Or for PulseAudio:
sudo apt install --reinstall pulseaudio pulseaudio-utils alsa-base

# UBUNTU: Install missing kernel modules
sudo apt install linux-modules-extra-$(uname -r)

# UBUNTU: Check audio group membership
sudo usermod -a -G audio $USER

# UBUNTU: Install pavucontrol for GUI management
sudo apt install pavucontrol
pavucontrol  # Opens advanced audio control panel

  

**Ubuntu Note:** After reinstalling packages, always restart the audio services using:  
`systemctl --user restart wireplumber pipewire pipewire-pulse` (for PipeWire)  
`systemctl --user restart pulseaudio` (for PulseAudio)

##   

## Microphone Troubleshooting

**Framework Laptop Users:** First, ensure the hardware privacy switch at the top of your screen isn't toggled off!

###   

### Hardware Privacy Switch (Framework Laptops)

**Toggled off, no input:**

![Microphone Switch Off](https://cdn.kustomerhostedcontent.com/media/6047cd84502177bce9fccae2/fb4dd97198f76828dade0077dfc406f1.jpg)

**Toggled on, mic has input and is active:**

![Microphone Switch On](https://cdn.kustomerhostedcontent.com/media/6047cd84502177bce9fccae2/0efaf0d73139dbc3639313de6b403816.jpg)

###   

### Check if Input Registers in Sound Settings

  

![Ubuntu Input Level Meter](https://cdn.kustomerhostedcontent.com/media/6047cd84502177bce9fccae2/ce6440d02e75c374ebefb6f4c5b74288.png)

If the input level does not register when you speak, check the following:

####   

#### 1\. Ensure the microphone is not muted in Settings:

*   Open Settings → Sound → Input
*   Check that the microphone slider is not all the way to the left (muted)
*   Ensure the correct input device is selected from the dropdown
*   Test by speaking and watching the input level meter

![Ubuntu Microphone Settings](https://cdn.kustomerhostedcontent.com/media/6047cd84502177bce9fccae2/30dc588370427e03e6fa33f7fa21ac50.png)

####   

#### 2\. Check application-specific permissions:

*   Some applications (Zoom, Teams, Discord) have their own audio settings
*   Check Settings → Privacy → Microphone to ensure apps have permission
*   For browsers, check site permissions (usually a microphone icon in the address bar)

####   

#### 3\. Verify the correct input device is selected:

*   You may have multiple input devices (built-in mic, USB webcam mic, Bluetooth headset)
*   The wrong device might be selected as default
*   In Settings → Sound → Input, select the correct device from the dropdown

###   

### Command Line Microphone Troubleshooting

\# Check default source
pactl info | grep "Default Source"

# Set source volume
pactl set-source-volume @DEFAULT\_SOURCE@ 75%

# Unmute source
pactl set-source-mute @DEFAULT\_SOURCE@ 0

# Test microphone with recording
arecord -d 5 test.wav && aplay test.wav

# Install pavucontrol for easier management
sudo apt install pavucontrol
pavucontrol  # Opens GUI for detailed audio control

##   

## Step 5: After Suspend/Resume Issues

Audio breaking after suspend/resume is a common issue. Here's how to diagnose and fix it:

\# Check what happened during resume
# For PipeWire:
journalctl --user -u wireplumber --since "5 minutes ago"
journalctl --user -u pipewire --since "5 minutes ago"

# For PulseAudio:
journalctl --user -u pulseaudio --since "5 minutes ago"

# Run diagnostic script to check for issues
./audio-diagnostic.sh --since "10 minutes ago" -v

# Quick fix - restart audio services
# For PipeWire (Ubuntu 22.10+):
systemctl --user restart wireplumber pipewire pipewire-pulse

# For PulseAudio (Ubuntu 20.04/22.04):
systemctl --user restart pulseaudio

**Tip:** You can create a script to automatically restart audio services after resume if this is a recurring issue.

##   

## Step 6: Generate Full Diagnostic Report

If problems persist, generate a complete diagnostic report to share when seeking help:

(
    echo "=== Audio Diagnostic Report ==="
    echo "Date: $(date)"
    echo "System: $(uname -a)"
    echo "Ubuntu: $(lsb\_release -a 2>/dev/null)"
    echo
    echo "=== Script Diagnostic ==="
    ./audio-diagnostic.sh -v
    echo
    echo "=== Audio Status ==="
    pactl info
    echo
    echo "=== Audio Devices ==="
    aplay -l
    arecord -l
    echo
    echo "=== Recent Logs ==="
    journalctl --user -u pulseaudio -u pipewire -u wireplumber --since "1 hour ago" --no-pager 2>/dev/null
    echo
    echo "=== Kernel Modules ==="
    lsmod | grep -E 'snd|audio'
    echo
    echo "=== Package Versions ==="
    dpkg -l | grep -E 'pipewire|pulseaudio|alsa|wireplumber'
) > audio-report-$(date +%Y%m%d-%H%M%S).txt

echo "Report saved to audio-report-\*.txt"

##   

##   

_Last Updated: 2025 | Compatible with PulseAudio and PipeWire | Ubuntu-focused_