Basically the title.
With Firefox supporting VAAPI on Wayland and quite a few news on the Ozone advancements and the short enablement of Wayland support on Chromium last months this seems … close?
AFAIK Chromium as of todays Fedora package does not support VAAPI on Wayland due to XWayland.
Answer: We are two releases away from Ozone/Wayland enabled by default in upstream (Chrome 87). See 1759408 – Enable ozone (wayland/x11) in chromium to improve hardware acceleration for further tracking.
Great! I installed Chrome Dev (v87) now. A bit iffy so far, getting a plethora of hard to google errors, but after trying various stuff I managed to at least get it to run with
google-chrome-unstable --enable-features=UseOzonePlatform --ozone-platform=wayland --disable-gpu --disable-software-rasterizer
Disabling GPU is obviously bad, but I’m using it as a second browser for testing web dev stuff, and I use Wayland fractional scaling, which makes regular Chrome/ium unusable to me, so it’s an ever so slight improvement, at least.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.