Bug 1212034

Summary:	No sound after upgrade to Leap 15.5
Product:	[openSUSE] openSUSE Distribution	Reporter:	Alexander Kruppa <akruppa>
Component:	Upgrade Problems	Assignee:	Antonio Larrosa <alarrosa>
Status:	NEW ---	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	alarrosa, nwr10cst-oslnx
Version:	Leap 15.5
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE Leap 15.5
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Alexander Kruppa 2023-06-05 16:12:30 UTC

This is a copy-paste of my comment on [https://forums.opensuse.org/t/solved-no-sound-after-upgrade-to-leap-15-5/166693/1] where dcurtisfra replied that I should open a bug about it. If you need any further information about by system, I will happily provide it.

Here’s a problem that kept me busy all day. After upgrading to Leap 15.5, no audio would play by any means, not even in YaST->Sound->Play Test Sound.

I know very little about the Linux sound system, so I can’t give detailed information on the problem. However, it seems to have been that there were two symlinks on my system:

/etc/xdg/systemd/user/pipewire-pulse.service → /dev/null
/etc/xdg/systemd/user/pipewire-pulse.socket → /dev/null

and these prevented the pipewire-pulse service from starting:

alex@lily:~> systemctl --user --now enable pipewire pipewire-pulse
Failed to enable unit: Unit file /etc/xdg/systemd/user/pipewire-pulse.service is masked.

Deleting the two symlinks as root, then running as a normal user

systemctl --user unmask pipewire-pulse
systemctl --user start pipewire-pulse

seems to have fixed it.

Comment 1 Neil Rickert 2023-06-05 17:26:42 UTC

No problems here.

I did a clean install of 15.5, instead of an upgrade.  And perhaps that's the difference.

Comment 2 Alexander Kruppa 2023-06-05 19:06:06 UTC

I just checked the backup I made before the upgrade, and the two symlinks were not present in the 15.4 installation.

Comment 3 Antonio Larrosa 2023-06-27 12:07:23 UTC

Can you check if you have installed the wireplumber-audio package? If that's installed then maybe you want to be sure the following user services are enabled:

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

Thanks Neil for confirming a clean installation is ok. Note that on a clean, new installation, Leap uses pulseaudio while Alexander mentions he has the pipewire-pulse service in his system, so that means he installed pipewire-pulseaudio (or wireplumber-audio) manually, replacing pulseaudio.

Comment 4 Alexander Kruppa 2023-07-11 15:21:52 UTC

I have since upgraded from 15.5 to Tumbleweed, so unfortunately I can't check the 15.5 installation any more.

For the record, yesterday I updated the Tumbleweed distro by doing zypper dup, and the two links to /dev/null re-appeared after the update completed, so sound was gone again until I removed them.

I've now run
systemctl --user enable wireplumber pipewire.socket pipewire-pulse.socket
which output
Created symlink /home/alex/.config/systemd/user/pipewire-session-manager.service → /usr/lib/systemd/user/wireplumber.service.
Created symlink /home/alex/.config/systemd/user/pipewire.service.wants/wireplumber.service → /usr/lib/systemd/user/wireplumber.service.

Let's see whether the sound breaks again the next time I do a Tumbleweed update with zypper dup. I'll update then.

Comment 5 Alexander Kruppa 2023-10-10 16:53:59 UTC

I just did a "zypper dup" distro upgrade, and sure enough, the two links re-appeared:

lrwxrwxrwx 1 root root 9 Okt 10 17:59 /etc/xdg/systemd/user/pipewire-pulse.service -> /dev/null
lrwxrwxrwx 1 root root 9 Okt 10 17:59 /etc/xdg/systemd/user/pipewire-pulse.socket -> /dev/null

I did the upgrade today, btw, so the file timestamps are not the installation time.

The wireplumber-audio package is installed:

> rpm -q wireplumber-audio
wireplumber-audio-0.4.14-2.3.noarch

Comment 6 Antonio Larrosa 2023-10-13 10:00:22 UTC

That's really strange. Can you run the following command and copy here the output?

systemctl status --user pipewire-pulse.service pipewire-pulse.socket

Also, it would be interesting if after that, you run these commands as root:

rm /etc/xdg/systemd/user/pipewire-pulse.service /etc/xdg/systemd/user/pipewire-pulse.socket
/usr/bin/systemctl --global preset pipewire-pulse.service
/usr/bin/systemctl --global preset pipewire-pulse.socket

And check if the symlinks are recreated by the preset configuration.

Finally, just to try to get some hint of what's happening, can you check if any pipewire services/socket are masked with these commands? 

systemctl list-unit-files --state=masked
systemctl list-unit-files --user --state=masked