I unpacked the snap from the dev channel, remove the DISABLE_WAYLAND
definition, added the wayland plug, but the application still fails to
display a window:

ubuntu@groovyvm:~$ chromium --enable-features=UseOzonePlatform 
--ozone-platform=wayland
[5042:5042:0928/181747.909095:ERROR:egl_util.cc(70)] Failed to load GLES 
library: libGLESv2.so.2: libGLESv2.so.2: cannot open shared object file: No 
such file or directory
[5042:5042:0928/181748.000370:ERROR:viz_main_impl.cc(150)] Exiting GPU process 
due to errors during initialization

(chrome:4835): dbind-WARNING **: 18:17:48.525: Could not open X display


This requires more investigation and work.

Also, that phoronix news states that it's unlikely to ship soon in the
stable builds.

** Changed in: chromium-browser (Ubuntu)
       Status: New => Confirmed

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1897454

Title:
  [snap] Chromium dev cuts off Wayland display

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Since v87 Chromium ships with support for Ozone/Wayland:
  https://www.phoronix.com/scan.php?page=news_item&px=Chrome-87-Ozone-Try-Again.

  This build flag is not disabled in dev (edge) channel build, so it should be 
possible to run Chromium with flags
    --enable-features=UseOzonePlatform --ozone-platform=wayland.

  This does not work due to environment variable DISABLE_WAYLAND set to 1 here:
  
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/snapcraft.yaml?h=dev#n18.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897454/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to