-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Screencast not working with Chromium or Firefox #271
Comments
I also tried this test script (after having installed > python xdp-screen-cast.py
session /org/freedesktop/portal/desktop/session/1_261/u1 created
sources selected
streams:
stream 126
X connection to :0 broken (explicit kill or server shutdown). |
Can you try the flatpak versions of Firefox and Chromium, please? |
@columbarius Chromium on Arch fails like @WhyNotHugo described for me, and the version from flatpak fails the same:
In fact it's actually slightly worse - the flatpak version shows the same |
i have the same error when trying to share my screen with chromium:
however, screen sharing works with firefox. is there any fix for this yet? i have followed all of the troubleshooting guides but couldn't fix it yet. i am on alpine linux edge. |
Odd,
|
I encountered the same issue. I think the next release of xdg-desktop-portal will fix this. https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/issues/74 for the time being I have just following packages installed
|
I only have xdg-desktop-portal, xdg-desktop-portal-gtk, and xdg-desktop-portal-wlr installed, so @romanstingler's workaround isn't fixing it for me, FYI. |
afaict this is caused by the now-infamous webrtc bug (https://bugs.chromium.org/p/webrtc/issues/detail?id=15174), because applying the webrtc fix in question to firefox fixes it for me (will test chromium after it builds) |
What is the easiest way to apply the fix? Or, do we know if any firefox or chromium pre-release include the fix? It doesn't look like chromium has decided whether or not to include the fix in the upcoming v114, for example. |
that is interesting. |
you would have to apply the patch to the webrtc in the tarball of chromium or firefox and build it yourself (or get your distro to do it), and yes, that won't fix flatpak and similar.. an example for firefox and chromium a noted hacky other workaround is PIPEWIRE_DEBUG=4 (yes, really), but that didn't fix it for me
yes, seemingly that will be all the way in 115.. for firefox, it's in 114b, so also will be in 114 https://bugzilla.mozilla.org/show_bug.cgi?id=1832770 that said, it's not guaranteed this would fix it, you might also have other issues |
Thank you @nekopsykose, that's very helpful. I can confirm that Firefox 114.0b8 can screenshare for me, when 113.0.2 could not :) |
glad it was that simple then :D |
yep, fixed there too @WhyNotHugo should work for you as well now |
just updated chromium to 113.0.5672.126-r2, works :) (alpine edge) |
Chromium 114 on Arch, which presumably hasn't been patched by the distro for this, still doesn't work. So I imagine upstream might include the webrtc fix in the 115 beta. For now, back to Firefox for video calls :) |
on firefox 114.0b9, i am facing this issue:
they are right, atleast it tries to screenshare, but i get this error. edit: i had |
Oh is screen capture with 10-bit an xdg-desktop-portal-wlr issue or a pipewire issue? As the errors I get when I have Trying to capture the 4k monitor (10-bit) in
Trying to capture the 4k monitor (10-bit) in
Ending Screenshare:
I can capture games in obs with |
i had it working for a while with the same sway 10-bit depth (in browser etc), so it's probably something else |
Hi. I have this problem on Debian testing. Black screen with frozen mouse cursor. But It seems that Chromium, Chrome and Firefox do not even attempt to connect to portals or pipewire.
If laucnhed without All browsers run wayland-native, ozone and webrtc flags in Crhom* are applied. Other wayland apps, like screenshots and screen recorders are working. I have a feeling that I'm missing something trivial.
|
Can you provide logs for the xdg-desktop-portal?
Recent versions require explicitly configuring the backend implementation that should be used (eg: wlr). Have you done this?
Have you checked the troubleshooting instruction in the wiki?
|
Sorry, false alarm. |
This issue still exists for me, when using chromium/obs/slack/zoom. In firefox however screen sharing works fine. xdg_desktop_portal output
xdg-desktop-portal-wlr output
chromium logs this error:
Steps to reproduce:
|
for me in chromium it works intermittently on my notebook with external monitor. I tried sharing my external one, was black. but I have only these installed
|
I'm running
xdg-desktop-portal
. It only yields a bunch of unrelated output:Another terminal is running
usr/libexec/xdg-desktop-portal-wlr
, which also provides no useful output:On chrome, when I try to screencast at https://mozilla.github.io/webrtc-landing/gum_test.html, if I pick "Entire Screen" it logs:
But the screencast area is just solid black with "FPS now: NaN , entire capture: NaN".
Firefox logs nothing, and shows nothing (e.g.: not even a black region).
When I screencast from chromium, xdp-wlr logs:
Versions of related components:
wireplumber
,pipewire
andpipewire-pulse
are all running. Also:Running this test script:
The text was updated successfully, but these errors were encountered: