[Snap] Crashes when starting screenshare on meet.jit.si with MOZ_ENABLE_WAYLAND
Categories
(Core :: WebRTC: Audio/Video, defect, P3)
Tracking
()
People
(Reporter: launchpad, Unassigned)
References
(Blocks 3 open bugs)
Details
Crash Data
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:107.0) Gecko/20100101 Firefox/107.0
Steps to reproduce:
- use Ubuntu 22.04, with a Gnome Wayland session, Firefox 107 (but I know at least the last version also didn't work, it's been crashing for a couple of months)
- Visit https://meet.jit.si/firefoxCrashesOnScreenshare and 'join' the meeting.
- click the screenshare button
- select "Use operating system" (I think this is pipewire, right?)
- select a window to share
Actual results:
Firefox crashes.
Expected results:
Firefox doesn't crash, but enables me to screenshare the selected window.
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Updated•2 years ago
|
Comment 2•2 years ago
|
||
Could you check about:crashes and see if this crash was reported?
I did report it that way, yes. it's this: https://crash-stats.mozilla.org/report/index/9b70288d-6594-4e26-93fb-a13700221109
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 4•2 years ago
|
||
There has got to be a better way to set the signature for this family of crashes...
Comment 5•2 years ago
|
||
The bug has a crash signature, thus the bug will be considered confirmed.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 6•2 years ago
|
||
I'm seeing the same symptoms (running the 108.0b5 snap on Ubuntu 22.10), but not the same crash signature: https://crash-stats.mozilla.org/report/index/ef817804-199e-430a-901b-6fa320221123.
Updated•2 years ago
|
Comment 7•2 years ago
|
||
Looks like a duplicate of bug 1790496.
Updated•2 years ago
|
https://bugzilla.mozilla.org/show_bug.cgi?id=1790496
is marked as fixed in Firefox 111 but that's not the whole truth; sure the browser doesn't CRASH, but neither does it share screen... and sometimes it shares the WRONG WINDOW(!)
Running nightly (111.0a1 (2023-01-24) ) with MOZ_ENABLE_WAYLAND=1, and jit.si again,
- I click Screen Share.
- A permissions dialog pops up, "Allow meet.jit.si to see your screen?", with "Select window or screen" showing in the select box. The only option in the select is Entire Screen (aside: why is the only option not selected automatically?). I select that.
- The first time I did this, I then got another redundant pop-up (pipewire?) saying what do I want to share - but with only Entire screen available to choose. I said Yes.
- the site now thinks it's screensharing, but all it's sharing is a blank black rectangle - both seen in the browser and by others in the meeting.
Running nightly with MOZ_ENABLE_WAYLAND= (i.e. No/without it) and jit.si again
- I click Screen Share
- Permissions dialog pops up "Allow..." as before, but this time there are options: entire screen or the firefox window itself (but no others).
- The pipewire(?) dialog pops up. If in (2) I selected the firefox window itself, then I'm now offered a choice of all my windows; if in (2) I selected entire screen, I'm offered a choice of screens (I only have one).
- picking an option from the pipewire dialog and the app now says I'm sharing, but all is blank. BUT now, immediately after it closed, the pipewire dialog opens again! Selecting the same option a 2nd time and something starts sharing...
- If I selected a window, that starts sharing, after a final confirmation.
- If I selected Entire Screen, then the confirmation dialog shows (thumbnail) the entire screen will be shared - great- but confirming and then it shows a single window - seems to be the last window I shared.
The last bit is a security risk - if I had shared something confidential, then minimised that and intended to share my screen a 2nd time I could expose the previous window to a potentially new person.
Description
•