On 9/28/20 3:18 PM, Anton Aylward wrote:
On 28/09/2020 15:45, David C. Rankin wrote:
On 9/28/20 4:39 AM, Wolfgang Rosenauer wrote:
On Leap 15.2, both firefox and chromium require libpipewire - I don't know if that is just our packaging though. as I understood pipewire is required (at least) for WebRTC screensharing when Firefox is running on wayland.
That may be, if you use any of that, but pipewire should not be bundled as a dependency of firefox. firefox works just fine without it. Plays video and audio just fine, etc..
This should definitely be one of those areas where the user has a choice. If the user needs all that fluff and wants pipewire to handle it, then they can certainly load pipewire. But for the user that doesn't use any of that, pipewire should not be up and running by default with no way to turn it off and now way to uninstall the openSUSE version pipewire without it also wanting to uninstall Firefox.
Remember, a new "feature" to some is a "bug" to others *if it can't be turned off*....
+1
Have you considered unloading pipewire and the 'suse" version of Firefox then loading Firefox from the Mozilla repository, built without suse.
That is likely what I will try before going to the mozila ftp site. I try and keep the VMs pure openSUSE. Up to the last few weeks 15.2 either didn't have pipewire or it wasn't being started by default. Now it takes more resources than Xorg -- even though there is no firefox started or running. It openSUSE bundled pipewire with the pipewire.service from upstream -- there would be no problem, I could simply stop and disable the serive, but openSUSE omits that file and pipewire is simply spinning away. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org