GTK4 crash with install libvulkan-intel

English Hardware
1

Since the last update of tumblewee to libvulkan_intel (25.3.0-1.1) GTK4 Apps like gnome-text-editor crashes… I have to uninstall libvulkan_intel…
Framework 12 with Intel GPU

MESA-INTEL: warning: …/src/intel/vulkan/anv_formats.c:993: FINISHME: support more multi-planar formats with DRM modifiers
MESA-INTEL: warning: …/src/intel/vulkan/anv_formats.c:959: FINISHME: support YUV colorspace with DRM format modifiers

(gnome-text-editor:24956): Gdk-WARNING **: 22:36:27.428: Vulkan: …/src/intel/vulkan/i915/anv_device.c:349: GPU hung on one of our command buffers (VK_ERROR_DEVICE_LOST)

(gnome-text-editor:24956): Gdk-WARNING **: 22:36:27.428: vkQueuePresentKHR(): The logical or physical device has been lost. (VK_ERROR_DEVICE_LOST) (-4)

2

@Nasendackel Hi, Not seeing that here I have an older intel gpu CometLake 630 and Intel Arc A380 but that’s running the Xe driver and vulkan is switched to the nvidia GPU.

Can you paste the output of inxi -GSaz

3

Thanks for your fast answer :slight_smile:

System:
  Kernel: 6.17.8-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
     clocksource: tsc avail: acpi_pm
     parameters: BOOT_IMAGE=/boot/vmlinuz-6.17.8-1-default
     root=/dev/mapper/system-root splash=silent loglevel=0 quiet
     security=selinux selinux=1 mitigations=auto
  Desktop: niri v: N/A with: waybar tools: swayidle avail: swaylock vt: 2
    dm: GDM v: 49.1 Distro: openSUSE Tumbleweed 20251119
  Graphics:
   Device-1: Intel Raptor Lake-P [UHD Graphics] vendor: Framework driver: i915
     v: kernel alternate: xe arch: Xe process: Intel 10nm built: 2020-21 ports:
     active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4 bus-ID: 00:02.0
     chip-ID: 8086:a721 class-ID: 0300
   Device-2: Framework Laptop 12 Webcam Module driver: uvcvideo type: USB
     rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-7:3 chip-ID: 32ac:001d
     class-ID: fe01 serial: <filter>
   Display: wayland server: Xwayland v: 24.1.8 compositor: niri driver: X:
     loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: 1
   Monitor-1: eDP-1 model: BOE Display NV122WUM-N42 built: 2024
     res: 1920x1200 dpi: 185 gamma: 1.2 size: 263x164mm (10.35x6.46")
     diag: 310mm (12.2") ratio: 16:10 modes: 1920x1200
   API: OpenGL v: 4.6 vendor: intel mesa v: 25.3.0 glx-v: 1.4 es-v: 3.2
     direct-render: yes renderer: Mesa Intel Graphics (RPL-U)
     device-ID: 8086:a721 memory: 45.68 GiB unified: yes
   API: Vulkan v: 1.4.328 layers: 5 device: 0 type: integrated-gpu
     name: Intel Graphics (RPL-U) driver: mesa intel v: 25.3.0
     device-ID: 8086:a721 surfaces: N/A device: 1 type: cpu name: llvmpipe
     (LLVM 21.1.5 256 bits) driver: mesa llvmpipe v: 25.3.0 (LLVM 21.1.5)
     device-ID: 10005:0000 surfaces: N/A
   API: EGL Message: EGL data requires eglinfo. Check --recommends.
   Info: Tools: api: glxinfo,vulkaninfo x11: xprop,xrandr
4

Maybe related

5

Please, next time use the Preformatted text button </> at the right of the Quote button " for your computer output.

1 Like
6

Something similar here with older Intel graphics (not necessarily related to Raptor Lake though).

7

@jsulig Hi, so your running Niri, which if like Hyprland has config options for the environment. I would suggest looking at those setting for perhaps a config option.

eg I have the likes of;

env = GDK_BACKEND,wayland
env = SDL_VIDEODRIVER,wayland
env = CLUTTER_BACKEND,wayland

I’m not sure if (since it’s a newer Intel GPU) switching to the Xe driver may help? T do this as root user run;

update-bootloader --add-option i915.force_probe=\!a721
update-bootloader --add-option xe.force_probe=a721
update-bootloader

Reboot and check it’s switched to Xe from i915, to revert just run above with --del-option instead of --add-option

Consider adding intel_iommu=on as well to your boot options, likewise check system security with fwupdmgr security

8

Will do :slight_smile:

9

Yes! Thanks … Setting GSK_RENDERER to gl solved the problem. This a a fix, but there seems to be a problem with mesa 25.3.0 and GTK4

10

Thanks … adding the bootloader made it worse… but switching gsk to gl worked

11

So, like in the thread I linked above, Vulkan on Intel GPU is not working. Apparently something wrong with the update to Mesa-drivers (25.2.7 → 25.3.0) in snapshot 20251118.
A bug report might be needed.

PS: maybe vulkaninforeturns something interesting.

12

Hi, affects my Rog Strix with Intel Raptor Lake-S UHD, too. Thanks for workaround.
Bug report filled there: 1254121 – GTK4 applications glitches and crash at Mesa 25.3.0

13

I’m using GNOME. What should I do to get around this issue?

14

@kryzet create a /etc/environment file and add GSK_RENDERER=gl to the file and reboot…

15

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.