Firefox/Zen-Browser (Gecko) crashing with Kernel 7.1.8

Hi,

I updated TW, yesterday. Since then, Gecko-based browsers (Firefox, Zen Browser) have been crashing whenever a YouTube video is embedded on a webpage. This happens on some sites (e.g., Moodle), though not on Heise.de. I’m not sure, but I think I noticed the mouse stuttering a bit too.

I have reverted the system to kernel 7.1.6.

System info:
ASUS Zenbook UX3405
Graphics card: Intel ARC
openSUSE VERSION_ID=“20260812”

> inxi -Gz                                                                                                                                                                                                           ~@ZenbookOpenSUSE
Graphics:
  Device-1: Intel Meteor Lake-P [Intel Arc Graphics] driver: i915 v: kernel
  Device-2: Shinetech USB2.0 FHD UVC WebCam driver: uvcvideo type: USB
  Display: wayland server: X.org v: 1.21.1.24 with: Xwayland v: 24.1.13
    compositor: kwin_wayland driver: X: loaded: modesetting unloaded: vesa
    dri: iris gpu: i915 resolution: 2880x1800~120Hz
  API: EGL v: 1.5 drivers: iris,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6 vendor: intel mesa v: 26.1.6 renderer: Mesa Intel Arc
    Graphics (MTL)
  API: Vulkan v: 1.4.357 drivers: intel,llvmpipe surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: gputop, intel_gpu_top, lsgpu
    wl: wayland-info x11: xdpyinfo, xprop, xrandr

Best regards
Kay

I just updated an N100 system, so also VERSION_ID=“20260812”, but no issues with 6.18 kernel at moodle.com. But I might see a different moodle.com then you, as websites are personalized (and I have ad-blocker and maybe other differences w.r.t. internet).
I would say clean caches, maybe something went wrong during install, then re-install maybe. I had once that that solved an issues, but crashes are rare in my experience. If so, maybe start with the program with strace, look at coredumps, but it seems difficult for such big software as firefox is.
You might also need to list and/or look at extra codec packages, if you have those installed from 3rd-party repo etc. YT can serve different files etc even website URL is the same.

This makes me wonder if something is missing. Maybe @malcolmlewis knows, he has Intel Arc

… but issues with heat (35 deg celcius here) in my brain; 7.1.8 it must be
And maybe as some more info about N100:

> inxi -Gz
Graphics:
  Device-1: Intel Alder Lake-N [UHD Graphics] driver: i915 v: kernel
  Display: unspecified server: X.org v: 1.21.1.24 with: Xwayland v: 24.1.13 driver: X:
    loaded: modesetting unloaded: vesa dri: iris gpu: i915 tty: 139x41 resolution: 1920x1080
  API: EGL v: 1.5 drivers: iris,swrast platforms: gbm,surfaceless,device
  API: OpenGL v: 4.6 vendor: mesa v: 26.2.0 note: console (EGL sourced) renderer: Mesa Intel
    Graphics (ADL-N), llvmpipe (LLVM 22.1.8 256 bits)
  API: Vulkan v: 1.4.357 drivers: intel,llvmpipe surfaces: N/A
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
    wl: wayland-info x11: xdpyinfo, xprop, xrandr

I have my own instance of Moodle. Courses with integrated YouTube-Videos make problems. I don’t know which plugin moodle or Gecko use for displaying integrated videos. I tried two different browser. Zen-Browser is my default browser but same problem in Firefox. I don’t think it is a caching-problem. After rollback no problems.

OK, I don’t know anything about Moodle, If a local/own instance, others cannot really reproduce.
Maybe have a look at FireFox about:support internal page at Media and see for what codecs there is HW support. I see at mine: HW decoding support for H264, VP9, VP8, AV1, HEVC. Trend is that YT offers AV1. There was/is an issue w.r.t. that when packman repo is active. Maybe have a look at sudo zypper lr output

But maybe it is totally other issue. When such an issue happens, I try to pinpoint which package by comparing change lists in the Tumbleweed download repo area, it is per snapshot. Maybe a new version of Mesa is the root cause, etc.

@guckuck Make sure the likes of intel-media-driver and libvulkan_intel are installed. I would also suggest ensuring your user is in the video and render groups.

Experiencing the same - 7.1.8 firefox playing youtube videos

Aug 14 firefox[10968]: libva info: VA-API version 1.24.0
Aug 14 firefox[10968]: libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so
Aug 14 firefox[10968]: libva info: Found init function __vaDriverInit_1_24
Aug 14 firefox[10968]: libva info: va_openDriver() returns 0

Aug 14 kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:849f9ffc, in Renderer [10656]
Aug 14 kernel: i915 0000:00:02.0: [drm] GPU error state saved to /sys/class/drm/card1/error
Aug 14 kernel: i915 0000:00:02.0: [drm] Renderer[10656] context reset due to GPU hang
Aug 14 firefox[10151]: [GFX1-]: Detect DeviceReset DeviceResetReason::RESET DeviceResetDetectPlace::WR_POST_UPDATE in Parent process

Aug 14 firefox[37382]: [Child 37382, MediaDecoderStateMachine #8] WARNING: Decoder=7f0edb8e7800 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005): file firefox-153.0.3/dom/media/MediaDecoderStateMachineBase.cpp:168
Aug 14 firefox[37382]: [Child 37382, MediaDecoderStateMachine #8] WARNING: Decoder=7f0edb8e7800 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005): file firefox-153.0.3/dom/media/MediaDecoderStateMachineBase.cpp:168
Aug 14 firefox[37382]: [Child 37382, MediaDecoderStateMachine #8] WARNING: Decoder=7f0edb8e7800 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005): file firefox-153.0.3/dom/media/MediaDecoderStateMachineBase.cpp:168
Aug 14 firefox[37382]: [Child 37382, MediaDecoderStateMachine #8] WARNING: Decoder=7f0edb8e7800 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005): file firefox-153.0.3/dom/media/MediaDecoderStateMachineBase.cpp:168
Aug 14 kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:849f9ffc, in Renderer [10656]
Aug 14 kernel: i915 0000:00:02.0: [drm] Renderer[10656] context reset due to GPU hang
Aug 14 firefox[10151]: [GFX1-]: Detect DeviceReset DeviceResetReason::RESET DeviceResetDetectPlace::WR_POST_UPDATE in Parent process
Aug 14 kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:849fdffb, in Renderer [10656]
Aug 14 kernel: i915 0000:00:02.0: [drm] Renderer[10656] context reset due to GPU hang
Aug 14 firefox[10151]: [GFX1-]: Detect DeviceReset DeviceResetReason::RESET DeviceResetDetectPlace::WR_POST_UPDATE in Parent process
Aug 14 kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:87d7fee8, in firefox [10151]
Aug 14 kernel: i915 0000:00:02.0: [drm] firefox[10151] context reset due to GPU hang
Aug 14 firefox[10151]: [GFX1-]: Detect DeviceReset DeviceResetReason::RESET DeviceResetDetectPlace::WR_POST_UPDATE in Parent process
Aug 14 firefox[10151]: [GFX1-]: Detect DeviceReset DeviceResetReason::RESET DeviceResetDetectPlace::WR_POST_UPDATE in Parent process
Aug 14 firefox[10151]: [GFX1-]: Detect DeviceReset DeviceResetReason::RESET DeviceResetDetectPlace::WR_POST_UPDATE in Parent process
Aug 14 firefox[10151]: [GFX1-]: Detect DeviceReset DeviceResetReason::RESET DeviceResetDetectPlace::WR_POST_UPDATE in Parent process
Aug 14 firefox[10151]: [GFX1-]: Detect DeviceReset DeviceResetReason::RESET DeviceResetDetectPlace::WR_POST_UPDATE in Parent process
Aug 14 firefox[10151]: [GFX1-]: Detect DeviceReset DeviceResetReason::RESET DeviceResetDetectPlace::WR_POST_UPDATE in Parent process
Aug 14 firefox[10151]: [GFX1-]: Detect DeviceReset DeviceResetReason::RESET DeviceResetDetectPlace::WR_POST_UPDATE in Parent process
Aug 14 firefox[10151]: [GFX1-]: Detect DeviceReset DeviceResetReason::RESET DeviceResetDetectPlace::WR_POST_UPDATE in Parent process
Aug 14 firefox[10151]: [GFX1-]: In-process device reset threshold exceeded
Aug 14 firefox[10151]: [GFX1-]: Fallback WR to SW-WR

No issues seen (no drm errors) here with google-chrome, Intel 630 (Hyprland) and Intel ARC A380 (GNOME) both on 20260813.

Is your user a member of the render group, since that’s what the error is about…

Not a kernel issue, had to go back to a snapshot that still had Mesa 26.1.6 .

I don’t see how a GPU HANG and dump relates to permissions

Your running SELinux? If so check for errors there…

@mburge please also show the output from inxi -GSaz then -G is not verbose enough.

I’m not the OP, but here they are

I already downgraded to Mesa 26.1.6 but using the snapshot just before that can still repro

❯ inxi -GSaz
System:
  Kernel: 7.1.8-1-default arch: x86_64 bits: 64 compiler: gcc v: 16.2.0
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-7.1.8-1-default
    root=UUID=99a5af1a-9348-4e4e-9c42-e64cbf5e1710
    rootflags=subvol=/@/.snapshots/1134/snapshot splash=silent quiet
    security=apparmor rd.driver.blacklist=nouveau
    rd.driver.blacklist=nova-core intel_iommu=on mitigations=auto
  Desktop: KDE Plasma v: 6.7.4 tk: Qt v: N/A info: frameworks v: 6.28.0
    wm: kwin_wayland tools: avail: xscreensaver vt: 2 dm: 1: GDM v: 50.2
    2: LightDM v: 1.32.0 note: stopped 3: SDDM note: stopped Distro: openSUSE
    Tumbleweed 20260813
Graphics:
  Device-1: Intel Raptor Lake-S UHD Graphics vendor: Lenovo driver: i915
    v: kernel alternate: xe arch: Xe process: Intel 10nm built: 2020-21 ports:
    active: eDP-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:a788
    class-ID: 0300
  Device-2: NVIDIA AD106M [GeForce RTX 4070 Max-Q / Mobile] vendor: Lenovo
    driver: nvidia v: 610.57.04 alternate: nouveau,nvidia_drm
    non-free: 550-6xx.xx+ status: current (as of 2026-07) arch: Lovelace
    code: AD1xx process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4
    speed: 16 GT/s lanes: 8 ports: active: none empty: DP-1, DP-2, HDMI-A-1,
    eDP-2 bus-ID: 01:00.0 chip-ID: 10de:2860 class-ID: 0300
  Device-3: Chicony Integrated Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-11:4 chip-ID: 04f2:b7b6
    class-ID: fe01 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.24 with: Xwayland v: 24.1.13
    compositor: kwin_wayland driver: X: loaded: N/A unloaded: modesetting,vesa
    alternate: fbdev,intel dri: iris,nouveau gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: BOE Display 0x0b38 serial: <filter> built: 2022
    res: mode: 2560x1600 hz: 165 scale: 125% (1.25) to: 2048x1280 dpi: 189
    gamma: 1.2 size: 344x215mm (13.54x8.46") diag: 406mm (16") ratio: 16:10
    modes: 2560x1600
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
    drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia wayland: drv: iris x11: drv: iris
    inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: intel mesa v: 26.2.0 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel Graphics (RPL-S)
    device-ID: 8086:a788 memory: 30.33 GiB unified: yes display-ID: :0.0
  API: Vulkan v: 1.4.357 layers: 5 device: 0 type: integrated-gpu
    name: Intel Graphics (RPL-S) driver: mesa intel v: 26.2.0
    device-ID: 8086:a788 surfaces: N/A device: 1 type: discrete-gpu
    name: NVIDIA GeForce RTX 4070 Laptop GPU driver: nvidia v: 610.57.04
    device-ID: 10de:2860 surfaces: N/A device: 2 type: cpu name: llvmpipe
    (LLVM 22.1.8 256 bits) driver: mesa llvmpipe v: 26.2.0 (LLVM 22.1.8)
    device-ID: 10005:0000 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,
    kscreen-doctor, xfce4-display-settings gpu: lact,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr

Currently (Mesa 26.1.6 – no issue)

❯ inxi -GSaz
System:
  Kernel: 7.1.8-1-default arch: x86_64 bits: 64 compiler: gcc v: 16.2.0
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-7.1.8-1-default
    root=UUID=99a5af1a-9348-4e4e-9c42-e64cbf5e1710 splash=silent quiet
    security=apparmor rd.driver.blacklist=nouveau
    rd.driver.blacklist=nova-core intel_iommu=on mitigations=auto
  Desktop: KDE Plasma v: 6.7.4 tk: Qt v: N/A info: frameworks v: 6.28.0
    wm: kwin_wayland tools: avail: xscreensaver vt: 2 dm: 1: GDM v: 50.2
    2: LightDM v: 1.32.0 note: stopped 3: SDDM note: stopped Distro: openSUSE
    Tumbleweed 20260813
Graphics:
  Device-1: Intel Raptor Lake-S UHD Graphics vendor: Lenovo driver: i915
    v: kernel alternate: xe arch: Xe process: Intel 10nm built: 2020-21 ports:
    active: eDP-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:a788
    class-ID: 0300
  Device-2: NVIDIA AD106M [GeForce RTX 4070 Max-Q / Mobile] vendor: Lenovo
    driver: nvidia v: 610.57.04 alternate: nouveau,nvidia_drm
    non-free: 550-6xx.xx+ status: current (as of 2026-07) arch: Lovelace
    code: AD1xx process: TSMC n4 (5nm) built: 2022+ pcie: gen: 1
    speed: 2.5 GT/s lanes: 8 link-max: gen: 4 speed: 16 GT/s ports:
    active: none empty: DP-1, DP-2, HDMI-A-1, eDP-2 bus-ID: 01:00.0
    chip-ID: 10de:2860 class-ID: 0300
  Device-3: Chicony Integrated Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-11:4 chip-ID: 04f2:b7b6
    class-ID: fe01 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.24 with: Xwayland v: 24.1.13
    compositor: kwin_wayland driver: X: loaded: N/A unloaded: modesetting,vesa
    alternate: fbdev,intel dri: iris,nouveau gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: BOE Display 0x0b38 serial: <filter> built: 2022
    res: mode: 2560x1600 hz: 165 scale: 125% (1.25) to: 2048x1280 dpi: 189
    gamma: 1.2 size: 344x215mm (13.54x8.46") diag: 406mm (16") ratio: 16:10
    modes: 2560x1600
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
    drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia wayland: drv: iris x11: drv: iris
    inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: intel mesa v: 26.1.6 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel Graphics (RPL-S)
    device-ID: 8086:a788 memory: 30.33 GiB unified: yes display-ID: :0.0
  API: Vulkan v: 1.4.357 layers: 5 device: 0 type: integrated-gpu
    name: Intel Graphics (RPL-S) driver: mesa intel v: 26.1.6
    device-ID: 8086:a788 surfaces: N/A device: 1 type: discrete-gpu
    name: NVIDIA GeForce RTX 4070 Laptop GPU driver: nvidia v: 610.57.04
    device-ID: 10de:2860 surfaces: N/A device: 2 type: cpu name: llvmpipe
    (LLVM 22.1.8 256 bits) driver: mesa llvmpipe v: 26.1.6 (LLVM 22.1.8)
    device-ID: 10005:0000 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,
    kscreen-doctor, xfce4-display-settings gpu: lact,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr

btw the repro is to just search for something (popular) on youtube and keep scrolling down rapidly causing it to load as many video thumbnails as possible

If you start the browser with switherooctl so it uses the Nvidia device, how does that fair?

Not reproducible with the nvidia (driver)

here’s more info

journalctl -b -0 | grep 'i915'
Aug 14 18:27:06 localhost kernel: i915 0000:00:02.0: [drm] Found alderlake_s/raptorlake_s (device ID a788) integrated display version 12.00 stepping D0
Aug 14 18:27:06 localhost kernel: i915 0000:00:02.0: [drm] VT-d active for gfx access
Aug 14 18:27:07 localhost kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
Aug 14 18:27:07 localhost kernel: i915 0000:00:02.0: [drm] Using Transparent Hugepages
Aug 14 18:27:07 localhost kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adls_dmc_ver2_01.bin (v2.1)
Aug 14 18:27:07 localhost kernel: i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io:owns=io+mem
Aug 14 18:27:07 localhost kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/tgl_guc_70.bin version 70.49.4
Aug 14 18:27:07 localhost kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
Aug 14 18:27:07 localhost kernel: i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads
Aug 14 18:27:07 localhost kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
Aug 14 18:27:07 localhost kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
Aug 14 18:27:07 localhost kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled
Aug 14 18:27:07 localhost kernel: i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized
Aug 14 18:27:07 localhost kernel: i915 0000:00:02.0: [drm] Skipping intel_backlight registration
Aug 14 18:27:07 localhost kernel: i915 0000:00:02.0: [drm] Registered 4 planes with drm panic
Aug 14 18:27:07 localhost kernel: [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 1
Aug 14 18:27:07 localhost kernel: fbcon: i915drmfb (fb0) is primary device
Aug 14 18:27:07 localhost kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
Aug 14 18:27:09 localhost kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
Aug 14 18:27:09 localhost kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
Aug 14 18:27:09 localhost kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops intel_audio_component_bind_ops [i915])
Aug 14 18:27:19 localhost.localdomain gnome-shell[2083]: Added device '/dev/dri/card1' (i915) using atomic mode setting.
Aug 14 18:30:58 localhost.localdomain kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:849f9ffc, in Renderer [11559]
Aug 14 18:30:58 localhost.localdomain kernel: i915 0000:00:02.0: [drm] GPU error state saved to /sys/class/drm/card1/error
Aug 14 18:30:58 localhost.localdomain kernel: i915 0000:00:02.0: [drm] Renderer[11559] context reset due to GPU hang
Aug 14 18:31:07 localhost.localdomain kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:859ffffb, in Renderer [11559]
Aug 14 18:31:07 localhost.localdomain kernel: i915 0000:00:02.0: [drm] Renderer[11559] context reset due to GPU hang

The contents of /sys/class/drm/card1/error
https://paste.opensuse.org/pastes/21283a5b1d23

I would suspect a Mesa bug…

FWIW https://bugzilla.opensuse.org/show_bug.cgi?id=1275220

and my gawd just scrolling on that page trying to file the issue was a challenge – firefox even went unresponsive with a black screen, alt+tab would just show outline and hang there … paaaaaain

@mburge I would suggest you add the inxi -GSaz info to the bug report so they know it’s a dual GPU setup…

It now looks like I had at least 1 FireFox crash that fits the description both here in this topic and the linked bugzilla report. It is on my N100 system currently VERSION_ID=“20260817”
and I was more focused on the last crash (yesterday) but not enough to make it worth trying to reproduce. It looks like it is related to a more rare use-case of the GPU (i915) and/or non-CPU parts earlier yesterday as I was cleaning up old video transcoder scripts which cover Intel Broadcom Rockchip HW codec usage, but all different methods/drivers. I was also trying to see what vulkan can do, but ffmpeg8 (from packman for tumbleweed) mentioned no VK encoder API on the N100.
I had just installed ffmpeg8 a day before, earlier was still ffmpeg7 or even ffmpeg4 for many years.
The crash was at the time also the whole desktop froze for a few seconds, that I remember as typical GPU hang occurring various times in the past 3 years or so on Intel X5-z8350 SoC.
Now on N100 also very strange graphical effects, I could move the main remaining konsole terminal window, but ‘nice’ very fast like shivering effect around it, that was after the GPU hang. So I thought better type reboot before whole platform crash or freeze/hang maybe. In the past, usually the only way was ssh or even serial console to do a reboot, else just cold reboot / power-cycle.

I also now see in the bug report that there is an attachment with big content, I should have looked at my case and dump it as well, but was not really sure want actually caused the crash. I also has/was playing a video with mpv (a HEVC+HE-AAC DVB-T2 FTA recording). FireFox crashed when I was not really doing anything with it at the time it crashed, I was just switching to it. There was no real internet contentent involved, al local activity, but had been playing the same video with FireFox from Jellyfin server before.

Now that I write this, I remember the video (3 hours recording ) also stopped / exited all of a sudden some time earlier. It simply is something not needed a lot attention all the time, so I just forgot it and went on with doing other things.
So it seems to me that maybe ffmpeg8 and it libva stuff as well, might be a trigger. As those are from packman, not openSUSE Tumbleweed, the question is who should take the bug report.

Bottom line for me is that all this still works way better than comparable on Aarch64 (if at all working there) and is not really an openSUSE thing due to the codec royalties issue. I have also Debian installed, there things like Jellyfin (with HW transoding) work as upgrade-able standard .deb packages. There is no .rpm stuff for openSUSE. But is only server/background and Debian has older FireFox-ESR and older Mesa etc.

Might be a short-lived hiccup – no longer reproduces for me with Mesa 26.2.1.