I removed pulseaudio with pacman -Rdd, i want to keep the things that depend on pulseaudio. However, its still detected as a dependency conflict
mactan@mactan-desktop ~ $ pacman -Qi pulseaudio
Name : pipewire-pulse
Version : 0.3.19-1
Description : Server and user space API to deal with multimedia pipelines (PulseAudio replacement)
Architecture : x86_64
mactan@mactan-desktop ~ $ pulseaudio --version
bash: pulseaudio: command not found
mactan@mactan-desktop ~ $ pactl info
Server String: /run/user/1000/pulse/native
Library Protocol Version: 34
Server Protocol Version: 34
Is Local: yes
Client Index: 48
Tile Size: 65472
User Name: mactan
Host Name: mactan-desktop
Server Name: PulseAudio (on PipeWire 0.3.19)
Server Version: 14.0.0
I was reading through the thread in the process of removing pulseaudio and changing to Pipewire. If I read everything correctly can you confirm these steps are correct:
Most browsers used to rely on X11 for capturing the desktop (or individual applications) when using WebRTC (e.g. on Google Hangouts). On Wayland, the sharing mechanism is handled differently for security reasons. PipeWire enables sharing content under Wayland with fine-grained access controls.
This requires xdg-desktop-portal and one of its backends to be installed. The available backends are:
-xdg-desktop-portal-gtk for GNOME
-xdg-desktop-portal-kde for KDE
pipewire-pulse is a PipeWire package to replace PulseAudio pamac info pipewire-pulse confirms that this package is marked as conflicting with pulseaudio
Description : Low-latency audio/video router and processor -
PulseAudio replacement
Conflicts With : pulseaudio pulseaudio-bluetooth
And pamac install pipewire-pulse requests removal of 2 packages from my system
To remove (2):
pulseaudio-jack 14.2-2 (Depends On: pulseaudio) extra
pulseaudio 14.2-2 (Conflicts With: pipewire-pulse) extra
Both packages pipewire-pulse and pulseaudio could not be installed because of the conflicts
It is good to see that pulseeffects v5.0.1 in Arch now has an accurate description because the misleading description in v5.0.0 created some confusion
Description : Audio Effects for Pulseaudio Applications
But the misleading package name is likely to continue to confuse some users
I would not recommend Manjaro users switch from PulseAudio to PipeWire because there appears to be no support available on this forum
But if users want to replace PipeWire with Pulseaudio, all that should be needed is to install the metapackage manjaro-pipewire
There is also a metapackage manjaro-pulse to get back to PulseAudio if needed
Thanks for your good feedback. I have made some updates to the note with my reasoning. As pipeline become more stable and people want to test then atleast they will have the groups here feedback on how to do it.
Additionally the one item I noticed which maybe a bug between Gnome and Pipewire is trying to redirect audio to HDMI. Its a bit finicky when I have my laptop monitor and external monitor running at the same time. What will happen is you won’t see an option to choose HDMI for audio. So I will bug this:
Good point. If I play with the audio settings, unplug and replug the hdmi eventually shows up but is not staying. If I am in single screen mode (make the HDMI display primary) then I am more likely to have HDMI choice for audio.
But this flakiness still makes it a bug for me. I know it will get better with all the people contributing.
Interestingly enough i did try removing manjaro-pipewire and then installed back manjaro-pulse and the GUI loaded with a fatal error after rebooting.
So i went to command line and ran journalctl -r and noticed the error:
org.shell.desktop /usr/bin/gnome-shell: error while loading shared libraries: libpipewire-0.3.so.0 cannot open shared object file: No such file or directory
Looks like something is referencing pipewire.
Any ideas what i might need to do to go back to pulseaudio?
Thanks for the suggestion. On a technical standpoint if HDMI audio works on pulseaudio but not on pipewire it would be quite an edge test case if it was a bad cable.
That being said (as someone else might read this post) I have a TV and Monitor with different HDMI cables to re-produce the issue. So the missing HDMI audio option is probably a software bug to be fixed in the future.
I can confirm our cousins at Endeavor OS were able to re-produce the audio switching issue where ‘pavucontrol’ is being used to switch settings when gnome audio can’t.