Comment # 11 on bug 1172903 from Atri Bhattacharya

(In reply to Martin Mare�� from comment #10)
> (In reply to Atri Bhattacharya from comment #1)
> > This patch should ensure chromium should work with pipewire 0.3. Why would
> > you need pipewire 0.2 then?
> I'm more Google Chrome user so I wanted to get it running without a patch
> ;-) but maybe it's time to move to Chromium... I was also thinking about
> Electron apps (like Skype and MS Teams) where the patch cannot be easily
> applied (but I don't know how it works there) :-/ 
> 

I see. I suppose we ought to try and see if simply having a parallel
installable pipewire-modules = 0.2.x does solve this.

> > Btw, I have pkgs for pipewire02 in my home repository now (or shortly --
> > still bulding):
> > https://software.opensuse.org//download.
> > html?project=home%3Abadshah400&package=pipewire02
> > Installing them doesn't help however (as I expected).
> 
> I tested it too and Google Chrome even crashed in my case (There was
> something with Sandboxing).

That is surprising. Did you install the pipewire02-modules package? That is
what you will need.

I also want to keep this compat package as small as possible, so I remove
several components from it assuming they aren't needed for WebRTC directly. I
can try restoring them back one by one and see if that helps. It would be
helpful if you leave your comments about this package here:
https://build.opensuse.org/package/show/home:badshah400/pipewire02
instead of this bug, where we will continue to keep track of the progress in
getting WebRTC on Wayland for chromium and firefox working.

>
> I tried to make a sim-link to libpipewire-0.3.so.0 (expecting we have new
> 0.3 API pointing to 0.2 lib) but it didn't help me.

Yeah, this won't help.