Fix PipeWire Audio: 7-Step Linux Troubleshooting Guide 🔊

🧠 Visual Operational Summary

This visualization gives you an overview of the problem before diving into technical details. It serves as a conceptual roadmap for the investigation that follows.

🌐 AUDIO PROBLEM ON TUMBLEWEED
│
├── 🚨 USER SYMPTOM
│   ├── Main: No audio output
│   ├── Context: After system update
│   └── Impact: Total silence, mute applications
│
├── ⚠️ SYSTEM MANIFESTATION
│   ├── Component: WirePlumber (audio session manager)
│   ├── Error: Segmentation Fault (SIGSEGV)
│   ├── Behavior: Crash-reboot loop
│   └── Evidence: Core dump generated, restart counter > 300
│
├── 🔍 TECHNICAL DIAGNOSIS
│   ├── Immediate Cause: ABI conflict (Application Binary Interface)
│   │   ├── Binary ≠ Library
│   │   └── Incompatible memory structures
│   │
│   └── Root Cause: Inconsistent repository mixing
│       ├── wireplumber : v0.5.13 (third-party repo)
│       └── libwireplumber : v0.5.12 (official repo)
│
├── 🛠️ VALIDATED CORRECTION
│   └── Systemic realignment
│       ├── Goal: Version consistency
│       ├── Method: Synchronization upwards
│       └── Action: Alignment on single source
│
└── 🧪 INVESTIGATION METHODOLOGY
    ├── Approach: Progressive elimination
    ├── Technique: Core dump forensic analysis
    ├── Audit: Complete package verification
    └── Validation: Multiple functional tests
        

🧭 Phase 0: Initial Context – The Investigation Ground

Identified System Context

Technical Context: Wayland and Audio Services

On KDE Plasma with Wayland, audio services run in user context (--user), not at system level. This means PipeWire and WirePlumber run in the user session and depend entirely on the consistency of their local environment.

Quick Decision Guide

INITIAL DIAGNOSIS: Do you have these symptoms?

┌─────────────────────────────────────────────────────────────┐
│ systemctl --user status wireplumber                         │
│ ➜ Status: failed (Result: core-dump)                      │
│ ➜ Signal: SIGSEGV (Segmentation Fault)                    │
│ ➜ Behavior: Repeated restart loop                         │
└─────────────────────────────────────────────────────────────┘

   YES (all symptoms) → You are in the right place ✓
   NO (other symptoms) → Check: volume, default device,
                          pipewire & pipewire-pulse status
        

🩺 Step 1: Initial Observation and Surface Diagnosis

1.1 Audio Services Status - Systemd's Testimony

Command:
systemctl --user status wireplumber
        

Practical Case - Decisive Observation

× wireplumber.service - Multimedia Service Session Manager
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
     Active: failed (Result: core-dump) since Sat 2026-01-10 09:19:25 CET; 2min 26s ago
   Duration: 1.576s
    Process: 41682 ExecStart=/usr/bin/wireplumber -p $WIREPLUMBER_PROFILE (code=dumped, signal=SEGV)
   Main PID: 41682 (code=dumped, signal=SEGV)
        

1.2 Log Analysis - Evidence of Crash Loop

Command:
journalctl -b --user-unit=wireplumber --no-pager | tail -30
        

Practical Case - Observed Result

wireplumber.service: Main process exited, code=dumped, status=11/SEGV
wireplumber.service: Failed with result 'core-dump'.
wireplumber.service: Scheduled restart job, restart counter is at 5.
wireplumber.service: Start request repeated too quickly.
wireplumber.service: Failed with result 'core-dump'.
Failed to start Multimedia Service Session Manager.
        

🔍 FORENSIC ANALYSIS OF SYSTEMD LOGS
├── ⚠️  Confirmed failure: Failed with result 'core-dump'
│    └── Signature: code=dumped, status=11/SEGV
├── 🔄  Infernal loop: Restart counter
│    ├── Initial: 5
│    ├── Intermediate: 292
│    └── Final observed: 348
└── ⏱️  Rapid crash: Start request repeated too quickly
    └── Implication: Service too unstable for systemd
        

🧱 Step 2: Hardware and Driver Investigation

2.1 PCI audio hardware identification

Command:
sudo lspci -v | grep -A5 -i "audio"
        

Practical Case - Observed Result

