Gnome-shell getting killed with no coredump, artifacting with workaround fix 🤧

No, both my displays are around 140 DPI as per this calculator, the secondary machine’s built-in monitor is 1080p (15.6") and the primary’s external monitor is 4k (32").

Looks like

Minor rendering issues (#7154) · Issues · GNOME / gtk · GitLab and/or Rendering artefacts (#7076) · Issues · GNOME / gtk · GitLab (which I assume have the same underlying issue)

Ah, looks like this is a known issue. Any workaround by changing the font settings, for example?

Current font config

If the comments from Rendering artefacts (#7076) · Issues · GNOME / gtk · GitLab are correct, using a different font or font size or scaling factor might help avoid this for some situations or it might start breaking in others.

1 Like

Thanks, it’s working okay with scaling factor set to 1.05. Some small artifacts in Nautilus though, so it’s definitely a trade off.

I encountered a similar problem. Gnome been killed because of RT timeout. Turning off RT or increasing rttime rlimit solve the problem, but I am not sure whether it is related to fullscreen window. I frequently encounter this when using the browser normally or do any complex job.
Not connecting an external monitor seems to alleviate the problem.

And the problem completely disappeared after upgrading to Linux 6.11.

1 Like

I had artifacts in otherwise OK apps with scaling set to 1.05, so reverted back to normal font scaling.

Hope someone can fix this in Gnome 48 :pleading_face: