Dennis HilkLinux diagnosticsDE

Linux Gaming Repair Center

Audio is missing or crackles in Wine and Proton

Compare the host audio session with the game stream, routing, mute state and dropout evidence.

Editorial source review: Open the diagnostic assistants
On this page
  1. Check another application first
  2. Inspect the live game stream
  3. Crackling needs timing evidence
  4. Gather evidence
  5. A controlled test
  6. Related diagnostics
  7. Sources & limitations

Check another application first

If desktop audio is also missing, begin with the host’s devices, output profile and user-session services. If only one Wine or Proton game is silent, check whether it creates an audio stream and where that stream is routed. PipeWire commonly provides PulseAudio compatibility through pipewire-pulse, but the installed sound server must be established rather than assumed. A running PipeWire process alone does not prove that the game sees the right interface. Bluetooth headset modes, HDMI outputs and a game’s own device selection can change the route without removing the sound card.

Inspect the live game stream

While the game is producing sound, inspect the desktop mixer or wpctl status. Compare the game stream’s mute state and destination with a working application. A saved default output and an already-running stream can differ, so switching the default device may leave the stream unchanged. For standalone Wine, keep the correct runner and prefix when examining its audio configuration; opening an unrelated system winecfg can inspect the wrong environment. Proton’s Steam prefix should not be opened with a random system Wine version as an initial repair.

Crackling needs timing evidence

Crackling under load is different from a silent or muted stream. Observe whether PipeWire error counters increase at the same time as frame-time or I/O spikes. An xrun supports a missed audio deadline, not a diagnosis of an insufficient sound card. CPU scheduling, device clock behavior, transport and graph quantum can all matter. Do not prescribe a universal sample rate or minimum latency. A lower latency setting can make dropouts worse, while a larger buffer can mask scheduling pressure. Preserve the existing configuration and start with routing checks before changing audio timing.

Gather evidence before changing the system

Run one command at a time in the relevant host or game environment. Read its requirements and interpretation first. The website displays commands and never runs them.

Read-only observation

wpctl status

Requirements: PipeWire with WirePlumber and wpctl; a different sound server needs its own tools.

Compare sinks and streams while the game emits sound. An absent game stream and a present but misrouted stream lead to different next steps.

Read-only observation

wpctl get-volume @DEFAULT_AUDIO_SINK@

Requirements: WirePlumber with a valid default playback sink.

Read the default sink’s volume and mute state. This is not necessarily the destination of a game stream that was opened earlier.

Read-only observation

systemctl --user status pipewire pipewire-pulse wireplumber --no-pager

Requirements: systemd user services and a PipeWire/WirePlumber installation; no sudo.

Check services in the game user’s session. A missing unit may reflect a different configured audio stack, not a service crash.

Read-only observation

pw-top

Requirements: PipeWire tools with access to the current user’s audio graph.

Watch the active game stream and ERR counters during a short dropout. Counter changes support timing evidence; stop with q or Ctrl+C.

A controlled test with a way back

Record the game stream’s current output and volume in the desktop mixer. Move only that stream to a known-working output and compare with another application at moderate volume.

Rollback: Restore the stream’s previous output, volume and mute state in the mixer. Stop pw-top. No system-wide sample-rate or PipeWire configuration change is needed for this test.

What this test cannot establish: A correctly routed stream can still fail inside the game or compatibility runtime. Audio that continues during a display freeze does not prove that the GPU is healthy or that the whole system stayed responsive.

Sources and scope

This editorial review uses primary project and distribution references. It does not establish that a fix has been reproduced on your hardware. Installed versions, the game runtime and the selected graphics API can change the result.