GNOME 48 graphics issues (mesa)

Desktop
1

I don’t know if this issue is the distro’s fault, but I’m gonna explain the issue I’m having.

I’m using Fedora Workstation 42, which comes with GNOME 48 by default, in previous Fedora 41 version, I was always having this error messages in the terminal, but all apps opened without any problems:

MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete
MESA-INTEL: warning: ../src/intel/vulkan_hasvk/anv_formats.c:752: FINISHME: support YUV colorspace with DRM format modifiers
MESA-INTEL: warning: ../src/intel/vulkan_hasvk/anv_formats.c:783: FINISHME: support more multi-planar formats with DRM modifiers

But in this new version, the same message appears, but when I try to use a GTK-based app, I get the following screens (I opened GNOME calculator):

imagen
imagen1366×768 112 KB

I can open the Activities menu and the upper right menu, etc.

I fixed this problem by creating a new profile system-wide script with the following contents:

#!/bin/bash

# in /etc/profile.d/rendering-fix.sh

export GSK_RENDERER=gl

System Details Report

Report details

  • Date generated: 2025-06-07 13:12:46

Hardware Information:

  • Hardware Model: VIT VIT P2400
  • Memory: 4.0 GiB
  • Processor: Intel® Core™ i3-3110M × 4
  • Graphics: Intel® HD Graphics 4000 (IVB GT2)
  • Disk Capacity: 240.1 GB

Software Information:

  • Firmware Version: E1485IIA.20G
  • OS Name: Fedora Linux 42 (Workstation Edition)
  • OS Build: (null)
  • OS Type: 64-bit
  • GNOME Version: 48
  • Windowing System: Wayland
  • Kernel Version: Linux 6.14.9-300.fc42.x86_64
2

I think in previous versions GTK-based apps were falling back to OpenGL rendering if the system didn’t support Vulkan.

But somehow this feature was removed.

This only affects GTK-based apps, since Firefox opened without any problems (before writing that fix script)

1 Like
3

This is a bug in the latest mesa release:

3 Likes
4

Then Fedora 41 surely must have used an older mesa version.

Thank you for responding!

1 Like
5

I do have the issue in Mesa Version: 25.0.7, way before the version in that Git issue :thinking:

6

Mesa 25.0.7 was just released last week, but doesn’t contain the referenced commit, which has since been reverted.

Saw this recently on Arch Forums

Looks like the fix may be in vulkan-intel 25.1.3 rather…

Not sure how Fedora rolls, but guessing a packaging backport or 25.0.8 upstream release.

7

Mesa 25.0.7 contains that commit:

1 Like
8

Ah, under “Tags containing this commit”… separate for the 25.0.x and 25.1.x branches.

I was looking at:

So this still is the case…

9

I’m now seeing this issue with flatpak apps. (I’m running Fedora Silverblue 42, and I previously had this issue with non-flatpak apps, but an update to Silverblue has fixed it.) This is on a Lenovo ThinkPad X230 with Intel® HD Graphics 4000 (IVB GT2).

I think it only affects apps that use the GNOME 48 runtime (for example Text Editor from Flathub) — though every other app I have either uses an out-of-date runtime (GNOME 46) or doesn’t use GTK4.

I’ve tried rolling back org.gnome.Platform//48, org.freedesktop.Platform.GL.default//24.08 and org.freedesktop.Platform//24.08 to versions from May 2025, but I still see the bug.

To do this I ran, for example, flatpak remote-info --log flathub org.freedesktop.Platform//24.08; found the commit hash 69f5ca3180618e77eb1264af2b67048fc1c6a2884ee403c76b24b0e15bfc16c9; and then ran sudo flatpak update --commit=69f5ca3180618e77eb1264af2b67048fc1c6a2884ee403c76b24b0e15bfc16c9 org.freedesktop.Platform//24.08

Is there another flatpak runtime I need to roll back to escape this bug until a fix is released?

10

Well it looks like it’s fixed this morning. flatpak history shows an update for org.freedesktop.Platform.VAAPI.Intel, and all previously-affected apps now work fine.

1 Like