Hi all, I recently updated my System on Feburary 28th, and ever since all of my audio has gone out. Today I updated my system and got YaST Sound, hoping that would fix the issue, however nothing happened there either. Reading through this forum it also had the suggestion of using Pavucontrol, however there are no sound devices there, likewise with plasma’s integrated sound options, too. The only thing that shows is labelled “dummy output”.
I’ve tried checking the help guide for audio issues, and I’ve only been able to get sound out of a specific device through my terminal. However, it feels like a dead end. I’m not the most literate when it comes to this and need help.
So I bit the bullet and did the big rebuild update for 20260303 tonight and now I see I should’ve held back, because I’m in the same boat. No onboard audio, no HDMI audio.
My results for pactl info are similar but not quite the same:
user@host ~ $ pactl info
Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 91
Tile Size: 65472
User Name: user
Host Name: host
Server Name: PulseAudio (on PipeWire 1.6.0)
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: @DEFAULT_SINK@
Default Source: @DEFAULT_SOURCE@
Cookie: f193:b769
Likewise for systemctl status --user wireplumber
user@host ~ $ systemctl status --user wireplumber
● wireplumber.service - Multimedia Service Session Manager
Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
Active: active (running) since Thu 2026-03-05 18:51:28 JST; 18min ago
Invocation: 1d99db5f4d4a4883a0e5fe61eac553a5
Main PID: 2585 (wireplumber)
Tasks: 3 (limit: 38345)
CPU: 28ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
└─2585 /usr/bin/wireplumber -p main
3月 05 18:51:28 host systemd[2412]: Started Multimedia Service Session Manager.
Considering this is an audio issue, could packages in packman-essentials be implicated? I wouldn’t think that would cause the audio devices to disappear entirely, though.
Just in case:
user@host ~ $ zypper pa -ir packman-essentials
Loading repository data...
Reading installed packages...kurohime
S | Repository | Name | Version | Arch
---+--------------------+---------------------------+-----------------------------------------+-------
i | packman-essentials | ffmpeg-8 | 8.0.1-1699.4.pm.67 | x86_64
v | packman-essentials | ffmpeg-8 | 8.0.1-1699.4.pm.67 | i586
v | packman-essentials | gdk-pixbuf-loader-libheif | 1.21.2-1699.4.pm.89 | x86_64
v | packman-essentials | gdk-pixbuf-loader-libheif | 1.21.2-1699.4.pm.89 | i586
i | packman-essentials | libavcodec61 | 7.1.3-1699.3.pm.12 | x86_64
v | packman-essentials | libavcodec61 | 7.1.3-1699.3.pm.12 | i586
i | packman-essentials | libavcodec62 | 8.0.1-1699.4.pm.67 | x86_64
v | packman-essentials | libavcodec62 | 8.0.1-1699.4.pm.67 | i586
v | packman-essentials | libavcodec62-32bit | 8.0.1-1699.4.pm.67 | x86_64
i | packman-essentials | libavdevice62 | 8.0.1-1699.4.pm.67 | x86_64
v | packman-essentials | libavdevice62 | 8.0.1-1699.4.pm.67 | i586
i | packman-essentials | libavfilter10 | 7.1.3-1699.3.pm.12 | x86_64
v | packman-essentials | libavfilter10 | 7.1.3-1699.3.pm.12 | i586
i | packman-essentials | libavfilter11 | 8.0.1-1699.4.pm.67 | x86_64
v | packman-essentials | libavfilter11 | 8.0.1-1699.4.pm.67 | i586
v | packman-essentials | libavfilter11-32bit | 8.0.1-1699.4.pm.67 | x86_64
i | packman-essentials | libavformat61 | 7.1.3-1699.3.pm.12 | x86_64
v | packman-essentials | libavformat61 | 7.1.3-1699.3.pm.12 | i586
i | packman-essentials | libavformat62 | 8.0.1-1699.4.pm.67 | x86_64
v | packman-essentials | libavformat62 | 8.0.1-1699.4.pm.67 | i586
v | packman-essentials | libavformat62-32bit | 8.0.1-1699.4.pm.67 | x86_64
i | packman-essentials | libavutil59 | 7.1.3-1699.3.pm.12 | x86_64
v | packman-essentials | libavutil59 | 7.1.3-1699.3.pm.12 | i586
i | packman-essentials | libavutil60 | 8.0.1-1699.4.pm.67 | x86_64
v | packman-essentials | libavutil60 | 8.0.1-1699.4.pm.67 | i586
v | packman-essentials | libavutil60-32bit | 8.0.1-1699.4.pm.67 | x86_64
v | packman-essentials | libfdk-aac2 | 2.0.2-1699.1.pm.145 | x86_64
v | packman-essentials | libfdk-aac2 | 2.0.2-1699.1.pm.145 | i586
v | packman-essentials | libfdk-aac2-32bit | 2.0.2-1699.1.pm.145 | x86_64
v | packman-essentials | libheif-aom | 1.21.2-1699.4.pm.89 | x86_64
v | packman-essentials | libheif-aom | 1.21.2-1699.4.pm.89 | i586
v | packman-essentials | libheif-dav1d | 1.21.2-1699.4.pm.89 | x86_64
v | packman-essentials | libheif-dav1d | 1.21.2-1699.4.pm.89 | i586
v | packman-essentials | libheif-ffmpeg | 1.21.2-1699.4.pm.89 | x86_64
v | packman-essentials | libheif-ffmpeg | 1.21.2-1699.4.pm.89 | i586
v | packman-essentials | libheif-jpeg | 1.21.2-1699.4.pm.89 | x86_64
v | packman-essentials | libheif-jpeg | 1.21.2-1699.4.pm.89 | i586
v | packman-essentials | libheif-openh264 | 1.21.2-1699.4.pm.89 | x86_64
v | packman-essentials | libheif-openh264 | 1.21.2-1699.4.pm.89 | i586
v | packman-essentials | libheif-openjpeg | 1.21.2-1699.4.pm.89 | x86_64
v | packman-essentials | libheif-openjpeg | 1.21.2-1699.4.pm.89 | i586
v | packman-essentials | libheif-rav1e | 1.21.2-1699.4.pm.89 | x86_64
v | packman-essentials | libheif-rav1e | 1.21.2-1699.4.pm.89 | i586
v | packman-essentials | libheif-svtenc | 1.21.2-1699.4.pm.89 | x86_64
v | packman-essentials | libheif1 | 1.21.2-1699.4.pm.89 | x86_64
v | packman-essentials | libheif1 | 1.21.2-1699.4.pm.89 | i586
i | packman-essentials | libpostproc58 | 7.1.3-1699.3.pm.12 | x86_64
v | packman-essentials | libpostproc58 | 7.1.3-1699.3.pm.12 | i586
v | packman-essentials | libquicktime0 | 1.2.4+git20180804.fff99cd-1699.11.pm.26 | x86_64
v | packman-essentials | libquicktime0 | 1.2.4+git20180804.fff99cd-1699.11.pm.26 | i586
i | packman-essentials | libswresample5 | 7.1.3-1699.3.pm.12 | x86_64
v | packman-essentials | libswresample5 | 7.1.3-1699.3.pm.12 | i586
i | packman-essentials | libswresample6 | 8.0.1-1699.4.pm.67 | x86_64
v | packman-essentials | libswresample6 | 8.0.1-1699.4.pm.67 | i586
v | packman-essentials | libswresample6-32bit | 8.0.1-1699.4.pm.67 | x86_64
i | packman-essentials | libswscale8 | 7.1.3-1699.3.pm.12 | x86_64
v | packman-essentials | libswscale8 | 7.1.3-1699.3.pm.12 | i586
i | packman-essentials | libswscale9 | 8.0.1-1699.4.pm.67 | x86_64
v | packman-essentials | libswscale9 | 8.0.1-1699.4.pm.67 | i586
v | packman-essentials | libswscale9-32bit | 8.0.1-1699.4.pm.67 | x86_64
v | packman-essentials | libvlc5 | 3.0.23-1699.8.pm.3 | x86_64
v | packman-essentials | libvlc5 | 3.0.23-1699.8.pm.3 | i586
v | packman-essentials | libvlccore9 | 3.0.23-1699.8.pm.3 | x86_64
v | packman-essentials | libvlccore9 | 3.0.23-1699.8.pm.3 | i586
i | packman-essentials | libx264-165 | 20250608.b35605ac-1699.1.pm.3 | x86_64
v | packman-essentials | libx264-165 | 20250608.b35605ac-1699.1.pm.3 | i586
i | packman-essentials | libx265-215 | 4.1-1699.4.pm.8 | x86_64
v | packman-essentials | libx265-215 | 4.1-1699.4.pm.8 | i586
v | packman-essentials | vlc | 3.0.23-1699.8.pm.3 | x86_64
v | packman-essentials | vlc | 3.0.23-1699.8.pm.3 | i586
v | packman-essentials | vlc-codec-gstreamer | 3.0.23-1699.8.pm.3 | x86_64
v | packman-essentials | vlc-codec-gstreamer | 3.0.23-1699.8.pm.3 | i586
i+ | packman-essentials | vlc-codecs | 3.0.23-1699.8.pm.3 | x86_64
v | packman-essentials | vlc-codecs | 3.0.23-1699.8.pm.3 | i586
v | packman-essentials | vlc-lang | 3.0.23-1699.8.pm.3 | noarch
v | packman-essentials | vlc-lang | 3.0.23-1699.8.pm.1 | noarch
v | packman-essentials | vlc-noX | 3.0.23-1699.8.pm.3 | x86_64
v | packman-essentials | vlc-noX | 3.0.23-1699.8.pm.3 | i586
v | packman-essentials | vlc-qt | 3.0.23-1699.8.pm.3 | x86_64
v | packman-essentials | vlc-qt | 3.0.23-1699.8.pm.3 | i586
Nevermind, after reading the comment in the bugzilla report, mentioned by hui, I decided to try shutting down my computer entirely and letting it sit for a bit.
Sure enough, after a restart it is back to normal again. Not the most satisfying resolution because I don’t feel like I learned anything about what was going on, but at least it works now.
@Teahcherries, have you tried, ahem, turning it off and on again?
You didn’t have the same issue as the OP…wireplumber is operating with the main profile which includes audio. I’m not surprised that restarting the system helped following the kernel update.
FWIW in the last few days I got no audio after login every now and then.
If that happens systemctl --user restart pipewirefixes the issue.
I didn’t investigate further so I don’t know if it might be the same problem reported here.
Just updated to 20260304 and noticed an update to pipewire with 3 patches from upstream, let’s see how it goes.
This looks like it might be the same “no audio” problem you were helping me with following my conversion from leap 15.6 to tumbleweed a couple of days ago. I reverted back to leap 15.6, if you remember.
If there is a viable solution coming from this thread, I will try the leap 15.6 → tumbleweed conversion again.
Based on what you shared (not sure why the multiple command iterations posted), WirePlumber is installed and configured correctly. Any problems with “no onboard or HDMI audio” are likely kernel/module related, not service configuration related.