After the latest updates, i’m continually getting getting Service Crash reports that
gnome-software
has crashed. This seems to happen a dozen times or more after boot, then stops happening. What is going on? Can i do anything to remedy this?
Terminal output?
Journal?
Terminal not used. Which journal output /var/log…?
Usually it is the first attempt, when an app crashes, to start it from a terminal and watch for output.
…no output to terminal in that case. A window opens showing Refreshing Softwarewhich remains open until next crash.
Sorry, Refreshing Data (not Refreshing Software)
After one gnome-software restart, a window showing Lorem appeared until the next crash.
Thereafter, the pattern continued with the Refreshing Data window. But
after the 9th crash the terminal output the following error
21:00:54:732 Gdk Vulkan: ../src/amd/vulkan/radv_physical_device.c:2228: Device '/dev/dri/renderD128' is not using the AMDGPU kernel driver: Invalid argument (VK_ERROR_INCOMPATIBLE_DRIVER)
Illegal instruction (core dumped) gnome-software
and after every crash thereafter the same message appears.
So a hardware issue with vulkan and amdgpu, Is this a dual GPU setup? Can you show the output from inxi -GSaz
inxi -GSaz
System:
Kernel: 6.18.7-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.18.7-1-default
root=UUID=ce70a4cb-918a-4971-a283-3500612754a9 splash=silent
mitigations=auto quiet security=selinux selinux=1 enforcing=1
Desktop: GNOME v: 49.3 tk: GTK v: 3.24.51 wm: gnome-shell
tools: gsd-screensaver-proxy avail: xscreensaver dm: GDM v: 49.2
Distro: openSUSE Tumbleweed 20260131
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Caicos [Radeon HD 6450/7450/8450
/ R5 230 OEM] vendor: PC Partner / Sapphire driver: radeon v: kernel
alternate: amdgpu arch: TeraScale-2 code: Evergreen process: TSMC 32-40nm
built: 2009-15 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 ports:
active: DVI-D-1,HDMI-A-1 empty: VGA-1 bus-ID: 01:00.0 chip-ID: 1002:6779
class-ID: 0300 temp: 55.5 C
Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
compositor: gnome-shell driver: X: loaded: modesetting unloaded: vesa
alternate: fbdev dri: r600 gpu: radeon display-ID: 0
Monitor-1: DVI-D-1 model: AOC 2243W serial: <filter> built: 2010
res: 1920x1080 dpi: 102 gamma: 1.2 size: 477x268mm (18.78x10.55")
diag: 547mm (21.5") ratio: 16:9 modes: max: 1920x1080 min: 720x400
Monitor-2: HDMI-A-1 model: Lenovo L24e-30 serial: <filter> built: 2022
res: 1920x1080 dpi: 93 gamma: 1.2 size: 527x296mm (20.75x11.65")
diag: 604mm (23.8") ratio: 16:9 modes: max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 vendor: mesa v: 25.3.4 glx-v: 1.4 es-v: 3.1
direct-render: yes renderer: AMD CAICOS (DRM 2.51.0 / 6.18.7-1-default LLVM
21.1.8) device-ID: 1002:6779 memory: 1000 MiB unified: no display-ID: :0.0
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Info: Tools: api: glxinfo x11: xprop,xrandr
Check if avoiding the Vulkan renderer is a suitable workaround:
GSK_RENDERER=gl gnome-software
If that works you may choose to install the AMDGPU driver and check if Vulkan works or change the gnome-software launcher to permanently use openGL.
Why not? I didn’t change anything, and it has been working fine for years. I’m getting similar behaviour on my TERRA laptop, so it’s not a hardware failure.
Sounds like a promising idea, but I am out of my depth here.
Just open a terminal and issue GSK_RENDERER=gl gnome-software
If it works, we understand that it is a Vulkan problem and not (only) a gnome-software one.
For amdgpu I’m not a regular user, you may read SDB:AMDGPU
Maybe you miss kernel-firmware-amdgpu or something in your config prevents the driver from loading.
Quoting from the SDB page:
For older chips (Terascale 1, 2, 3) use radeon and r600 drivers, because they are incompatible with amdgpu driver.
So unless Malcolm can suggest some magic, you are left without Vulkan.
That means that the current Gnome 49.x, or at least some of its newer native apps, might be slower or crash.
A workaround is locating the relevant .desktop file, for instance
/usr/share/applications/org.gnome.Software.desktop
and editing the line reading Exec=gnome-software so that it reads Exec=GSK_RENDERER=gl gnome-software.
If the problem involves many apps or the desktop itself you are better off creating a file /etc/environmentthat reads GSK_RENDERER=gl , or appending such a line if you already have an /etc/environment file, directing Gnome to use the openGL renderer throughout.
Maybe in the long run you are better off with a lighter desktop like xfce on such hardware.
The environment file is the best way… It’s a Mesa issue, likely a regression… or just old hardware not being supported any more… @mrmazda may have some ideas…
See https://bugzilla.opensuse.org/show_bug.cgi?id=1254121 for the previous bug report.
~> GSK_RENDERER=gl gnome-software
Illegal instruction (core dumped) GSK_RENDERER=gl gnome-software
By the way, the kernel-firmware-amdgpu is installed on my config.
@hnimmo you need kernel-firmware-radeon is libvulkan_radeon package installed?
Edit: What Mesa packages are you using? zypper se -si Mesa
Both kernel-firmware-radeon and libvulkan_radeon are installed
~> zypper se -si Mesa
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+---------------------------+---------+--------------------+--------+----------------------
i | Mesa | package | 25.3.4-1.1 | x86_64 | Main Repository (OSS)
i | Mesa-demo-x | package | 9.0.0-7.1 | x86_64 | Main Repository (OSS)
i | Mesa-dri | package | 25.3.4-1.1 | x86_64 | Main Repository (OSS)
i | Mesa-libEGL1 | package | 25.3.4-1.1 | x86_64 | Main Repository (OSS)
i | Mesa-libGL1 | package | 25.3.4-1.1 | x86_64 | Main Repository (OSS)
i | Mesa-libva | package | 25.3.4-1.1 | x86_64 | Main Repository (OSS)
i+ | Mesa-vulkan-device-select | package | 25.3.4-1699.2.pm.1 | x86_64 | Packman Repository
@hnimmo So were you using the Packman versions of Mesa before? Else change the Mesa-vulkan-device-select to the OSS version.
Works here:
bruno@LT-B:~> GSK_RENDERER=gl gnome-software
bruno@LT-B:~>
So there might be something else going on.
BTW, setting the environment variable in the .desktop file doesn’t work (or is not as simple as I thought), so as Malcolm wrote, the environment file is the best way (if the problem is Vulkan and not something else).
I wasn’t consciously using the packman version.
Packman repo has been in my config for years in those days to get the vlc packages working. Can I drop it now?