Wayland support, GTK3 support.
Reported by
dmitriyh...@gmail.com,
May 26 2016
|
|||||
Issue description
Chrome Version : 52.0.2723.2 (Developer Build) (64-bit) GTK3
URLs (if applicable) :
Other browsers tested: firefox
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari: FAIL
Firefox: FAIL
IE: FAIL
What steps will reproduce the problem?
(1) Compile Chromium with GTK3 on any distro (Arch/Fedora/Gentoo/LFS)
(2) Try to run it under wayland-environment
What is the expected result?
Full support for GTK3 and Wayland, perfect work without 32-bit libs.
What happens instead?
It doesn't works.
Please provide any additional information below. Attach a screenshot if
possible.
I compile Chromium with GTK3 on Gentoo nomultilib, it doesn't even launch, even with xwayland it crush from any key pressing.
Under X-server it works.
,
May 27 2016
dmitriyhetman@Could you please respond to comment #1?
,
May 27 2016
No, it's rather about Wayland support, Chromium GTK3 under Xorg-server works good, but not work with wayland (Weston)
,
May 27 2016
Thank you for providing more feedback. Adding requester "ssamanoori@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 31 2016
,
Jun 21 2016
XWayland support needs to added to the GTK3 side of things for this to work. If you run `xlsclients`(command to list apps using XWayland) from the terminal it won't show Chromium. An easy fix for the moment is to start Chromium like so: `GDK_BACKEND=x11 chromium` The GTK3 build has never worked in the Wayland environment (however the GTK2 version has always worked)
,
Oct 7 2016
You can specify supported GDK backends within the code when initialising, Chromium really should do this since otherwise GTK3 (rightly) assumes the application supports Wayland natively since anything else is a bug. Either blacklist backends or support them. Of course even better would be to fix Chromium to work with Wayland natively, is there a plan for this? The Ozone-Wayland code works great within its scope; that is for embedded browsers. Is it possible to have a statement of intention, will the full desktop UX/(GTK?) be ported to Ozone, or will Wayland be supported within the GTK3 build? This is especially pertinent given the upcoming Fedora release is defaulting to gnome-wayland out of the box.
,
Nov 7 2016
GNOME 3.22.x now by default starts on Wayland. Is there plans to address this?
,
Nov 8 2016
@kgizdov Both GTK3 and Wayland are actively being worked on. GTK3 bugs: 132847 79722 Wayland bugs: 295089 Please take your stars to those bugs instead. Unfortunately since this issue is really 2 in 1, it wouldn't make sense to merge, so closing this out. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by thestig@chromium.org
, May 26 2016