Getting the following error when I try to update today (Tumbleweed, pretty much only standard repos enabled).
Problem: the to be installed pipewire-alsa-0.3.70-1.1.x86_64 conflicts with 'alsa-plugins-pulse' provided by the installed alsa-plugins-pulse-1.2.7.1-4.4.x86_64
Solution 1: deinstallation of alsa-plugins-pulse-1.2.7.1-4.4.x86_64
Solution 2: deinstallation of pipewire-alsa-0.3.69-2.1.x86_64
Solution 3: keep obsolete pipewire-alsa-0.3.69-2.1.x86_64
On a single core Pentium 32bit TW I just started to upgrade minutes ago, with none of pipewire or wireplumber installed, no similar conflict appeared.
How long ago was your last upgrade? IMO it depends whether yours is currently more dependent on pipewire or on pulseaudio. The following is from a TW upgrade on Intel Haswell to 20230511 where pulseaudio is not in use, or even installed:
# pinxi -Aaz --vs --zl --hostname
pinxi 3.3.27-01 (2023-05-07)
Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 00:03.0
chip-ID: 8086:0c0c class-ID: 0403
Device-2: Intel 8 Series/C220 Series High Definition Audio
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
chip-ID: 8086:8c20 class-ID: 0403
API: ALSA v: k6.2.12-1-default status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: aRts v: 1.5.10 status: off with: artswrapper status: off
tools: artsdsp
Server-2: PipeWire v: 0.3.69 status: off with: wireplumber status: off
tools: pw-cat,pw-cli,wpctl
# aplay /usr/share/sounds/alsa/test.wav # analog audio works normally
Playing WAVE '/usr/share/sounds/alsa/test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
# rpm -qa | grep -E 'alsa|arts|gstr|jack|mix|pavu|puls|sof-f|wire' | sort
alsa-1.2.9-1.1.x86_64
alsa-firmware-1.2.4-4.4.noarch
alsa-oss-1.1.8-5.2.x86_64
alsa-plugins-1.2.7.1-4.4.x86_64
alsa-plugins-speexrate-1.2.7.1-4.4.x86_64
alsa-plugins-upmix-1.2.7.1-4.4.x86_64
alsa-ucm-conf-1.2.9-1.1.noarch
alsa-utils-1.2.9-1.1.x86_64
arts-1.5.10-39.88.x86_64
gstreamer-1.22.2-1.1.x86_64
gstreamer-plugins-base-1.22.2-1.1.x86_64
kdelibs3-arts-3.5.10-243.20.x86_64
kdemultimedia3-arts-3.5.10.1-81.24.x86_64
kdemultimedia3-mixer-3.5.10.1-81.24.x86_64
libgstreamer-1_0-0-1.22.2-1.1.x86_64
libgstriff-1_0-0-1.22.2-1.1.x86_64
libjack0-1.9.22-1.1.x86_64
libpipewire-0_3-0-0.3.69-2.1.x86_64
libpulse0-16.1-3.1.x86_64
libwireplumber-0_4-0-0.4.14-1.1.x86_64
PackageKit-gstreamer-plugin-1.2.5-9.2.x86_64
pipewire-0.3.69-2.1.x86_64
pipewire-modules-0_3-0.3.69-2.1.x86_64
pipewire-spa-plugins-0_2-0.3.69-2.1.x86_64
pipewire-spa-tools-0.3.69-2.1.x86_64
pipewire-tools-0.3.69-2.1.x86_64
sof-firmware-2.2.4-1.2.noarch
wireplumber-0.4.14-1.1.x86_64
# systemctl --global --user status pipewire.{service,socket}
* pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: disabled)
Active: inactive (dead)
TriggeredBy: * pipewire.socket
* pipewire.socket - PipeWire Multimedia System Socket
Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; preset: enabled)
Active: active (listening) since Fri 2023-05-12 19:12:42 EDT; 6min ago
Triggers: * pipewire.service
Listen: /run/user/0/pipewire-0 (Stream)
CGroup: /user.slice/user-0.slice/user@0.service/app.slice/pipewire.socket
#
Last update was yesterday or the day before. I’ve no idea if my system is more dependent on pipewire or pulse audio. My (very, very limited) understanding was that pipewire is slowly replacing pulse audio?
I’ve just had the same issue. I had a look around in yast, and it seems that in my system there are lots of connections to alsa-pulse, and none to pipewire - so I uninstalled pipewire - I assume that’ll be the path of least resistance…
@rokejulianlockhart read the changelog (As a Tumbleweed user you should follow the Development Mailing List) a conflict was created to replace alsa-plugins-pulse.
Which option to choose may depend on whether you prefer pulse over pipewire. I had switched TW to pipewire, but after experiencing sound glitches in the form of dropouts, I switched back to pulse (after extensive searches and experimentation to try and resolve the issue). So I figured option 2 might suit me better.