00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kabini HDMI/DP Audio
        Subsystem: Hewlett-Packard Company Device 226b
        Flags: bus master, fast devsel, latency 0, IRQ 44
        Memory at fea64000 (64-bit, non-prefetchable) [size=16K]
--
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 02)
        Subsystem: Hewlett-Packard Company Device 226b
        Flags: bus master, slow devsel, latency 32, IRQ 16
        Memory at fea60000 (64-bit, non-prefetchable) [size=16K]
        Kernel driver in use: snd_hda_intel
        

2.2 Kernel driver verification

Command:
lsmod | grep -E "snd_|sof_|hda"
        

Practical Case - Observed Result

snd_hda_codec_alc269   147456  1
snd_hda_intel          69632  0
snd_hda_codec         225280  6 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek_lib,snd_hda_codec_alc269,snd_hda_codec_atihdmi
snd_hda_core          151552  7 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek_lib,snd_hda_codec_alc269,snd_hda_codec_atihdmi
        

🧩 Step 3: Software and Configuration Investigation

3.1 Search for corrupted configurations

find /etc/wireplumber/ /usr/share/wireplumber/ ~/.config/wireplumber/ -type f -name "*.conf" -empty
        

3.2 Test in Minimal Mode

systemctl --user stop wireplumber
WIREPLUMBER_PROFILE=minimal wireplumber
        

🧪 MINIMAL STARTUP TEST
├── Minimal mode = FUNCTIONAL ✓
├── Full mode = SIGSEGV CRASH ❌
└── Implication: Problem in Lua config, not binary
        

🔬 Step 4: In-depth Diagnosis - Forensic Analysis

4.1 Quantify the Crisis: The Crash Loop

coredumpctl list wireplumber
        

4.2 Autopsy with GDB

coredumpctl debug wireplumber

(gdb) bt full
        

Practical Case - Autopsy Results

#0  0x00007f7a9a54364b wp_properties_get (libwireplumber-0.5.so.0 + 0x3e64b)
#1  0x00007f7a9864c63e n/a (libwireplumber-module-lua-scripting.so + 0x1d63e)
#2  0x00007f7a985db9fe n/a (liblua5.4.so.5 + 0x129fe)
#3  0x00007f7a985e757d n/a (liblua5.4.so.5 + 0x1e57d)
#4  0x00007f7a985e97ca n/a (liblua5.4.so.5 + 0x207ca)
#5  0x00007f7a985dc58a n/a (liblua5.4.so.5 + 0x1358a)
#6  0x00007f7a985d6d5b n/a (liblua5.4.so.5 + 0xdd5b)
#7  0x00007f7a985d8dce n/a (liblua5.4.so.5 + 0xfdce)
#8  0x00007f7a985dc6a0 lua_pcallk (liblua5.4.so.5 + 0x136a0)
#9  0x00007f7a9864d2a9 n/a (libwireplumber-module-lua-scripting.so + 0x1e2a9)
#10 0x00007f7a98652032 n/a (libwireplumber-module-lua-scripting.so + 0x23032)
        

🔬 CORE DUMP FORENSIC ANALYSIS
├── 💥 Impact Point: Crash in wp_properties_get
│    └── Library: libwireplumber-0.5.so.0
├── 🧩 Execution Context: Call via Lua scripting module
│    ├── Module: libwireplumber-module-lua-scripting.so
│    └── Function: lua_pcallk
└── 🚨 Dereferencing Evidence: Attempt to access address 0x1f
     └── Indication: Corrupted pointer (almost NULL)
        

4.3 The Irrefutable Warning: ABI Divergence

warning: .dynamic section for "/lib64/libwireplumber-0.5.so.0"
         is not at the expected address
         (wrong library or version mismatch?)
        

wireplumber --version
        

wireplumber
Compiled with libwireplumber 0.5.13
Linked with libwireplumber 0.5.12
        

⚠️ CRITICAL WARNING

Compiled with X vs Linked with Y
      ↓
FATAL ABI INCOMPATIBILITY
      ↓
100% guaranteed SIGSEGV
        

🧮 Step 5: Root Cause Investigation - Package Audit

5.1 Forensic Audit of Installed Versions

zypper search -s -i 'wireplumber*' 'libwireplumber*' 'pipewire*' | grep -E "^i|Repository" | sort
        

Practical Case - Criminal Result

