Thanks for clarifying.
> If I launch Chromium with the --ozone-platform-hint=wayland or
--ozone-platform-hint=auto (as specified in the snap's starter script)
1. Just to confirm, this means that if you just launch the Chromium snap
normally, the described behavior happens? Because, as you pointed out,
--ozone-platform-hint=auto is a default flag in the launcher, so passing
it via command line shouldn't affect the observed behavior.
2. Is the issue something new or was it this way ever since you started
using the edge Chromium snap?
3. Can you attach the log generated from running 'chromium --enable-
logging=stderr --v=1 2&>1 >chr.log'?
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => New
** Tags added: kivu
** Description changed:
- Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium with the
- --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as
+ Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium (edge channel)
+ with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as
specified in the snap's starter script), the browser always ends up into
slow SW rendering.
When omitting the parameter or setting it to "X11", HW rendering gets
correctly detected and activated.
The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics
620 chip running Mesa 23.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055040
Title:
Software rendering under Wayland mode
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
