This should be fixed with https://git.launchpad.net/~chromium-
team/chromium-browser/+git/snap-from-
source/commit/?id=a4f41b5c065e14e954bc81d2d3e2b0c7fc26fc4d.
With the next builds that pick up this change, chromium will still
default to XWayland, but users can change this setting at
chrome://flags/#ozone-platform-hint to try out native Wayland support.
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: chromium-browser (Ubuntu)
Importance: Low => 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 has Wayland support disabled
Status in chromium-browser package in Ubuntu:
Fix Committed
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