🕵️ RECONSTITUTED SCENARIO
├── 📦 Third-party repo (home:pallaswept)
│    └── Offers: WirePlumber 0.5.13
├── 🏛️ Official repositories
│    └── Maintain: WirePlumber 0.5.12
└── 💥 Result: Mixed installation → Guaranteed ABI conflict
        

5.2 Repository and Priority Analysis

zypper lr -P
        

Practical Case - Result

🧠 Step 6: Strategic Debate and Corrective Action

6.1 The Dilemma: Regression vs Version Upgrade

Two paths were available to resolve incompatibility between wireplumber (v0.5.13) and libwireplumber (v0.5.12):

Option A: Regression to official version (v0.5.12)

sudo zypper in --from openSUSE-Tumbleweed-Oss wireplumber
        

Advantages: Return to a known stable state from official repository.

Disadvantages: On Tumbleweed (rolling release), deliberately regressing a package goes against the natural flow of updates and creates temporal inconsistency.

Option B: Library version upgrade (v0.5.13)

sudo zypper in -f libwireplumber-0_5-0 --from home:pallaswept
        

Advantages: Respects rolling release principle by synchronizing all components to the most recent version.

Disadvantages: Relies on a third-party repository (home:pallaswept) for future stability.

6.2 Why version upgrade is consistent

WHY IS VERSION UPGRADE CONSISTENT?
═════════════════════════════════════════════════════════════════

TUMBLEWEED PHILOSOPHY: CONTINUOUS ADVANCEMENT FLOW

        t₀ (yesterday)      t₁ (today)            t₂ (tomorrow)
        ════════           ═══════════════        ═════════════

Official:  0.5.12              0.5.12                0.5.13
           ├─────────────────────┬─────────────────────┤
           │                     │                     │
Third:     0.5.13              0.5.13                0.5.14
           ├─────────────────────┬─────────────────────┤
           │                     │                     │

┌─────────────────────────────────────────────────────────────┐
│ OUR SITUATION AT t₁:                                        │
│ • wireplumber       : 0.5.13 (third-party, installed)   ✅ │
│ • libwireplumber    : 0.5.12 (official)          ❌ CLASH   │
└─────────────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────┐
│ OPTION A (Regression): Go backwards                         │
│                                                              │
│       t₁ (now)                                              │
│       ═══════════════════                                    │
│       wireplumber  : 0.5.12 ← TEMPORAL BACKWARD STEP ❌     │
│       libwireplumber : 0.5.12 ✅ (consistent)               │
│                                                              │
│   ⚠️  Temporal inconsistency: system goes backward          │
│   ⚠️  Goes against rolling release philosophy               │
└─────────────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────┐
│ OPTION B (Upgrade): Advance together ✅ RECOMMENDED         │
│                                                              │
│       t₁ (now)                                              │
│       ═══════════════════                                    │
│       wireplumber  : 0.5.13 ✅                              │
│       libwireplumber : 0.5.13 ✅ (consistent)               │
│                                                              │
│   ✅ Temporal consistency: everything up to date             │
│   ✅ Respects rolling release: we advance together          │
│   ✅ Prepared for t₂: ready for next updates                │
└─────────────────────────────────────────────────────────────┘
        

6.3 Immediate Correction: Version Alignment

Preliminary verification: available versions of libwireplumber-0_5-0 :

zypper search -s -r home:pallaswept -r openSUSE-Tumbleweed-Oss libwireplumber-0_5-0
        

Version 0.5.13 available in home:pallaswept. ✓

Correction Execution

sudo zypper in -f --from home:pallaswept libwireplumber-0_5-0
        

6.4 Post-Correction Verification: ABI Consistency Confirmed

rpm -q wireplumber libwireplumber-0_5-0
        

wireplumber-0.5.13+git20251223.84429b4-6.3.x86_64
libwireplumber-0_5-0-0.5.13+git20251223.84429b4-6.3.x86_64
        

wireplumber --version
        

wireplumber
Compiled with libwireplumber 0.5.13
Linked with libwireplumber 0.5.13
        

6.5 Post-Correction Audit: PipeWire Validation

rpm -q pipewire pipewire-aptx && echo "Consistent versions" || echo "Attention required"
        

pipewire-1.5.84-2.2.x86_64
pipewire-aptx-1.5.84-1699.1.pm.1.x86_64
Consistent versions
        

✅ Step 7: Cleanup, Reset and Validation

