How to Fix No Sound or Audio Crackling in Steam Games on Linux Mint (2026 Guide)

Priya

Content Writer & Researcher

Last Updated: 15 October 2026
How to Fix No Sound or Audio Crackling in Steam Games on Linux Mint (2026 Guide)
🖥️

Still Hearing Static? Let a Linux Expert Fix It for You

Our Linux desktop specialists diagnose PipeWire, PulseAudio, and Steam audio conflicts on your exact hardware configuration. Pay only per ticket — no subscription, no guesswork.

🖥️12,400+PCs Fixed
⭐4.9★Google Rating
⚡<15 minAvg. Response
🛡️ISO 27001Certified

You just booted up your favourite Steam game on Linux Mint, only to be greeted by dead silence — or worse, a wall of crackling static that makes the game unplayable. System sounds work fine. Music plays. Yet the moment you launch Steam, audio vanishes or distorts beyond recognition.

You are not alone. This is one of the most commonly reported problems after upgrading to Linux Mint 21.x or 22, and the root cause nearly always traces back to how PipeWire replaced PulseAudio as the default sound server. Steam and many Proton-translated games still expect the older PulseAudio behaviour, and PipeWire's compatibility layer does not always cooperate. This guide walks you through every proven fix, from a 30-second command to a full sound-server rollback, so you can get back to gaming without buying a new OS.

Why Steam Games Lose Sound on Linux Mint 22 (PipeWire vs PulseAudio)

Linux Mint 21 shipped with PulseAudio as the default sound server. Starting with Mint 21.3 and carrying into Mint 22, the distro transitioned to PipeWire — a modern, low-latency audio and video framework. PipeWire is better in many ways: lower latency, better Bluetooth handling, and native JACK support for audio production. However, the transition introduced a compatibility layer called pipewire-pulse that impersonates PulseAudio. Steam, SDL2, and many game engines expect to talk directly to PulseAudio, and they occasionally misdetect or misuse the compatibility shim.

The result is a frustrating split: your desktop speakers work perfectly because applications like Firefox and Rhythmbox use PipeWire's native APIs, while Steam games silently fall back to a broken ALSA path or fail to open an audio stream at all.

Common symptoms of this conflict include:

  • No audio in Steam games while system sounds play normally
  • Audio crackling, popping, or static after a few minutes of gameplay
  • Sound cuts out mid-session, requiring a game restart
  • HDMI audio working on the desktop but absent inside games
  • Error messages in Steam's console referencing ALSA or audio device unavailability

Step 1: Identify Your Active Sound Server (PipeWire or PulseAudio)

Before changing anything, confirm which audio stack is actually running. Open a terminal and run:

pactl info | grep "Server Name"

You will see one of two outputs:

# PipeWire with PulseAudio compatibility layer:
Server Name: PulseAudio (on PipeWire 1.x.x)

# Native PulseAudio:
Server Name: pulseaudio

To get a broader picture of your audio hardware and active driver, use:

inxi -A

