Override GDK_BACKEND in GTK initialization
GDK_BACKEND gets set by chrome-remote-desktop [1]. GDK_BACKEND takes precedence over gdk_set_allowed_backends() [2], so this means weston sessions (which inherit GDK_BACKEND) will incorrectly try to use X11, which won't work. To avoid this, manually set GDK_BACKEND during GTK initialization. [1] https://source.chromium.org/chromium/chromium/src/+/master:remoting/host/linux/linux_me2me_host.py;drc=be48a068a67faa7f3bc2ea0d03529d62319f06fb;l=461 [2] https://gitlab.gnome.org/GNOME/gtk/blob/3.24.5/gdk/gdkdisplaymanager.c#L441 BUG=None R=nickdiego Change-Id: I5ae6cae1511e4a7215098a0c291d735303a1827f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2586184 Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Commit-Queue: Nick Yamane <nickdiego@igalia.com> Auto-Submit: Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:Nick Yamane <nickdiego@igalia.com> Cr-Commit-Position: refs/heads/master@{#835870}
Showing
Please register or sign in to comment