Open Bug 1629319 Opened 5 years ago Updated 2 years ago

[WAYLAND] Screen sharing will cause firefox to crash

Categories

(Core :: WebRTC: Audio/Video, defect, P3)

75 Branch
defect

Tracking

()

UNCONFIRMED

People

(Reporter: mozilla-bugzilla, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0

Steps to reproduce:

Run Firefox in flatpak, override permissions to run on wayland only:

  1. Install firefox | flaptak install flathub org.mozilla.firefox
  2. Override Firefox to run in wayland only mode | flatpak --user override --socket=wayland --nosocket=x11 --env=MOZ_ENABLE_WAYLAND=1 org.mozilla.firefox
  3. Run firefox as usual | flatpak run org.mozilla.firefox
  4. Share screen in any tool, for example https://meet.jit.si

Actual results:

Firefox crashes as soon as it tries to access the screen/screen-sharing-permission.

While the rest of browsing works perfectly fine.

Expected results:

Showing an error or simply have working screen sharing on wayland. But definitely not straight crash the entire browser.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core

Resetting severity to default of --.

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Severity: normal → --

We don't currently build Firefox with support for Wayland screensharing. This is a build system limitation (see Bug 1430775). Once we get that fixed, this is something we'll want to investigate. I'm not sure why you're seeing a crash, Bug 1430775 seems to indicate that there is no crash, just a black screen. But I don't have a system with which to investigate this, so I'll have to leave it unconfirmed.

Severity: -- → S3
Component: Widget: Gtk → WebRTC: Audio/Video
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.