The latest chromium security update now renders many pages with annoying visual artefacts - lwn.net, salsa.debian.org, gmail.com -- mainly when using (moving or clicking) the mouse i tried downgrading to 135.0.7049.95-1~deb12u1 but that version then refused to start (i suppose some setttings are incompatible) . do i need to do something else to make the downgrade work? i note my android phone has a lower version, 137, which seems to be in stable-proposed-updates , so maybe 138 is a bad version? (if you want to know what graphics card is used the please let me know how to find that out - i expect it is intel of some kind. arch is amd64) thank-you for maintaining chromium, it normally works great!
Hi, Thanks for the report. In general it's helpful to know if you're running wayland or X, and your desktop environment. 138 does seem a bit buggier than 137, and so far they haven't really backported many fixes from 139. I'll keep an eye on this. There's a bug with Skia Graphite enabled that might be what you're seeing: https://issues.chromium.org/issues/428802472 Going to chrome://gpu will tell you if Skia Graphite is enabled or not. On my end it is disabled, and I don't see any artifacts. If it is enabled, please try --disable-skia-graphite and report back. Thanks, Andres
i am using gnome with the default (i think that is wayland? following instructions on the internet I did loginctl -p Type show-session <id> and it says Type=wayland ) Graphics Feature Status Canvas: Hardware accelerated Direct Rendering Display Compositor: Disabled Compositing: Hardware accelerated Multiple Raster Threads: Disabled OpenGL: Enabled Rasterization: Hardware accelerated on all pages Raw Draw: Disabled Skia Graphite: Disabled TreesInViz: Disabled Video Decode: Hardware accelerated Video Encode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated WebGPU: Disabled WebNN: Disabled it didnt help, but i see a lot of ERROR:ui/gl/gl_surface_presentation_helper.cc:260] GetVSyncParametersIfAvailable() failed for 1 times! which led me to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901831 which suggested --use-gl=osmesa which seems to fix it. It feels a bit slower, but at least i can see things again!
Hi, Can you let me know if you're still seeing this issue with chromium 140? Thanks, Andres On Tue, 1 Jul 2025 20:45:30 +0100 Richard Lewis <richard.lewis.debian@googlemail.com> wrote:
Thanks for the reminder - i didnt check any earlier versions, but this is indeed fixed with 140.0.7339.127-1~deb13u1