How to troubleshoot sound problems

Hank Lee, The Music and Audio SIG Version F40 Last review: 2025-04-15
This page covers some basic troubleshooting techniques to help narrow down the root cause of an issue. It also explains information that should be included when filing bugs related to sound. General sound problems - where the problem is observed across multiple applications - should usually be filed against the kernel, or PipeWire (see below for instructions on determining whether the problem is PipeWire-related). If the problem is observed only in a specific application, or only in applications which use a single multimedia library (such as SDL or OpenAL), the bug should be filed against that component.

Introduction

Sound problems in Fedora can arise from a variety of causes, ranging from misconfigured audio services to missing or outdated drivers. In most cases, these issues are related to the transition to PipeWire, Fedora’s default audio server since Fedora 34. While PipeWire aims to unify and improve audio handling across applications, its integration with legacy tools like PulseAudio and ALSA can sometimes lead to conflicts or device recognition problems.

Typical issues users may encounter:

  • No sound output or input

  • Only “Dummy Output” is available

  • Microphones not being detected

  • Audio devices missing after updates

  • Broken Bluetooth audio connections

This guide provides a step-by-step approach to diagnosing and resolving these sound issues. It covers both general troubleshooting and specific fixes for input-related problems, such as missing microphones or inactive input devices.

Diagnosing the Problem

  • Determining if the issue is with the kernel, PipeWire, or specific applications.

  • Collecting logs and system information.

Check which Kernel driver is in use by PCI devices

To display kernel drivers handling each device, use the lspci (List PCI) command with the option -k. Searching for known issues specific to driver’s name and your hardware model before reporting issues to Ask Fedora.

$ sudo lspci -k
bash

New hardware drivers are updated continuously. If you see a device listed as unknown, query your PCI device ID database.

$ sudo lspci -Q
bash

And update your local PCI ID database by running the command update-pciids.

$ sudo update-pciids
bash

ALSA Firmware

The ALSA Firmware package contains firmware for various third-party sound cards.

See which firmware is in use by running the following command.

$ sudo dnf list alsa-firmware
bash

The regular ALSA Firmware will appear <alsa-firmware.noarch>.

If the regular firmware is not on the output, install the alsa-firmware.

$ sudo dnf install alsa-firmware
bash

If any other firmware is installed, put them on blocklist on configuration directory for modprobe.

/etc/modprobe.d/*.conf

Add the line on configuration file.

blacklist <the module to blocklist>

The dracut tool creates an initial image used by the kernel for preloading the block device modules. The option -f overwrite existing initramfs file.

$ sudo dracut -f
bash

Reboot your computer for the change to take effect.

$ sudo reboot
bash

Hardware information

It is always useful to include detailed information on your sound hardware when filing a sound-related bug. To produce this information, run this command:

$ alsa-info.sh --no-upload
bash

It will generate a file containing detailed information about your sound hardware with the name /tmp/alsa-info.txt. Attach this file to your bug report.

Is it PipeWire?

PipeWire is a media sharing server, low-level multimedia framework that aims to;

  • improve handling of audio and video under Linux

  • work for all users at all levels

  • offer support for PulseAudio, JACK (JACK Audio Connection Kit), ALSA and GStreamer-based applications

Visual checks on ports

Qpwgraph is a graph manager dedicated to PipeWire.

Visual checks on ports using Qpwgraph will help discover all the routing between applications and devices and change the routing as you need. For example, if multiple applications and devices are connected and disconnected like below,

  • Firefox: video conference application using WebRTC protocol

  • VLC: media playback

  • OBS Studio: live stream and recording

  • USB soundcards or mixers: devices

it will be useful to learn how ports are connected to applications and devices graphically.

Ports are directional, they can be either:

  • Source ports (output). Located at the right-most edge of a node, they generate an audio/video/midi stream.

  • Sink ports (input). Located at the left-most edge of a node, they consume an audio/video/midi stream.

Ports also have different types:

  • Audio (default color: green)

  • Video (default color: blue)

  • PipeWire/JACK MIDI (default color: red)

  • ALSA MIDI (default color: purple)

Ports of the same type and opposite directions can be connected.

Check the upstream documentation for user guide Qpwgraph User Guide.

Resolving Audio Input Issues

Follow these steps to resolve most audio input issues.

Solution steps:

Step 1: Reinstall PipeWire and Related Packages

Make sure the necessary PipeWire components are installed and working correctly.

sudo dnf reinstall pipewire pipewire-pulseaudio pipewire-alsa wireplumber
bash

Then reboot your system.

Step 2: Check Audio Service Status

Ensure that the PipeWire and WirePlumber services are active.

systemctl --user status pipewire
systemctl --user status wireplumber
bash

If they are not running, enable them:

systemctl --user enable --now pipewire
systemctl --user enable --now wireplumber
bash

Step 3: Verify User Permissions

Check that your user belongs to the correct groups:

groups
bash

If audio is missing, add it:

sudo usermod -aG audio $USER
bash

Step 4: Reset configuration files

If the audio configuration is corrupted, you can reset it by moving the old config folders:

mv ~/.config/pulse ~/.config/pulse_backup
mv ~/.config/pipewire ~/.config/pipewire_backup
bash

Then reboot your system.

Step 5: Check hardware

If you’re using an external microphone, try reconnecting it or testing with a different device to rule out hardware issues.

Debugging options

Debugging usually starts after the bug has been identified, and works best when users are very familiar with the circumstances surrounding the bug.

PipeWire has its own debugging options. Please see the upstream documentation PipeWire debugging.

Need More Help?

If the above steps don’t resolve your issue, visit the Fedora community:

Contributions and feedback help improve Fedora documentation for everyone.

Want to help? Learn how to contribute to Fedora Docs ›