Happy to hear that!
Would you mind confirming if the log from 3 no longer has references to
crashed GPU process? Because if it still does, then I know for future
debugging that that could be a red herring.
** Changed in: chromium-browser (Ubuntu)
Status: New => Fix Released
--
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/2055040
Title:
Software rendering under Wayland mode
Status in chromium-browser package in Ubuntu:
Fix Released
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+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
