-
Notifications
You must be signed in to change notification settings - Fork 63
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 latest chromium (85.0.4183.102) #51
Comments
Yup, I'm experiencing the same as of this morning. Looking into it. |
I can't find anything at all that's changed about Chromium between 84 and 85, although I'm no Chromium expert. Every other app I try is working correctly. I also tried some older xdpw commits before we made some changes to buffer reuse and that has no effect. What's even stranger is that if I continue trying to cast, eventually the preview window breaks (seemingly shows nothing, but actually contains an all white display), but the actual cast starts working. I'm at a loss for today. |
I'm also running 85.0.4183.102-1 here and I don't have this issue However, I cannot choose a specific screen, I can only share my second monitor, no idea if it is a normal behaviour or not... |
@pjeanjean It is normal. Eventually output selection will be enabled by a separate mechanism (see #12) Can I ask what distro you are using? Both myself and @joelazar are using Arch Linux, so maybe it is a distro specific issue. |
I'm also running Arch, and using sway as WM. |
@pjeanjean Can you run this for me so I can compare version numbers (if you use yay, if not, pacman should work).
|
I have another computer running sway on Arch, on which I'm using PipeWire a bit more, I will check if it also works when I get back home and I will report back. |
@pjeanjean Thanks for your help. This is bizarre. And you're using the regular old chromium package from pacman? |
Yes, I never managed to run chromium-ozone |
Hmmm, very confusing. Thanks for the info. Let me know how things are working on your other system. |
I've been having the exact same issue for a while now. Downgrading pipewire to pipewire-0.3.2-3.fc32.x86_64 fixed it for me, but it's quite unstable. I think it's making my machine lag a lot (libinput 1.16 complains a lot about lag while/after csting my screen). I'm on Fedora 32 and Chrome 85.0.4183.102 |
Looks like screen sharing also works on my other system. Funny thing is that I also use Pipewire as audio backend on this one (the first computer I tested was running regular Pulse and JACK2), and it caused segfaults whenever the screencast popup was supposed to open. |
I was unable to share my screen in Chromium lately, as well. However, my issue seems to have been fixed in |
yeah, I just wanted to write the same that it works for me now too with the following setup:
|
Glad to hear this is resolved for some in this thread. @grizonic are you also able to resolve your issue by upgrading xdg-desktop-portal? I'll test this myself shortly and close the issue if it seems fixed. |
Yup, confirmed this is working again. |
I've recently noticed that the screen casting is not working anymore with the current latest chromium (85.0.4183.102) on arch.
With the same versions I did manage to get it working with an older chromium version (84.0.4147.135-1) and I gathered the logs from this command (
/usr/lib/xdg-desktop-portal -r & /usr/lib/xdg-desktop-portal-wlr -l DEBUG
) with both of them.With 85.0.4183.102
With 84.0.4147.135-1
The text was updated successfully, but these errors were encountered: