Or as Olivier mentioned... chrome://flags/#ozone-platform-hint
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897454
Title:
[snap] Chromium has Wayland support disabled
To manage notifications
Now you can enable Wayland in chrome://flags with
Preferred Ozone platform = Wayland
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897454
Title:
[snap] Chromium has Wayland support disabled
To
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897454
Title:
[snap] Chromium has Wayland support disabled
To
@copong Wayland for Chromium is definitely still experimental, but is
under active development, helped because ChromeOS is/will use it.
I'd suggest you compare with an upstream build: https://download-
chromium.appspot.com/
Just download, unpack and run the chromium binary. Since the snap's
It feels pretty sluggish to use. Not sure if it's a packaging issue or
chromium issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897454
Title:
[snap] Chromium has Wayland support disabled
To
It works for me on 102.0.5005.40 (latest/beta channel) but with the
following GPU error messages:
```
[2005781:2005781:0506/130903.210912:ERROR:gpu_init.cc(481)] Passthrough is not
supported, GL is egl, ANGLE is
WARNING: Kernel has no file descriptor comparison support: Operation not
permitted
I can confirm wayland works for the version 102.0.5005.40 snap just
built and released in the beta channel. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897454
Title:
[snap] Chromium has
** Tags added: wayland wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897454
Title:
[snap] Chromium has Wayland support disabled
To manage notifications about this bug go to:
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
This still fails with Chromium 100.0.4896.127 (snap 1967) on 22.04:
$ chromium --enable-features=UseOzonePlatform --ozone-platform=wayland
[261783:261783:0425/123646.322058:ERROR:wayland_connection.cc(209)] Failed to
connect to Wayland display
You could test an upstream build of Chromium: https://download-
chromium.appspot.com/
Since this version is unconfined, it doesn't share config data with the
snap, so it's safe to use alongside the snap for testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Forgot to add. Chromium is from the edge channel, at version
101.0.4919.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897454
Title:
[snap] Chromium has Wayland support disabled
To manage
It still fails to start (sway 1.7):
~ chromium --enable-features=UseOzonePlatform --ozone-platform=wayland
[278662:278662:0310/100635.924517:ERROR:wayland_connection.cc(209)] Failed to
connect to Wayland display
[278662:278662:0310/100635.924552:ERROR:ozone_platform_wayland.cc(226)] Failed
to
Before assuming that enabling Wayland would fix the screen sharing
issues, please verify that it actually does:
chromium --enable-features=UseOzonePlatform --ozone-platform=wayland
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The priority of this bug is Low but since Wayland is now the default
session this means chromium runs via XWayland and then when doing
window/screen sharing on say Google Meet I can only share windows which
are also using XWayland, not native ones - which is the majority of the
rest of the
** Summary changed:
- [snap] Chromium dev cuts off Wayland display
+ [snap] Chromium has Wayland support disabled
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897454
Title:
[snap] Chromium has
16 matches
Mail list logo
