The following packages have unmet dependencies: pipewire-audio: Conflicts: pulseaudio Conflicts: pulseaudio-module-bluetooth but 1:16.1+dfsg1-2ubuntu10.1 is to be installed Conflicts: pulseaudio pipewire-alsa: Conflicts: pulseaudio Conflicts: pulseaudio
This installation has been active since 22.04. It has been updated since, not reinstalled. I have made no explicit changes to the sound system other than my usb external interface has been removed (in the middle of moving) and I am using an bluetooth sound bar for sound.
~$ pactl info
Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 109
Tile Size: 65472
User Name: somebody
Host Name: somewhere
Server Name: PulseAudio (on PipeWire 1.2.6)
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: bluez_output.00_18_96_B0_04_04.1
Default Source: bluez_output.00_18_96_B0_04_04.1.monitor
Cookie: a685:114f
I should not have to. You want me to randomly uninstall packages and hope everything works? I think the installer should be the one to resolve this. Not me.
Sure, I agree. But until this packaging conflict can be fixed, it is what is needed.
There is a bug report:
I’d have been able to be a guinea pig to be able to verify what happens, but I very recently had to replace my OS drive, so I don’t have a system that was upgraded from 22.04 any longer.
I may see if this is something my ancient and rusty packaging knowledge can fix.
Thanks! This helped me to update KDE Neon Testing. Discovery freezed to loading packets. Pkcon refresh + update produced just silmilair error message. Now it updated ok.
It’s worth noting that the bug is now marked as resolved but it didn’t actually fix it for people that were already blocked, I still had to manually uninstall pulseaudio.
I too installed when 22.04 was the base and have been updating since, so I assume that’s the commonality here and why pulseaudio was installed, though never removed despite having no packages depending on it.
For anyone still stuck on this, manual intervention appears to be the only fix.
For me a simple sudo apt remove pulseaudio and then restarting Discover allowed Discover to update.