After the forced reinstall, is wireplumber still exhibiting errors?
No sound, I’ll do reboot.
I think forced refresh of “pipewire-spa-plugins” should be “pipewire-spa-plugins-0_2”.
Did reboot and stil no sound.
pavucontrol shows no output devices like it used to. It showed line-out and headphones as outputs.
Show the wireplumber.service status again please.
Also wpctl status and pactl list cards
I am going to end this and revert back to leap 16.5. I could do all I needed to do using leap 16.5. I was only upgrading as it seemed like the thing to do.
Thanks for all your efforts. I’ll pprobably do fresh install at some point in the future.
tom kosvic
You mean Leap 15.6 of course. All good. I suspect something stale getting left during the upgrade. A clean install is probably a sensible approach. Just back up your important data first.
I’d like to keep this thread open and continue it for solution to no sound… I went back to tumbleweed after update from leap 15.6. Moving to nvidia proprietrary drivers from noveau seemed to solve the kwin problems I was having with files and dialogs not closing.
I still have no sound and no diagnostic path forward.
Pipewire is not running.
(base) tom@mydesktop: ~ $ systemctl --user status wireplumber
× wireplumber.service - Multimedia Service Session Manager
Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Tue 2026-03-31 14:37:40 CDT; 21min ago
Duration: 62ms
Invocation: 4600835f0f534338858d04bb5db66ce3
Process: 7488 ExecStart=/usr/bin/wireplumber -p $WIREPLUMBER_PROFILE (code=exited, status=78)
Main PID: 7488 (code=exited, status=78)
CPU: 52ms
Mar 31 14:37:40 mydesktop systemd[2039]: wireplumber.service: Scheduled restart job, restart counter is at 5.
Mar 31 14:37:40 mydesktop systemd[2039]: wireplumber.service: Start request repeated too quickly.
Mar 31 14:37:40 mydesktop systemd[2039]: wireplumber.service: Failed with result 'exit-code'.
Mar 31 14:37:40 mydesktop systemd[2039]: Failed to start Multimedia Service Session Manager.
(base) tom@mydesktop: ~ $
After a start of wireplumber I get same ststus message.
Journalctl shows missing "no component provides ‘monitor.alsa’, wanted by 'hardware.audio [virtual]:.
(base) tom@mydesktop: ~ $ journalctl -b --user-unit=wireplumber
Mar 31 14:35:16 mydesktop systemd[2039]: Started Multimedia Service Session Manager.
Mar 31 14:35:17 mydesktop wireplumber[2280]: failed to load components: no component provides 'monitor.alsa', wanted by 'hardware.audio [virtual]'
Mar 31 14:35:17 mydesktop systemd[2039]: wireplumber.service: Main process exited, code=exited, status=78/CONFIG
Mar 31 14:35:17 mydesktop systemd[2039]: wireplumber.service: Failed with result 'exit-code'.
Mar 31 14:35:17 mydesktop systemd[2039]: wireplumber.service: Scheduled restart job, restart counter is at 1.
Mar 31 14:35:17 mydesktop systemd[2039]: Started Multimedia Service Session Manager.
Mar 31 14:35:17 mydesktop wireplumber[2334]: failed to load components: no component provides 'monitor.alsa', wanted by 'hardware.audio [virtual]'
Mar 31 14:35:17 mydesktop systemd[2039]: wireplumber.service: Main process exited, code=exited, status=78/CONFIG
Mar 31 14:35:17 mydesktop systemd[2039]: wireplumber.service: Failed with result 'exit-code'.
Mar 31 14:35:17 mydesktop systemd[2039]: wireplumber.service: Scheduled restart job, restart counter is at 2.
Mar 31 14:35:17 mydesktop systemd[2039]: Started Multimedia Service Session Manager.
Mar 31 14:35:17 mydesktop wireplumber[2338]: failed to load components: no component provides 'monitor.alsa', wanted by 'hardware.audio [virtual]'
Mar 31 14:35:17 mydesktop systemd[2039]: wireplumber.service: Main process exited, code=exited, status=78/CONFIG
Mar 31 14:35:17 mydesktop systemd[2039]: wireplumber.service: Failed with result 'exit-code'.
Mar 31 14:35:18 mydesktop systemd[2039]: wireplumber.service: Scheduled restart job, restart counter is at 3.
Mar 31 14:35:18 mydesktop systemd[2039]: Started Multimedia Service Session Manager.
Mar 31 14:35:18 mydesktop wireplumber[2342]: failed to load components: no component provides 'monitor.alsa', wanted by 'hardware.audio [virtual]'
Mar 31 14:35:18 mydesktop systemd[2039]: wireplumber.service: Main process exited, code=exited, status=78/CONFIG
Mar 31 14:35:18 mydesktop systemd[2039]: wireplumber.service: Failed with result 'exit-code'.
Mar 31 14:35:18 mydesktop systemd[2039]: wireplumber.service: Scheduled restart job, restart counter is at 4.
Mar 31 14:35:18 mydesktop systemd[2039]: Started Multimedia Service Session Manager.
Mar 31 14:35:18 mydesktop wireplumber[2355]: failed to load components: no component provides 'monitor.alsa', wanted by 'hardware.audio [virtual]'
Mar 31 14:35:18 mydesktop systemd[2039]: wireplumber.service: Main process exited, code=exited, status=78/CONFIG
Mar 31 14:35:18 mydesktop systemd[2039]: wireplumber.service: Failed with result 'exit-code'.
Mar 31 14:35:18 mydesktop systemd[2039]: wireplumber.service: Scheduled restart job, restart counter is at 5.
Other research in alsa docs says “monitor.alsa” should be in “alsa-monitor.conf” file but there is no file named that on my machine.
Need an audio expert I think. Any help appreciated.
tom kosvic
Further note: Bear in mind, while running leap 15.6, the sound worked fine including bluetooth. The system was updated through opensuse-migration-tool. So the answer might be in what differences are there in audio files between leap15.6 and tumbleweed.
tom kosvic
Per @deano_ferrari request
(base) tom@mydesktop: ~ $ wpctl status
PipeWire 'pipewire-0' [1.6.2, tom@mydesktop, cookie:3618806377]
└─ Clients:
32. marco [1.6.2, tom@mydesktop, pid:2998]
33. pipewire [1.6.2, tom@mydesktop, pid:2281]
35. mate-settings-daemon [1.6.2, tom@mydesktop, pid:2963]
36. xdg-desktop-portal [1.6.2, tom@mydesktop, pid:2926]
37. MATE Volume Control StatusIcon [1.6.2, tom@mydesktop, pid:3188]
38. PulseAudio systray [1.6.2, tom@mydesktop, pid:3158]
39. Blueman [1.6.2, tom@mydesktop, pid:3141]
40. Caja [1.6.2, tom@mydesktop, pid:3048]
41. Panel [1.6.2, tom@mydesktop, pid:3011]
42. wnck-applet [1.6.2, tom@mydesktop, pid:3096]
43. Thunderbird [1.6.2, tom@mydesktop, pid:6599]
44. Thunderbird [1.6.2, tom@mydesktop, pid:6599]
45. Thunderbird [1.6.2, tom@mydesktop, pid:6599]
46. Vivaldi input [1.6.2, tom@mydesktop, pid:7825]
47. wpctl [1.6.2, tom@mydesktop, pid:8406]
Audio
├─ Devices:
│
├─ Sinks:
│ 34. Dummy Output [vol: 1.00]
│
├─ Sources:
│
├─ Filters:
│
└─ Streams:
Video
├─ Devices:
│
├─ Sinks:
│
├─ Sources:
│
├─ Filters:
│
└─ Streams:
Settings
└─ Default Configured Devices:
(base) tom@mydesktop: ~ $ pactl list cards
(base) tom@mydesktop: ~ $
No ALSA devices are being exposed into it at all.
Check
pw-cli ls Device
aplay -l
and verify SPA ALSA plugin is present…
ls /usr/lib64/spa-0.2/alsa
@deano_ferrari , I loaded pulseaudio through software manager and sound started working through wired headphones. I think that process removes pipewire.
No bluetooth yet.
If you wish, I will go back to pipewire for diagnosis but I would probably like to stay where sound is working and work on the bluetooth. I don’t do any heavy weight sound stuff other than listening.
If you want me to go back for diagnosis, I will, let me know. I feel bad that this is 2nd time I bailed out using alternate solutions.
tom kosvic
Just use what works for you. 
I got bluetooth on pulseaudio running so i will stick with this for now. It started after innumerable stops/starts of bluetoothctl using systemctl and rfkill. No sure what sequence worked but it started.
No files were needed or added in moving to tumbleweed from leap 15.6 to keep bluetooth working.