7.1 Systemd Environment Cleanup

systemctl --user enable --now pipewire.socket
systemctl --user enable --now pipewire.service
systemctl --user enable --now pipewire-pulse.socket
systemctl --user enable --now pipewire-pulse.service
systemctl --user enable --now wireplumber.service
        

systemctl --user status wireplumber --no-pager
        

● wireplumber.service - Multimedia Service Session Manager
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
     Active: active (running) since Sat 2026-01-10 11:32:47 CET; 26s ago
   Main PID: 79646 (wireplumber)
      Tasks: 7 (limit: 12984)
     Memory: 18.4M
        CPU: 245ms
     CGroup: /user.slice/user-1000.slice/session-c4.scope/app.slice/wireplumber.service
             └─79646 /usr/bin/wireplumber -p "$WIREPLUMBER_PROFILE"

Jan 10 11:32:47 tumbleweed systemd[1234]: Started Multimedia Service Session Manager.
        

7.2 Complete Stability Verification

Test 1: Service Status

systemctl --user status wireplumber --no-pager | grep -E "Active|Main PID|code=dumped"
        

Result: Active: active (running) – no more SEGV ✓

Test 2: Audio Functionality

wpctl status
        

PipeWire 'pipewire-0' [1.5.84, crisis@tumbleweed, cookie:2244450242]
 └─ Clients:
        42. WirePlumber [export]                [1.5.84, crisis@tumbleweed, pid:79646]
        52. WirePlumber                         [1.5.84, crisis@tumbleweed, pid:79646]

Audio
 ├─ Devices:
 │      34. Internal Audio                      [alsa]
 │      46. Internal Audio                      [alsa]
 ├─ Sinks:
 │  *   38. Internal Audio Analog Stereo       [vol: 0.40]
 │      66. Internal Audio Digital Stereo (HDMI) [vol: 0.40]
        

Test 3: Effective Audio Test

aplay /usr/share/sounds/alsa/Front_Center.wav
        

Result: Audible sound without error ✓

🔧 Prevention Script: audio_check.sh

Script Execution Flow

Before discovering the complete code, here is the diagram explaining how the script works, step by step:

┌─────────────────────────────────────────────────────┐
│ 1. Execute: ./audio_check.sh                        │
└────────────┬────────────────────────────────────────┘
             │
    ┌────────▼────────┐
    │ [1/5] ABI TEST  │  ← CRITICAL TEST
    └────────┬────────┘
             │
    ┌────────▼──────────────────────────────┐
    │ Extract COMPILED version              │
    │ Extract LINKED version                │
    │ Display both values                   │
    └────────┬──────────────────────────────┘
             │
    ┌────────▼──────────────────────────────┐
    │ Test version match                    │
    │ COMPILED = LINKED ?                   │
    └────────┬──────────────────────────────┘
             │
    ┌─────────┴─────────┐
    │                   │
YES │                   │ NO
    │                   │
┌───▼───────────────┐  ┌───▼────────────────────────┐
│ ✅ CONSISTENCY OK │  │ 🚨 CRITICAL ALERT          │
│ Exact versions    │  │ INCONSISTENT versions!     │
│                   │  │ Proposes: sudo zypper ... │
└───────────────────┘  └────────┬───────────────────┘
                                │
                       ┌────────▼──────────────┐
                       │ [2/5] RPM Versions    │
                       │ [3/5] Source Repos    │
                       │ [4/5] Priorities      │
                       │ [5/5] Audio Services  │
                       └───────────────────────┘
        

Complete Script Code - Corrected and Robust Version

#!/bin/bash
# audio_check.sh - Preventive audio stack audit

echo "═══════════════════════════════════════════════════"
echo "  AUDIO STACK AUDIT - CONSISTENCY AND STABILITY"
echo "═══════════════════════════════════════════════════"

echo ""
echo "[1/5] ABI Consistency (CRITICAL TEST)"
echo "──────────────────────────────────────────────────"

# Extract versions
COMPILED=$(wireplumber --version 2>/dev/null | grep "Compiled" | grep -oE "[0-9]+\.[0-9]+\.[0-9]+" | head -1)
LINKED=$(wireplumber --version 2>/dev/null | grep "Linked" | grep -oE "[0-9]+\.[0-9]+\.[0-9]+" | head -1)

# Display results
echo "Compiled with: $COMPILED"
echo "Linked with:   $LINKED"

