Closed Bug 1431399 Opened 5 years ago Closed 4 years ago

[Wayland] with WebRTC playback device sharing indicator is not shown

Categories

(Core :: Widget: Gtk, defect, P3)

defect

Tracking

()

RESOLVED FIXED
mozilla67
Tracking Status
firefox59 --- wontfix
firefox67 --- fixed

People

(Reporter: stransky, Assigned: stransky)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Firefox on wayland crashes when I open the following site with an USB camera:

https://webrtc.github.io/samples/src/content/getusermedia/gum/

WebRTC playback device sharing indicator is not shown.
> Firefox on wayland crashes when I open the following site with an USB camera:
> 
> https://webrtc.github.io/samples/src/content/getusermedia/gum/

It works on my environment without crash.

Camera: Logitech C910

$ hg id -i
3cfc35010196

$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS"

$ env | grep -e XDG_CURRENT_DESKTOP -e DISPLAY
WAYLAND_DISPLAY=wayland-0
XDG_CURRENT_DESKTOP=ubuntu:GNOME

But the indicator isn't shown yet:

Gdk-Message: 15:59:45.814: Window 0x7f599f102500 is a temporary window without parent, application will not be able to position it on screen.
Gdk-Message: 15:59:45.814: Window 0x7f599f102500 is a temporary window without parent, application will not be able to position it on screen.
It works fine for me with trunk & Fedora 28, even the indicator is shown.

eWindowType_child window (a window defined by GdkWindow only) is not supported on Wayland
as we need moz_container to provide wl_surface to draw into.

As a workaroud create a regular toplevel window instead of child on Wayland to enable
rendering and window manipulation.

Pushed by ccoroiu@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d7348960f8da
[Wayland] Render eWindowType_child as a toplevel window on Wayland, r=ashie

Keywords: checkin-needed
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
QA Whiteboard: [qa-67b-p2]
You need to log in before you can comment on or make changes to this bug.