I tried to stop #Thunderbird/#Firefox from using the #pulseaudio socket of #pipewire because of a bug in Debian that renders the audio daemons useless after some time: sockets do not get closed and the only way to get audio back when there are no sockets left is to restart.
The way I tried to do it didn't work completely. #Firefox still opens sockets to the pulseaudio daemon - even though the processes show that they run in an environment containing PULSE-SERVER=unix:/dev/null.
Any ideas how I stop firefox using that pulseaudio socket? Mount namespace - does it include sockets? A restriction on a systemd slice (cgroup) I could use?
That looks really great! Can't wait see it filled with life.
Meanwhile I'll share my solution. I'm an #email user since more than 30 years and I'm running my own email server since nearly the start of it.
The lack of having a reliable email client for my #Librem5, my sons #pinephone and #MobileLinux in general bothered me a long time. #Geary didn't fit my needs and #Thunderbird which I use on my desktop is no option for mobile devices, yet.
I ended up using #tangram to access a #selfhosted #snappymail.
I intentionally broke audio output of #Mozilla #Thunderbird and #Firefox:
https://chrichri.ween.de/o/e65a99d0fd024803b9cf59e0bd6da85a
Lately I found that I'd sometimes like to click on audio content people are sharing. I do and somehow expectedly I can't hear what Firefox starts playing.
Found OpenWith which allows to open an URL through its context menu with any configured external program.
Now I can open links to a lot of content by using FreeTube.
Sometimes listening isn't enough. Had to go into a video conference yesterday. Listening to music on my #Librem5 worked fine, but when I tried to get audio in the conference I remembered that my desktop is broken, because of this #Debian #Bookworm #Pipewire issue I wrote about.
I had to ask the other participants to wait, because I'd need to restart my desktop to get sound. Not funny if connected with people partly working on Apple devices.
#Workaround time: the major problem at the time being in my use case seems to be #Mozilla #Firefox and #Thunderbird leaving sockets to pipewire-#pulseaudio open.
I now run them using PULSE-SERVER=unix:/dev/null <program> and it seems they really do not connect to pipewire-pulse anymore and therefor can't leave its sockets open.
No sound in #Mozilla apps is o.k. - I can always run #ungoogled-#chromium if I need a page deliver sound.