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
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
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.
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.