Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Learn More

Firefox upgrade from 115 -> 116 results in “broken” screen capture

  • 4 Antworten
  • 0 haben dieses Problem
  • 46 Aufrufe
  • Letzte Antwort von jeezusjr

more options

Reposting from https://discourse.mozilla.org/t/firefox-upgrade-from-115-116-results-in-broken-screen-capture/121964

Howdy folks!

I am on Arch Linux and recently upgraded Firefox from 115 to 116 and this broke WebRTC screen capture. Whenever I try to share my screen in Microsoft teams and Google Meet, the participants only see a black screen with a cursor. I am able to reproduce the issue on this test page. I had to downgrade to 115 in order to “fix” this critical feature. Before that it was broken in 114 and I had to use Chromium for presentations. I no longer want to touch Chrome with a 100 ft pole since they are trying to introduce Web Environment Integrity.

The only bug I have been able to find is from three years ago:

https://bugzilla.mozilla.org/show_bug.cgi?id=1640771

I don’t want to add a “me too” comment, but was wondering how to show/give my support to get this issue fixed? It is crippling to my work workflow, and I don’t want to be on 115 forever. I am an engineer so I can provide advanced support to a Firefox dev, just not development as firefox is gargantuan beast of a code base.

Any guidance or pointers would be appreciated, Thanks!

Reposting from https://discourse.mozilla.org/t/firefox-upgrade-from-115-116-results-in-broken-screen-capture/121964 Howdy folks! I am on Arch Linux and recently upgraded Firefox from 115 to 116 and this broke WebRTC screen capture. Whenever I try to share my screen in Microsoft teams and Google Meet, the participants only see a black screen with a cursor. I am able to reproduce the issue on this test page. I had to downgrade to 115 in order to “fix” this critical feature. Before that it was broken in 114 and I had to use Chromium for presentations. I no longer want to touch Chrome with a 100 ft pole since they are trying to introduce Web Environment Integrity. The only bug I have been able to find is from three years ago: https://bugzilla.mozilla.org/show_bug.cgi?id=1640771 I don’t want to add a “me too” comment, but was wondering how to show/give my support to get this issue fixed? It is crippling to my work workflow, and I don’t want to be on 115 forever. I am an engineer so I can provide advanced support to a Firefox dev, just not development as firefox is gargantuan beast of a code base. Any guidance or pointers would be appreciated, Thanks!

Ausgewählte Lösung

Sharing the tab or screen with the test page works for me on Ubuntu 23.04 (Wayland).

Check for errors in the Browser Console (Ctrl+Shift+J).

Does it still happen in a new profile? An easy way to test a new profile is to install Developer Edition and see if it happens there or refresh your existing profile.

Diese Antwort im Kontext lesen 👍 1

Alle Antworten (4)

more options
more options

This test fails for you? see screenshot Did you try Firefox in Safe Mode? https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode#search104

Try downloading Firefox from Mozilla, run firefox-bin from the folder and see if you have the same issue. https://www.mozilla.org/en-US/firefox/all/#product-desktop-release

What Desktop? X11 or Wayland?

more options

Ausgewählte Lösung

Sharing the tab or screen with the test page works for me on Ubuntu 23.04 (Wayland).

Check for errors in the Browser Console (Ctrl+Shift+J).

Does it still happen in a new profile? An easy way to test a new profile is to install Developer Edition and see if it happens there or refresh your existing profile.

more options

Hey thanks all for the interest, but the issue is fixed.

So last week when I hit the issue, I downgraded to Firefox 115, but unfortunately Firefox did not like that and forced me to create a new profile. So today when I went to go and get proof of the breakage using this new profile on 116, the screen capture is now working.

Not sure how a new profile solved the issue, but that seems to be the case.

I am on Nvidia driver with Wayland.

Everything is good now, so marking solved.

Thanks again for the help all!