Ever since the update a week ago and all the Packman/mini-libs stuff, now resolved here, sound has been broken. I see a wireplumber core dump, end points for Pipewire (pulseaudio and alsa plugins too) do not get created. There is a spa.bluez fail to start (never used that but some say it might be related) and I don’t know how to proceed further with troubleshooting.
I have more errors, but the forum won’t let me post or paste them in.
Welcome to the openSUSE Forums!
Snapshot 20260324 included several pipewire and alsa related packages, to rule out the obvious please zypper dup again and see if something changes.
Then posting zypper lr -d and zypper se -si alsa pipewire wireplumber might help us understand what is going on.
Also you can check if pw-top (run as your user) shows something unusual.
I’m zypper dup’d to the minute here and have been through all of this.
zypper se -si alsa pipewire wireplumber
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+--------------------------------+---------+-------------------+--------+----------------------
i+ | alsa | package | 1.2.15.3-1.2 | x86_64 | Main Repository (OSS)
i+ | alsa-devel | package | 1.2.15.3-1.2 | x86_64 | Main Repository (OSS)
i+ | alsa-oss | package | 1.1.8-5.9 | x86_64 | Main Repository (OSS)
i+ | alsa-oss-32bit | package | 1.1.8-5.9 | x86_64 | Main Repository (OSS)
i+ | alsa-plugins | package | 1.2.12-1.11 | x86_64 | Main Repository (OSS)
i+ | alsa-plugins-speex | package | 1.2.12-1.11 | x86_64 | Main Repository (OSS)
i+ | alsa-plugins-speexrate | package | 1.2.12-1.11 | x86_64 | Main Repository (OSS)
i+ | alsa-plugins-upmix | package | 1.2.12-1.11 | x86_64 | Main Repository (OSS)
i+ | alsa-ucm-conf | package | 1.2.15.3-1.2 | noarch | Main Repository (OSS)
i+ | alsa-utils | package | 1.2.15.2-1.2 | x86_64 | Main Repository (OSS)
i+ | gstreamer-plugin-pipewire | package | 1.6.2-1.2 | x86_64 | Main Repository (OSS)
i+ | kpipewire6-imports | package | 6.6.3-1.1 | x86_64 | Main Repository (OSS)
i+ | libKPipeWire6 | package | 6.6.3-1.1 | x86_64 | Main Repository (OSS)
i+ | libKPipeWireDmaBuf6 | package | 6.6.3-1.1 | x86_64 | Main Repository (OSS)
i+ | libKPipeWireRecord6 | package | 6.6.3-1.1 | x86_64 | Main Repository (OSS)
i+ | libpipewire-0_3-0 | package | 1.6.2-1.2 | x86_64 | Main Repository (OSS)
i+ | libpipewire-0_3-0-32bit | package | 1.6.2-1.2 | x86_64 | Main Repository (OSS)
i+ | libwireplumber-0_5-0 | package | 0.5.13-3.1 | x86_64 | Main Repository (OSS)
i+ | pipewire | package | 1.6.2-1.2 | x86_64 | Main Repository (OSS)
i+ | pipewire-alsa | package | 1.6.2-1.2 | x86_64 | Main Repository (OSS)
i+ | pipewire-alsa-32bit | package | 1.6.2-1.2 | x86_64 | Main Repository (OSS)
i+ | pipewire-aptx | package | 1.6.2-1699.1.pm.1 | x86_64 | Packman Repository
i+ | pipewire-aptx | package | 1.6.2-1699.1.pm.1 | x86_64 | Packman
i+ | pipewire-config-rates | package | 1.6.2-1.2 | x86_64 | Main Repository (OSS)
i+ | pipewire-config-upmix | package | 1.6.2-1.2 | x86_64 | Main Repository (OSS)
i+ | pipewire-devel | package | 1.6.2-1.2 | x86_64 | Main Repository (OSS)
i+ | pipewire-jack | package | 1.6.2-1.2 | x86_64 | Main Repository (OSS)
i+ | pipewire-libjack-0_3 | package | 1.6.2-1.2 | x86_64 | Main Repository (OSS)
i+ | pipewire-libjack-0_3-32bit | package | 1.6.2-1.2 | x86_64 | Main Repository (OSS)
i+ | pipewire-libjack-0_3-devel | package | 1.6.2-1.2 | x86_64 | Main Repository (OSS)
i+ | pipewire-module-xrdp | package | 0~git19-1.8 | x86_64 | Main Repository (OSS)
i+ | pipewire-modules-0_3 | package | 1.6.2-1.2 | x86_64 | Main Repository (OSS)
i+ | pipewire-modules-0_3-32bit | package | 1.6.2-1.2 | x86_64 | Main Repository (OSS)
i+ | pipewire-pulseaudio | package | 1.6.2-1.2 | x86_64 | Main Repository (OSS)
i+ | pipewire-spa-plugins-0_2 | package | 1.6.2-1.2 | x86_64 | Main Repository (OSS)
i+ | pipewire-spa-plugins-0_2-32bit | package | 1.6.2-1.2 | x86_64 | Main Repository (OSS)
i+ | pipewire-spa-tools | package | 1.6.2-1.2 | x86_64 | Main Repository (OSS)
i+ | pipewire-tools | package | 1.6.2-1.2 | x86_64 | Main Repository (OSS)
i+ | wireplumber | package | 0.5.13-3.1 | x86_64 | Main Repository (OSS)
i+ | wireplumber-bash-completion | package | 0.5.13-3.1 | x86_64 | Main Repository (OSS)
Mod edit: Preformatted text for readability.
I have a few repos here, the usual main and OSS, Packman, some amateur radio repos and a few others. Audio packages are all from Main except for the codecs are from PackMan.
And the forum won’t let me post the errors from the wireplumber command. Complains about 2 links, but it’s a simple text paste?
Let’s try the WP errors this way if it’ll take it (and all of this worked for many years before the update)
:
When posting code or output, please try to post as preformatted text (refer to the </> button in the forum editor)…
```type or paste code here
```and it will appear like this
type or paste code here
More info
You have an extensive list of packages installed, required by a Digital Audio Workstation or? On the specifics, I wonder if the pipewire-aptx package from Packman might be related or not: is it possible to uninstall and test?
Please don’t tell stories, provide the computer output; to help you we need to see the details since, you know, “the devil is in the details…”
If you don’t want to show unrelated details that’s fine, redact the output clearly marking missing text (*** or or similar) but keep in mind that we cannot browse over your shoulder.
You appear to have enabled a duplicate of the Packman repo; that might be unrelated, but we cannot advise about what we cannot see.
Not sure what the best way to past in that repo list after the Discourse post? How would I do a simple copy and paste from the terminal then?
Depending on the terminal emulator you use…
Usually just selecting the text on the terminal and “middle clicking” here pastes the highlighted text.
Or selecting the text and CTRL+SHIFT+C copies text to the clipboard, then CTRL+V here pastes…
I was just copy and pasting and I’ll do that then.
I uninstalled the aptX plugin and rebooted with no change. Installed it again. I do have a set of Bluetooth earbuds I used a while ago for hands free listening in the office. I used this for amateur radio software defined radio work as well as development and many of the digital protocol applications will use either Pipewire direct , or emulated PulseAudio or the PortAudio or the APSA API depending on the particular digital decoding application. Some use Pipewire natively and some are for transmitting also as well as wide bandwidth receive. I do have lots of repos and some will be obvious while others are esoteric and needed for the rest of the work I do. (The two Packman repos are for redundancy and no issues were ever there from this, st least so far.)
I can’t paste in the zypper lr -d terminal output for you. The forum complains about links.
OK, you just joined the Forums and you have a temporary embargo on links (just making sure you are not a spam bot 
) but pasting between pre-formatted text tags should bypass that.
OK, I understand SDR and your other needs, no problem. But apparently there is something wrong with bluez (Bluetooth stack) and with udev, so some audio/video peripheral connected to the system? Or a bluetooth adapter connected via USB?
I would disconnect every (unusual?) peripheral, disable bluetooth and check plain music playing through built-in speakers (if any) to see if the basic pipewire+wireplumber is sound (pun intended).
You may check pw-top and install Helvum (zypper in helvum) to see graphically what wireplumber is doing.
You may check systemctl --user status pipewire pipewire-pulse wireplumber to check the current status of related services and systemctl --user restart pipewire pipewire-pulse wireplumber to restart them after a crash or a change in the system.
And that’s it for today (too late at night here for productive troubleshooting).
Unless fellow geekos from New Zealand chime in…
Understood on being new to the forums. I have been using Bugzilla for years and TW for a very long time, never had any real head scratchers with it so I never had to reach out for some help 
That says a lot about TW.
I don’t have any Bluetooth devices plugged in. No BT dongles (I used a BT dongle with the BT earpods when I used them) but none of that is plugged in. Realtek motherboard audio and the audio on the Radeon card, and the audio cards in the monitors I have (those are HDMI and disabled, don’t need them) so nothing odd at all. I think something about the (unneeded and unused right now) bluez stack is core dumping wireplumber, I heard some rumblings about that. I’ll try to remove that tomorrow and see if I make any headway.
Thanks again
As a reference here is what is installed here:
LT-B:~ # zypper se -si blue
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+--------------------------------+---------+--------------+--------+-----------
i+ | bluez | package | 5.79-3.5 | x86_64 | repo-oss
i | bluez-auto-enable-devices | package | 5.79-3.5 | noarch | repo-oss
i | bluez-cups | package | 5.79-3.5 | x86_64 | repo-oss
i+ | bluez-obexd | package | 5.79-3.5 | x86_64 | repo-oss
i | gnome-bluetooth | package | 47.1-2.2 | x86_64 | repo-oss
i+ | kernel-firmware-bluetooth | package | 20260313-1.1 | noarch | repo-oss
i | libbluetooth3 | package | 5.79-3.5 | x86_64 | repo-oss
i | libgnome-bluetooth-3_0-13 | package | 47.1-2.2 | x86_64 | repo-oss
i | libgnome-bluetooth-ui-3_0-13 | package | 47.1-2.2 | x86_64 | repo-oss
i | NetworkManager-bluetooth | package | 1.54.3-3.2 | x86_64 | repo-oss
i | typelib-1_0-GnomeBluetooth-3_0 | package | 47.1-2.2 | x86_64 | repo-oss
LT-B:~ #
and sound is working beautifully and even BT is in order apparently, even if something definitely changed with pipewire (still trying to make sense of it…)
Just seeing that a new version of wireplumber is in snapshot 20260326 Tumbleweed/diff/20260326 with explicit reference to
Enhanced Bluetooth loopback nodes …
so maybe wait for the next snapshot and try again?
Similar but a few more packages…
zypper se -si blue
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+--------------------------------+---------+------------------+--------+----------------------
i | bluedevil6 | package | 6.6.3-1.1 | x86_64 | Main Repository (OSS)
i+ | bluez | package | 5.79-3.5 | x86_64 | Main Repository (OSS)
i+ | bluez-auto-enable-devices | package | 5.79-3.5 | noarch | Main Repository (OSS)
i | bluez-cups | package | 5.79-3.5 | x86_64 | Main Repository (OSS)
i | bluez-obexd | package | 5.79-3.5 | x86_64 | Main Repository (OSS)
i+ | bluez-qt-devel | package | 5.116.0-1.4 | x86_64 | Main Repository (OSS)
i+ | bluez-qt-imports | package | 5.116.0-1.4 | x86_64 | Main Repository (OSS)
i+ | bluez-qt-udev | package | 5.116.0-1.4 | x86_64 | Main Repository (OSS)
i | gnome-bluetooth | package | 47.1-2.2 | x86_64 | Main Repository (OSS)
i+ | kernel-firmware-bluetooth | package | 20260313-1.1 | noarch | Main Repository (OSS)
i+ | kf6-bluez-qt | package | 6.24.0-1.1 | x86_64 | Main Repository (OSS)
i+ | kf6-bluez-qt-imports | package | 6.24.0-1.1 | x86_64 | Main Repository (OSS)
i+ | libbluetooth3 | package | 5.79-3.5 | x86_64 | Main Repository (OSS)
i+ | libbluetooth3-32bit | package | 5.79-3.5 | x86_64 | Main Repository (OSS)
i | libgnome-bluetooth-3_0-13 | package | 47.1-2.2 | x86_64 | Main Repository (OSS)
i | libgnome-bluetooth-ui-3_0-13 | package | 47.1-2.2 | x86_64 | Main Repository (OSS)
i+ | libKF5BluezQt6 | package | 5.116.0-1.4 | x86_64 | Main Repository (OSS)
i+ | libKF6BluezQt6 | package | 6.24.0-1.1 | x86_64 | Main Repository (OSS)
i | libQt5Bluetooth5 | package | 5.15.18+kde1-1.2 | x86_64 | Main Repository (OSS)
i | libQt5Bluetooth5-imports | package | 5.15.18+kde1-1.2 | x86_64 | Main Repository (OSS)
i+ | libQt6Bluetooth6 | package | 6.10.2-1.2 | x86_64 | Main Repository (OSS)
i | NetworkManager-bluetooth | package | 1.54.3-3.2 | x86_64 | Main Repository (OSS)
i | typelib-1_0-GnomeBluetooth-3_0 | package | 47.1-2.2 | x86_64 | Main Repository (OSS)
Edit:
Code-Tags by Sauerland, please see:
Code-Tags
I’ll keep an eye out for the new snapshot. Maybe that will resolve this.
Thanks again
I did see the new snapshot and the wireplumber upgrades. I installed that and rebooted.
But it did not fix the problem. Everything still fails as before including the wireplumber core dumps and the BlueZ reporting not available (not sure if that is even involved, but likely it is broken too).
What does systemctl --user -v restart wireplumber show?