Connection to the Sound Service Lost

Error I was mentioning earlier, well the one below was when I tried the reenable command, but they all have the same rest of the body.

Failed to reenable unit: Unit /etc/xdg/systemd/user/pipewire-pulse.socket is masked

Results:

jerm@jermPC ~ [1]> journalctl --user -b | grep pipewire
Oct 26 22:18:06 jermPC sudo[4322]:     jerm : TTY=pts/3 ; PWD=/home/jerm ; USER=root ; COMMAND=/usr/bin/zypper in --force pipewire-pulseaudio
Oct 26 22:18:34 jermPC sudo[6473]:     jerm : TTY=pts/3 ; PWD=/home/jerm ; USER=root ; COMMAND=/usr/bin/zypper in --force pipewire-pulse
Oct 26 22:19:33 jermPC sudo[6629]:     jerm : TTY=pts/3 ; PWD=/home/jerm ; USER=root ; COMMAND=/usr/bin/zypper in --force pipewire-pulseaudio
Oct 26 22:21:48 jermPC sudo[9370]:     jerm : TTY=pts/3 ; PWD=/home/jerm ; USER=root ; COMMAND=/usr/bin/zypper in --force pipewire
Oct 26 22:22:21 jermPC sudo[11921]:     jerm : TTY=pts/3 ; PWD=/home/jerm ; USER=root ; COMMAND=/usr/bin/zypper in kpipewire
Oct 26 22:22:42 jermPC sudo[12010]:     jerm : TTY=pts/3 ; PWD=/home/jerm ; USER=root ; COMMAND=/usr/bin/zypper in kpipewire6
Oct 26 22:27:24 jermPC sudo[17902]:     jerm : TTY=pts/3 ; PWD=/home/jerm ; USER=root ; COMMAND=/usr/bin/zypper in --force pipewire
Oct 26 23:05:02 jermPC sudo[26868]:     jerm : TTY=pts/3 ; PWD=/home/jerm ; USER=root ; COMMAND=/usr/bin/zypper in -f pipewire
Oct 26 23:06:39 jermPC sudo[29035]:     jerm : TTY=pts/3 ; PWD=/home/jerm ; USER=root ; COMMAND=/usr/bin/zypper in -f pipewire
Oct 26 23:09:44 jermPC sudo[31905]:     jerm : TTY=pts/3 ; PWD=/home/jerm ; USER=root ; COMMAND=/usr/bin/zypper in -fu pipewire-pulseaudio

Show the results of
ls -l /etc/xdg/systemd/user/*

lrwxrwxrwx 1 root root  41 Aug 26 15:07 /etc/xdg/systemd/user/dbus.service -> /usr/lib/systemd/user/dbus-broker.service
lrwxrwxrwx 1 root root   9 Oct 24 03:05 /etc/xdg/systemd/user/pipewire-pulse.service -> /dev/null
lrwxrwxrwx 1 root root   9 Oct 24 03:05 /etc/xdg/systemd/user/pipewire-pulse.socket -> /dev/null
lrwxrwxrwx 1 root root  41 Aug 16 23:26 /etc/xdg/systemd/user/pipewire-session-manager.service -> /usr/lib/systemd/user/wireplumber.service

/etc/xdg/systemd/user/basic.target.wants:
total 4
lrwxrwxrwx 1 root root 52 Aug 16 23:29 systemd-tmpfiles-setup.service -> /usr/lib/systemd/user/systemd-tmpfiles-setup.service

/etc/xdg/systemd/user/graphical-session-pre.target.wants:
total 4
lrwxrwxrwx 1 root root 43 Aug 16 23:23 xdg-user-dirs.service -> /usr/lib/systemd/user/xdg-user-dirs.service

/etc/xdg/systemd/user/pipewire.service.wants:
total 4
lrwxrwxrwx 1 root root 41 Aug 16 23:26 wireplumber.service -> /usr/lib/systemd/user/wireplumber.service

/etc/xdg/systemd/user/sockets.target.upholds:
total 4
lrwxrwxrwx 1 root root 54 Aug 16 23:29 drkonqi-coredump-launcher.socket -> /usr/lib/systemd/user/drkonqi-coredump-launcher.socket

/etc/xdg/systemd/user/sockets.target.wants:
total 12
lrwxrwxrwx 1 root root 54 Aug 16 23:29 drkonqi-coredump-launcher.socket -> /usr/lib/systemd/user/drkonqi-coredump-launcher.socket
lrwxrwxrwx 1 root root 43 Aug 16 23:26 pipewire-pulse.socket -> /usr/lib/systemd/user/pipewire-pulse.socket
lrwxrwxrwx 1 root root 37 Aug 16 23:26 pipewire.socket -> /usr/lib/systemd/user/pipewire.socket

/etc/xdg/systemd/user/timers.target.wants:
total 4
lrwxrwxrwx 1 root root 50 Aug 16 23:29 systemd-tmpfiles-clean.timer -> /usr/lib/systemd/user/systemd-tmpfiles-clean.timer

Ok, I would remove these two symlinks first.Then try re-enabling pipewire-pulse.{service,socket} again. (I’ve never encountered this issue before.)

Similar post here.

THANK YOU DEANO!!!
I was going crazy trying to figure this out.
You are a linux legend!
I guess it is an uncommon problem then.

So, I guess the symlink to devnull was the reason a broken pipe which kept pipewire from running since it would error out?

Well done. Uncharted territory for me.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.