Using #pipewire for screen sharing alongside #pulseaudio for audio hasn't been a great experience and complicated stuff a lot. I had it working by disabling all audio in pipewire, but I switched back to a complete pipewire setup.

I enabled #Debian #backports and installed the newer packages from there. I hope this'll improve the situation in one of two ways:

• solve the issue with open memfd or at least let it take longer to occure
• give me a version of pipewire and #wireplumber that is not that much outdated that even the official online documentation doesn't cover it anymore

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.