[snap] Chromium has Wayland support disabled
Bug #1897454 reported by
Jasiek Marcinkowski
This bug affects 14 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
Fix Released
|
Medium
|
Olivier Tilloy |
Bug Description
Since v87 Chromium ships with support for Ozone/Wayland:
https:/
This build flag is not disabled in dev (edge) channel build, so it should be possible to run Chromium with flags
--enable-
This does not work due to environment variable DISABLE_WAYLAND set to 1 here:
https:/
tags: | added: snap |
summary: |
- Chromium Dev Snap cuts off Wayland display + [snap] Chromium dev cuts off Wayland display |
Changed in chromium-browser (Ubuntu): | |
importance: | Medium → Low |
summary: |
- [snap] Chromium dev cuts off Wayland display + [snap] Chromium has Wayland support disabled |
tags: | added: wayland wayland-session |
Changed in chromium-browser (Ubuntu): | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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= UseOzonePlatfor m --ozone- platform= wayland 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 0928/181748. 000370: ERROR:viz_ main_impl. cc(150) ] Exiting GPU process due to errors during initialization
[5042:5042:
[5042:5042:
(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.