With recent updates on F40 on kde+wayland I cannot share a window in a meeting anymore. When this option is selected a black window is shown in the preview and to the other side of the conversation. Fortunately, sharing the entire screen still works.
On Mon, 2024-05-20 at 07:07 -0400, Neal Becker wrote:
With recent updates on F40 on kde+wayland I cannot share a window in a meeting anymore. When this option is selected a black window is shown in the preview and to the other side of the conversation. Fortunately, sharing the entire screen still works. --
Don't know the answer, but it might be useful to state what kind of meeting app you're talking about.
poc
On Mon, May 20, 2024, 7:58 AM Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Mon, 2024-05-20 at 07:07 -0400, Neal Becker wrote:
With recent updates on F40 on kde+wayland I cannot share a window in a meeting anymore. When this option is selected a black window is shown in the preview and to the other side of the conversation. Fortunately, sharing the entire screen still works. --
Don't know the answer, but it might be useful to state what kind of meeting app you're talking about.
poc
This was the MS teams webapp, using chrome browser.
On Mon, May 20, 2024 at 10:41 AM Neal Becker ndbecker2@gmail.com wrote:
On Mon, May 20, 2024, 7:58 AM Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Mon, 2024-05-20 at 07:07 -0400, Neal Becker wrote:
With recent updates on F40 on kde+wayland I cannot share a window in a meeting anymore. When this option is selected a black window is shown in the preview and to the other side of the conversation. Fortunately, sharing the entire screen still works. --
Don't know the answer, but it might be useful to state what kind of meeting app you're talking about.
poc
This was the MS teams webapp, using chrome browser.
After some more experiments I see it is a problem with both chrome-browser-stable and chrome-browser-beta. But firefox works OK. Unfortunately firefox is not fully functional with MS teams, so that's not a solution. With chrome when sharing a window the shared window flashes between displaying and a black window as I move the mouse. Quite unusable.
Hi,
Can you try Firefox, after you do following: 1) Go to "about:config" 2) Enable "widget.dmabuf.enabled" 3) Enable "widget.dmabuf.force-enabled" 4) Restart Firefox
Does it still work in Firefox? What GPU do you use?
Regards, Jan
po 20. 5. 2024 v 17:28 odesílatel Neal Becker ndbecker2@gmail.com napsal:
On Mon, May 20, 2024 at 10:41 AM Neal Becker ndbecker2@gmail.com wrote:
On Mon, May 20, 2024, 7:58 AM Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Mon, 2024-05-20 at 07:07 -0400, Neal Becker wrote:
With recent updates on F40 on kde+wayland I cannot share a window in a meeting anymore. When this option is selected a black window is shown in the preview and to the other side of the conversation. Fortunately, sharing the entire screen still works. --
Don't know the answer, but it might be useful to state what kind of meeting app you're talking about.
poc
This was the MS teams webapp, using chrome browser.
After some more experiments I see it is a problem with both chrome-browser-stable and chrome-browser-beta. But firefox works OK. Unfortunately firefox is not fully functional with MS teams, so that's not a solution. With chrome when sharing a window the shared window flashes between displaying and a black window as I move the mouse. Quite unusable.
-- _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On Mon, May 20, 2024 at 12:10 PM Jan Grulich jgrulich@redhat.com wrote:
Hi,
Can you try Firefox, after you do following:
- Go to "about:config"
- Enable "widget.dmabuf.enabled"
- Enable "widget.dmabuf.force-enabled"
- Restart Firefox
Does it still work in Firefox? What GPU do you use?
Regards, Jan
Thanks. Only "widget.dmabuf.force-enabled" was not enabled. After setting to True, I retested. Sharing on firefox works fine. Sharing on google-chrome-stable, google-chrome-beta, and brave-browser are not functional.
po 20. 5. 2024 v 19:18 odesílatel Neal Becker ndbecker2@gmail.com napsal:
On Mon, May 20, 2024 at 12:10 PM Jan Grulich jgrulich@redhat.com wrote:
Hi,
Can you try Firefox, after you do following:
- Go to "about:config"
- Enable "widget.dmabuf.enabled"
- Enable "widget.dmabuf.force-enabled"
- Restart Firefox
Does it still work in Firefox? What GPU do you use?
Regards, Jan
Thanks. Only "widget.dmabuf.force-enabled" was not enabled. After setting to True, I retested. Sharing on firefox works fine. Sharing on google-chrome-stable, google-chrome-beta, and brave-browser are not functional. --
Can you try to get older Firefox 125 from Koji? We applied a related patch to Firefox 126 so it might be the one that makes it work for you in Firefox.
Jan
On Mon, May 20, 2024 at 1:24 PM Jan Grulich jgrulich@redhat.com wrote:
po 20. 5. 2024 v 19:18 odesílatel Neal Becker ndbecker2@gmail.com napsal:
On Mon, May 20, 2024 at 12:10 PM Jan Grulich jgrulich@redhat.com wrote:
Hi,
Can you try Firefox, after you do following:
- Go to "about:config"
- Enable "widget.dmabuf.enabled"
- Enable "widget.dmabuf.force-enabled"
- Restart Firefox
Does it still work in Firefox? What GPU do you use?
Regards, Jan
Thanks. Only "widget.dmabuf.force-enabled" was not enabled. After setting to True, I retested. Sharing on firefox works fine. Sharing on google-chrome-stable, google-chrome-beta, and brave-browser are not functional. --
Can you try to get older Firefox 125 from Koji? We applied a related patch to Firefox 126 so it might be the one that makes it work for you in Firefox.
Jan
Trying firefox 125. Sharing appears to be working (but I didn't play with widget.dmabuf.force-enabled, which is False).
po 20. 5. 2024 v 19:55 odesílatel Neal Becker ndbecker2@gmail.com napsal:
On Mon, May 20, 2024 at 1:24 PM Jan Grulich jgrulich@redhat.com wrote:
po 20. 5. 2024 v 19:18 odesílatel Neal Becker ndbecker2@gmail.com napsal:
On Mon, May 20, 2024 at 12:10 PM Jan Grulich jgrulich@redhat.com wrote:
Hi,
Can you try Firefox, after you do following:
- Go to "about:config"
- Enable "widget.dmabuf.enabled"
- Enable "widget.dmabuf.force-enabled"
- Restart Firefox
Does it still work in Firefox? What GPU do you use?
Regards, Jan
Thanks. Only "widget.dmabuf.force-enabled" was not enabled. After setting to True, I retested. Sharing on firefox works fine. Sharing on google-chrome-stable, google-chrome-beta, and brave-browser are not functional. --
Can you try to get older Firefox 125 from Koji? We applied a related patch to Firefox 126 so it might be the one that makes it work for you in Firefox.
Jan
Trying firefox 125. Sharing appears to be working (but I didn't play with widget.dmabuf.force-enabled, which is False).
Can you please try that? It's important to have the same setup as Chrome. Firefox does some driver checking and can disable dmabufs, which makes it to use different buffers for screen sharing. Both Firefox and Chrome are 1:1 when it comes to screen sharing and this is the only thing that comes to my mind that can make the difference.
Also, can you try to run Chrome in a terminal and see if there is anything reported?
On Mon, May 20, 2024 at 2:07 PM Jan Grulich jgrulich@redhat.com wrote:
po 20. 5. 2024 v 19:55 odesílatel Neal Becker ndbecker2@gmail.com napsal:
On Mon, May 20, 2024 at 1:24 PM Jan Grulich jgrulich@redhat.com wrote:
po 20. 5. 2024 v 19:18 odesílatel Neal Becker ndbecker2@gmail.com napsal:
On Mon, May 20, 2024 at 12:10 PM Jan Grulich jgrulich@redhat.com wrote:
Hi,
Can you try Firefox, after you do following:
- Go to "about:config"
- Enable "widget.dmabuf.enabled"
- Enable "widget.dmabuf.force-enabled"
- Restart Firefox
Does it still work in Firefox? What GPU do you use?
Regards, Jan
Thanks. Only "widget.dmabuf.force-enabled" was not enabled. After setting to True, I retested. Sharing on firefox works fine. Sharing on google-chrome-stable, google-chrome-beta, and brave-browser are not functional. --
Can you try to get older Firefox 125 from Koji? We applied a related patch to Firefox 126 so it might be the one that makes it work for you in Firefox.
Jan
Trying firefox 125. Sharing appears to be working (but I didn't play with widget.dmabuf.force-enabled, which is False).
Can you please try that? It's important to have the same setup as Chrome. Firefox does some driver checking and can disable dmabufs, which makes it to use different buffers for screen sharing. Both Firefox and Chrome are 1:1 when it comes to screen sharing and this is the only thing that comes to my mind that can make the difference.
I can confirm that on firefox 125 with widet.dmabuf.force-enabled=True I see the same problem. When sharing the content flashes on/off as I move the mouse. I checked again that with widget.dmabuf.force-enabled=False I do not see a problem.
Also, can you try to run Chrome in a terminal and see if there is anything reported?
Nothing interesting in the terminal window.
út 21. 5. 2024 v 1:49 odesílatel Neal Becker ndbecker2@gmail.com napsal:
On Mon, May 20, 2024 at 2:07 PM Jan Grulich jgrulich@redhat.com wrote:
po 20. 5. 2024 v 19:55 odesílatel Neal Becker ndbecker2@gmail.com napsal:
On Mon, May 20, 2024 at 1:24 PM Jan Grulich jgrulich@redhat.com wrote:
po 20. 5. 2024 v 19:18 odesílatel Neal Becker ndbecker2@gmail.com napsal:
On Mon, May 20, 2024 at 12:10 PM Jan Grulich jgrulich@redhat.com wrote:
Hi,
Can you try Firefox, after you do following:
- Go to "about:config"
- Enable "widget.dmabuf.enabled"
- Enable "widget.dmabuf.force-enabled"
- Restart Firefox
Does it still work in Firefox? What GPU do you use?
Regards, Jan
Thanks. Only "widget.dmabuf.force-enabled" was not enabled. After setting to True, I retested. Sharing on firefox works fine. Sharing on google-chrome-stable, google-chrome-beta, and brave-browser are not functional. --
Can you try to get older Firefox 125 from Koji? We applied a related patch to Firefox 126 so it might be the one that makes it work for you in Firefox.
Jan
Trying firefox 125. Sharing appears to be working (but I didn't play with widget.dmabuf.force-enabled, which is False).
Can you please try that? It's important to have the same setup as Chrome. Firefox does some driver checking and can disable dmabufs, which makes it to use different buffers for screen sharing. Both Firefox and Chrome are 1:1 when it comes to screen sharing and this is the only thing that comes to my mind that can make the difference.
I can confirm that on firefox 125 with widet.dmabuf.force-enabled=True I see the same problem. When sharing the content flashes on/off as I move the mouse. I checked again that with widget.dmabuf.force-enabled=False I do not see a problem.
That's what I expected.
This issue will be fixed in Chrome/Chromium 127, sadly it missed the branching by a day. I will try to request this to be fixed in M126.
WebRTC issue: https://issues.webrtc.org/issues/338232699 WebRTC fix: https://webrtc-review.googlesource.com/c/src/+/349881
Jan
Also, can you try to run Chrome in a terminal and see if there is anything
reported?
Nothing interesting in the terminal window.
On Tue, May 21, 2024, 2:17 AM Jan Grulich jgrulich@redhat.com wrote:
út 21. 5. 2024 v 1:49 odesílatel Neal Becker ndbecker2@gmail.com napsal:
On Mon, May 20, 2024 at 2:07 PM Jan Grulich jgrulich@redhat.com wrote:
po 20. 5. 2024 v 19:55 odesílatel Neal Becker ndbecker2@gmail.com napsal:
On Mon, May 20, 2024 at 1:24 PM Jan Grulich jgrulich@redhat.com wrote:
po 20. 5. 2024 v 19:18 odesílatel Neal Becker ndbecker2@gmail.com napsal:
On Mon, May 20, 2024 at 12:10 PM Jan Grulich jgrulich@redhat.com wrote:
> Hi, > > Can you try Firefox, after you do following: > 1) Go to "about:config" > 2) Enable "widget.dmabuf.enabled" > 3) Enable "widget.dmabuf.force-enabled" > 4) Restart Firefox > > Does it still work in Firefox? What GPU do you use? > > Regards, > Jan >
Thanks. Only "widget.dmabuf.force-enabled" was not enabled. After setting to True, I retested. Sharing on firefox works fine. Sharing on google-chrome-stable, google-chrome-beta, and brave-browser are not functional. --
Can you try to get older Firefox 125 from Koji? We applied a related patch to Firefox 126 so it might be the one that makes it work for you in Firefox.
Jan
Trying firefox 125. Sharing appears to be working (but I didn't play with widget.dmabuf.force-enabled, which is False).
Can you please try that? It's important to have the same setup as Chrome. Firefox does some driver checking and can disable dmabufs, which makes it to use different buffers for screen sharing. Both Firefox and Chrome are 1:1 when it comes to screen sharing and this is the only thing that comes to my mind that can make the difference.
I can confirm that on firefox 125 with widet.dmabuf.force-enabled=True I see the same problem. When sharing the content flashes on/off as I move the mouse. I checked again that with widget.dmabuf.force-enabled=False I do not see a problem.
That's what I expected.
This issue will be fixed in Chrome/Chromium 127, sadly it missed the branching by a day. I will try to request this to be fixed in M126.
WebRTC issue: https://issues.webrtc.org/issues/338232699 WebRTC fix: https://webrtc-review.googlesource.com/c/src/+/349881
Jan
Also, can you try to run Chrome in a terminal and see if there is anything
reported?
Nothing interesting in the terminal window.
Thanks so much for your help! Needless to say, being able to conduct
remote meetings is a vital use case. Neal
út 21. 5. 2024 v 13:06 odesílatel Neal Becker ndbecker2@gmail.com napsal:
On Tue, May 21, 2024, 2:17 AM Jan Grulich jgrulich@redhat.com wrote:
út 21. 5. 2024 v 1:49 odesílatel Neal Becker ndbecker2@gmail.com napsal:
On Mon, May 20, 2024 at 2:07 PM Jan Grulich jgrulich@redhat.com wrote:
po 20. 5. 2024 v 19:55 odesílatel Neal Becker ndbecker2@gmail.com napsal:
On Mon, May 20, 2024 at 1:24 PM Jan Grulich jgrulich@redhat.com wrote:
po 20. 5. 2024 v 19:18 odesílatel Neal Becker ndbecker2@gmail.com napsal:
> > > On Mon, May 20, 2024 at 12:10 PM Jan Grulich jgrulich@redhat.com > wrote: > >> Hi, >> >> Can you try Firefox, after you do following: >> 1) Go to "about:config" >> 2) Enable "widget.dmabuf.enabled" >> 3) Enable "widget.dmabuf.force-enabled" >> 4) Restart Firefox >> >> Does it still work in Firefox? What GPU do you use? >> >> Regards, >> Jan >> > > Thanks. Only "widget.dmabuf.force-enabled" was not enabled. After > setting to True, I retested. Sharing on firefox works fine. > Sharing on google-chrome-stable, google-chrome-beta, and > brave-browser are not functional. > -- >
Can you try to get older Firefox 125 from Koji? We applied a related patch to Firefox 126 so it might be the one that makes it work for you in Firefox.
Jan
Trying firefox 125. Sharing appears to be working (but I didn't play with widget.dmabuf.force-enabled, which is False).
Can you please try that? It's important to have the same setup as Chrome. Firefox does some driver checking and can disable dmabufs, which makes it to use different buffers for screen sharing. Both Firefox and Chrome are 1:1 when it comes to screen sharing and this is the only thing that comes to my mind that can make the difference.
I can confirm that on firefox 125 with widet.dmabuf.force-enabled=True I see the same problem. When sharing the content flashes on/off as I move the mouse. I checked again that with widget.dmabuf.force-enabled=False I do not see a problem.
That's what I expected.
This issue will be fixed in Chrome/Chromium 127, sadly it missed the branching by a day. I will try to request this to be fixed in M126.
WebRTC issue: https://issues.webrtc.org/issues/338232699 WebRTC fix: https://webrtc-review.googlesource.com/c/src/+/349881
Jan
Also, can you try to run Chrome in a terminal and see if there is
anything reported?
Nothing interesting in the terminal window.
Thanks so much for your help! Needless to say, being able to conduct
remote meetings is a vital use case. Neal --
FYI: the fix was backported to M126 , which is going to be released in ~2 weeks.
Jan