Also check whether WirePlumber (PipeWire's session manager) is running:

systemctl --user status wireplumber pipewire pipewire-pulse

If any of those three units shows a status of failed or inactive, that is your first culprit. Restart all three in one command:

systemctl --user restart wireplumber pipewire pipewire-pulse

Then relaunch Steam. If sound returns, the session manager had crashed — a known intermittent bug on PipeWire versions below 1.0.7.

Step 2: Fix Audio Crackling and Dropouts in PipeWire

If you are on PipeWire and games produce crackling or intermittent dropouts rather than complete silence, the issue is almost always related to the audio buffer quantum — the size of the audio chunk PipeWire processes per cycle. Games using SDL2 or older OpenAL builds often request a very small quantum that conflicts with PipeWire's default settings.

Quick Runtime Fix (No Reboot Required)

Run this pair of commands while Steam is closed:

pw-metadata -n settings 0 clock.force-rate 48000
pw-metadata -n settings 0 clock.min-quantum 512

The first command locks PipeWire's sample rate to 48000 Hz, which is what most games and Steam's audio engine expect. The second raises the minimum buffer size to 512 frames, eliminating the underruns that cause crackling. These settings reset after a reboot, so test them first before making them permanent.

Permanent PipeWire Configuration

To make the fix survive reboots, create a custom PipeWire configuration file:

mkdir -p ~/.config/pipewire/pipewire.conf.d/
nano ~/.config/pipewire/pipewire.conf.d/10-gaming.conf

Paste in the following content:

context.properties = {
    default.clock.rate          = 48000
    default.clock.min-quantum   = 512
    default.clock.max-quantum   = 8192
}

Save the file (Ctrl+O, then Ctrl+X), then restart PipeWire:

systemctl --user restart wireplumber pipewire pipewire-pulse

Force Steam to Use ALSA Directly

For games that still crackle even after tuning PipeWire, you can bypass PipeWire entirely at the per-game level. In Steam, right-click the problematic game, choose Properties, and in the Launch Options field enter:

SDL_AUDIODRIVER="alsa" %command%

This tells SDL2 to talk to ALSA directly, skipping PipeWire's compatibility shim. It works well for older Unity, Unreal Engine 4, and Source engine games that have stubborn audio pipelines.

Step 3: Switch Back to PulseAudio If PipeWire Keeps Breaking

If the crackling persists or you experience complete audio loss that only resolves after restarting PipeWire, the cleanest solution for a gaming-focused machine is to revert to PulseAudio. PulseAudio is stable, battle-tested, and still fully supported on Linux Mint 22.

Remove PipeWire and Install PulseAudio

sudo apt remove pipewire pipewire-pulse wireplumber pipewire-alsa pipewire-audio-client-libraries
sudo apt install pulseaudio pulseaudio-utils pavucontrol
sudo apt autoremove

After the packages are removed and installed, reboot your system:

sudo reboot

After rebooting, verify PulseAudio is now active:

pactl info | grep "Server Name"
# Expected output: Server Name: pulseaudio

Launch Steam and test your games. In our experience, this resolves audio issues in over 90 percent of cases where PipeWire instability was the root cause.

Optional: Re-enable PipeWire Later

If you later want to try PipeWire again (for example, to use Bluetooth headphones or low-latency audio), install it freshly rather than mixing packages:

sudo apt install pipewire pipewire-pulse wireplumber pipewire-alsa
systemctl --user --now enable wireplumber pipewire pipewire-pulse
systemctl --user disable pulseaudio pulseaudio.socket

Step 4: Force Steam to Use the Correct Audio Device

Even with a healthy sound server, Steam sometimes locks onto the wrong audio device — for example, an internal monitor speaker or a disconnected Bluetooth sink that is still registered in the PulseAudio/PipeWire device list. This causes complete silence because audio is being sent to a device that produces no output.

Set the Default Sink

First, list all available audio output sinks:

pactl list short sinks

You will see output like:

47  alsa_output.pci-0000_00_1f.3.analog-stereo    PipeWire    s32le 2ch 48000Hz    RUNNING
52  alsa_output.hdmi-stereo                        PipeWire    s32le 2ch 48000Hz    SUSPENDED

Identify the sink name corresponding to your speakers or headphones (typically analog-stereo for the headphone jack, hdmi-stereo for HDMI). Set it as the default:

pactl set-default-sink alsa_output.pci-0000_00_1f.3.analog-stereo

Replace the sink name with the one from your own pactl list short sinks output. Then restart Steam completely (not just the game) and test audio again.

Move Existing Streams to the Correct Sink

If Steam is already running and you just changed the default sink, move the existing audio stream without restarting:

# Get the Steam audio stream index
pactl list short sink-inputs

# Move stream (replace INPUT_INDEX and SINK_NAME with real values)
pactl move-sink-input INPUT_INDEX SINK_NAME

Step 5: Fix HDMI Audio and Multi-Monitor Sound in Steam Games

HDMI audio in Steam games is a particularly common pain point on Linux Mint because HDMI audio devices are enumerated separately from analog outputs, and PipeWire's ALSA compatibility layer sometimes presents them in an order that confuses game engines.

Check HDMI Sink Detection

pactl list sinks | grep -A5 "hdmi\|HDMI"

If the HDMI sink shows SUSPENDED, the system sees it but has put it to sleep. Wake it and set it as default:

pactl set-default-sink alsa_output.hdmi-stereo
pactl set-sink-volume alsa_output.hdmi-stereo 80%

Force HDMI Audio via Steam Launch Options

For games that still ignore the HDMI sink, use the launch option to specify the ALSA device directly. First, find your HDMI ALSA card and device number:

aplay -l | grep HDMI

Example output: card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]

Then set the launch option in Steam to:

ALSA_PCM_CARD=1 ALSA_PCM_DEVICE=3 SDL_AUDIODRIVER=alsa %command%

Adjust card and device numbers to match your aplay -l output.

Static Noise on HDMI

If HDMI audio works but produces static or white noise, this is typically a sample-rate mismatch between the game engine and the HDMI receiver. Lock PipeWire to 48000 Hz as described in Step 2, or set the ALSA hardware rate explicitly:

nano ~/.asoundrc

Add:

defaults.pcm.rate_converter "speexrate_medium"

Save and restart Steam.

Additional Troubleshooting Tips

If none of the above steps fully resolve the issue, these additional checks cover edge cases that trip up Linux Mint gaming setups:

  • Verify Steam runtime audio libraries: Run steam steam://validate/ to force Steam to check and repair its runtime files, including bundled audio libraries.
  • Check for conflicting JACK installations: If you have JACK installed from a previous audio production setup, it can claim audio devices before PipeWire. Run systemctl --user stop jack and retest.
  • Update PipeWire via PPA: Linux Mint's repositories sometimes lag behind upstream. Adding the PipeWire PPA gives you version 1.0.7 or later, which fixed several gaming-related audio lock-up bugs: sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream && sudo apt update && sudo apt upgrade pipewire wireplumber
  • Check Proton-specific audio: For Windows games running via Proton, add PROTON_USE_WINED3D=1 to launch options if audio works in native Linux games but not in Proton titles.

If you have worked through every step here and still face audio problems specific to your hardware or game, get expert desktop support — our Linux specialists diagnose audio stack conflicts and game-specific issues on a pay-per-ticket basis, so you only pay when the problem is solved.

Summary

Audio issues in Steam games on Linux Mint almost always come down to the PulseAudio-to-PipeWire transition. Here is the decision tree in brief:

  1. Restart PipeWire services first — resolves crash-related silence instantly.
  2. Tune PipeWire's clock quantum — eliminates crackling caused by buffer underruns.
  3. Use SDL_AUDIODRIVER=alsa per game — bypasses the compatibility shim for stubborn titles.
  4. Roll back to PulseAudio — the nuclear option that works when PipeWire instability is chronic.
  5. Fix device routing via pactl — corrects audio being sent to the wrong sink.
  6. Configure ALSA card/device for HDMI — resolves multi-monitor audio routing.

With these steps, most Linux Mint gamers can restore full, crackle-free audio in under ten minutes. The PipeWire ecosystem is improving rapidly in 2026 — kernel 6.8+ and PipeWire 1.2+ have significantly reduced the gaming-specific bugs — so if you rolled back to PulseAudio, it is worth retrying PipeWire in a few months.

Get the Free Linux Server Admin Cheatsheet (PDF)

Essential commands for server management, networking, and troubleshooting — all on one printable page.

Running Linux servers? Let us manage them for you.

Our Managed Linux Server plans cover updates, security hardening, monitoring, and 24/7 incident response — so your servers stay up and your team stays focused.

  • Proactive OS patching and security updates
  • 24×7 monitoring with instant alerting
  • Backup configuration and disaster recovery
  • Dedicated Linux engineers on call
See Pricing Plans →

What our customers say

“Our production server went down at 2 AM. CloudHouse had it back online in under 20 minutes. Incredible response time.”

Arun S.

CTO, SaaS Startup

“They migrated our entire infrastructure from Ubuntu 18 to 22 with zero downtime. Couldn't have asked for better.”

Deepak N.

DevOps Lead

Frequently Asked Questions

This is almost always caused by the PipeWire sound server's PulseAudio compatibility layer (pipewire-pulse) not initialising correctly when Steam launches. Steam and many game engines expect native PulseAudio behaviour. Restarting PipeWire services with 'systemctl --user restart wireplumber pipewire pipewire-pulse' usually resolves it immediately.

Need this done for you?

Linux Mint Support

Hands-on help for Linux Mint desktops and laptops.

Learn more

Book your free 15-minute diagnosis

A certified technician will call you back within 15 minutes during business hours.

Share this article

Leave a Comment

Comments (0)

Loading comments...