Comment # 5 on bug 1178310 from Pablo Sanchez

Hi Takashi,

I did not know that pipewire was not needed.  :]

I've uninstalled the bits and I did two reboot tests:  audio works.  \o/

Thank you so much!

I detailed below what I've done with the hopes that it may help others.

Given pipewire is version 0.X, I'm going to assume it'll become more stable.

I'm happy to do more testing to try to get to the root-cause or just call it
done (RESOLVED).  Please let me know.

::: Strategy :::

Generally I try minimally invasive tactics first.

Below is the order in which I tried to resolve the issue.

::: 1 - User-level service disable :::

Stop and disable the pipewire.socket/.service for my user.  On reboot, I saw
the stack trace in /var/log/messages and no sound.

The service was still started for my user.

::: 2 - Globally disable the service :::

I globally disabled the service, rebooted and still no sound. 
/var/log/messages showed the stack trace.  I confirmed that the service was
disabled:

# user-level status check
systemctl --user status pipewire.socket
systemctl --user status pipewire.service

# globally disable the service
systemctl disable --global pipewire

::: 3 - Uninstall pipewire :::

I removed pipewire.  I probably should set up zypper to not install it.

No more stack trace and after two reboot tests, I confirmed audio is working.

# Drop the hammer on pipewire
rpm --erase pipewire pipewire-modules pipewire-spa-plugins-0_2
plasma5-session-wayland