# Verify consistency
if [ -z "$COMPILED" ] || [ -z "$LINKED" ]; then
    echo "⚠️  Unable to determine versions"
elif [ "$COMPILED" = "$LINKED" ]; then
    echo "✅ ABI Consistency OK: Identical versions ($COMPILED)"
else
    echo "⚠️  CRITICAL ALERT: INCONSISTENT versions!"
    echo "   Compiled: $COMPILED"
    echo "   Linked:   $LINKED"
    echo "   → Action: sudo zypper in -f libwireplumber-0_5-0 --from home:pallaswept"
fi

echo ""
echo "[2/5] Main Package Versions"
echo "──────────────────────────────────────────────────"
rpm -q wireplumber libwireplumber-0_5-0 pipewire pipewire-aptx 2>/dev/null | sort

echo ""
echo "[3/5] Package Sources (Repositories)"
echo "──────────────────────────────────────────────────"
zypper se -si 'wireplumber*' 'pipewire*' 2>/dev/null | grep -E "^i|Repository" | head -20

echo ""
echo "[4/5] Repository Priorities"
echo "──────────────────────────────────────────────────"
zypper lr -P 2>/dev/null | grep -E "(Alias|Priority|pallaswept|oss|packman)"

echo ""
echo "[5/5] Audio Services Status"
echo "──────────────────────────────────────────────────"
systemctl --user status wireplumber --no-pager 2>/dev/null | head -7
wpctl status 2>/dev/null | head -10

echo ""
echo "═══════════════════════════════════════════════════"
echo "  AUDIT COMPLETE"
echo "═══════════════════════════════════════════════════"
        

Installation and Usage

# 1. Create file
nano audio_check.sh

# 2. Paste script above
# 3. Make script executable
chmod +x audio_check.sh

# 4. Execute script
./audio_check.sh

# 5. Save result (optional)
./audio_check.sh > audio_audit_$(date +%Y%m%d).txt
        

📎 Appendices: Reference Commands

Key Investigation Commands

Investigation Timeline

INVESTIGATION DASHBOARD
┌──────────────────────────────────────────────────────┐
│  STEP                          START-END   DURATION │
├──────────────────────────────────────────────────────┤
│  Phase 0: Context            09:00-09:05   5 min  📋 │
│  Step 1: Diagnosis           09:05-09:20  15 min  🔴 │
│  Step 2: Hardware            09:20-09:35  15 min  🔍 │
│  Step 3: Software            09:35-09:55  20 min  🧪 │
│  Step 4: Forensics           09:55-10:30  35 min  🔬 │
│  Step 5: Package Audit       10:30-11:00  30 min  📦 │
│  Step 6: Correction          11:00-11:10  10 min  🔧 │
│  Step 7: Validation          11:10-11:15   5 min  ✅ │
├──────────────────────────────────────────────────────┤
│  TOTAL                                   2h15    📈 │
└──────────────────────────────────────────────────────┘
        

Real Case Statistics

📊 INVESTIGATION STATISTICS
├── ⏱️ Total investigation time: 2h15 minutes
├── 💥 Documented crashes: 23 in 2 minutes (peak)
├── 🔄 Maximum restart attempts: 348 by systemd
├── 📦 Inconsistent packages: 2 out of 4 main
├── 🗄️ Involved repositories: 3 (official + pallaswept + packman)
├── ⌨️ Documented commands: 42 distinct
└── 🧪 Diagnostic steps: 7 progressive iterations
        

Zypper Priority Rule Reminder

📉 ZYPPER PRIORITY SCALE (lower is stronger)
┌─────────────────────────────────────────────────────────────────────┐
│ PRIORITY  BAR CHART        LEVEL      REPO TYPE          ACTION     │
├─────────────────────────────────────────────────────────────────────┤
│    1      [■■■■■■■■■■] 100%    🥇 MASTER   Full control     FORCE   │
│   99      [■■■■□□□□□□] 40%     🥈 STANDARD Official (OSS)   DEFAULT │
│  110      [■■□□□□□□□□] 20%     🥉 THIRD    Third-party      FALLBACK│
└─────────────────────────────────────────────────────────────────────┘
📌 GOLDEN RULE: The LOWEST number wins in conflicts
💡 ADVICE: To prioritize a repo → lower its priority!
        

🔗 Official Sources

📚 Recommended SafeITExperts Readings