Even in Chrome where Wayland does seem to work (manually), it warns that
gnome-shell/mutter is missing zwp_linux_explicit_synchronization_v1. I
wonder if that explains the laggy feeling?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Alberto, please note that the snap already has libEGL.so and
libGLESv2.so, they live in /snap/chromium/current/usr/lib/chromium-
browser/.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
** Changed in: chromium-browser (Ubuntu)
Importance: Medium => Low
--
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
I did a quick test by unpacking the current stable snap (87.0.4280.88,
rev. 1421)
After removing DISABLE_WAYLAND, adding wayland plug, I copied missing
/usr/lib/x86_64-linux-gnu/libEGL* and /usr/lib/x86_64-linux-
gnu/libGLESv2* to the unpacked snap.
I now get the following errors:
Good point. I did not go that far.
I can only attest that it should work when packaged correctly. This
comment is being written from (Google branded) Chrome Unstable with
these flags and it runs pure Wayland.
--
You received this bug notification because you are a member of Desktop
Packages,
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
** Summary changed:
- Chromium Dev Snap cuts off Wayland display
+ [snap] Chromium dev cuts off Wayland display
--
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:
7 matches
Mail list logo
