Blender Flatpak crashes a SEGV error | F40 Kinoite |

Ask Fedora
, , , , , , , ,
1

Blender crashing as the title says.

In f39, I also experienced this issue, but got around it by booting in X11 instead of Wayland. So I assume the issue is with Wayland somehow. f40 Kinoite removed X11, so I can’t use that solution anymore.

The relevant error in the crash report seems to be SEGV (signal 11), which kills programs that try to access memory outside their purview.

I noticed that for other users, a similar error was being caused by having outdated hardware no longer supported by Blender. My machine is using recent hardware, so I don’t think this should be my problem.

Lastly, I’ve seen this or similar problems come up for people using Intel or Nvidia hardware. This shouldn’t be the case for me. Both my CPU and GPU are AMD based, not Intel nor Nvidia.

About this System:

Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
Kernel Version: 6.9.5-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 7950X 16-Core Processor
Memory: 61.9 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 XTX
Manufacturer: ASUS

flatpak info org.blender.Blender (minus “Date”):

Blender Foundation - Free and open source 3D creation suite

          ID: org.blender.Blender
         Ref: app/org.blender.Blender/x86_64/stable
        Arch: x86_64
      Branch: stable
     Version: 4.1.1
     License: GPL-3.0
      Origin: flathub
  Collection: org.flathub.Stable
Installation: system
   Installed: 1.4 GB
     Runtime: org.freedesktop.Platform/x86_64/23.08
         Sdk: org.freedesktop.Sdk/x86_64/23.08

      Commit: 3e5838d03e01228cf8599d9a98147d168f33d5da8fc7da205f462636affa37d3
      Parent: 1bd1d461eb15787d88f4aef3c680d17e5d05d4c87ae9bc3178bb9250d20af174
     Subject: Update blender-4.1.0-linux-x64.tar.xz to 4.1.1 (68ae71b0)

Overview - Crashed Processes Viewer (some details redacted):

           PID: 417219 (blender)
        Signal: 11 (SEGV)
  Command Line: ./blender
    Executable: /app/blender/blender
       Storage: /var/lib/systemd/coredump/core.blender.1000.20d11a77890e425cadfa03268b96dcba.417219.1719450444000000.zst (present)
  Size on Disk: 7.5M
       Message: Process 417219 (blender) of user 1000 dumped core.
                
                Module /app/blender/lib/libOpenImageDenoise_core.so.2.2.2 without build-id.
                Module /app/blender/lib/libOpenImageDenoise_core.so.2.2.2
                Module /app/blender/lib/libboost_locale.so.1.82.0 without build-id.
                Module /app/blender/lib/libboost_locale.so.1.82.0
                Module /app/blender/lib/libboost_serialization.so.1.82.0 without build-id.
                Module /app/blender/lib/libboost_serialization.so.1.82.0
                Module /app/blender/lib/libboost_wave.so.1.82.0 without build-id.
                Module /app/blender/lib/libboost_wave.so.1.82.0
                Module /app/blender/lib/libboost_regex.so.1.82.0 without build-id.
                Module /app/blender/lib/libboost_regex.so.1.82.0
                Module /app/blender/lib/libboost_chrono.so.1.82.0 without build-id.
                Module /app/blender/lib/libboost_chrono.so.1.82.0
                Module /app/blender/lib/libboost_thread.so.1.82.0 without build-id.
                Module /app/blender/lib/libboost_thread.so.1.82.0
                Module /app/blender/lib/libMaterialXCore.so.1.38.8 without build-id.
                Module /app/blender/lib/libMaterialXCore.so.1.38.8
                Module /app/blender/lib/libboost_filesystem.so.1.82.0 without build-id.
                Module /app/blender/lib/libboost_filesystem.so.1.82.0
                Module /app/blender/lib/libboost_iostreams.so.1.82.0 without build-id.
                Module /app/blender/lib/libboost_iostreams.so.1.82.0
                Module /app/blender/lib/libboost_python311.so.1.82.0 without build-id.
                Module /app/blender/lib/libboost_python311.so.1.82.0
                Module /app/blender/lib/libboost_system.so.1.82.0 without build-id.
                Module /app/blender/lib/libboost_date_time.so.1.82.0 without build-id.
                Module /app/blender/lib/libOpenImageDenoise.so.2.2.2 without build-id.
                Module /app/blender/lib/libOpenImageDenoise.so.2.2.2
                Module /app/blender/lib/libcycles_kernel_oneapi_aot.so without build-id.
                Module /app/blender/lib/libcycles_kernel_oneapi_aot.so
                Module /app/blender/lib/libembree4.so.4 without build-id.
                Module /app/blender/lib/libembree4.so.4
                Module /app/blender/lib/libtbb.so.2 without build-id.
                Module /app/blender/lib/libtbb.so.2
                Stack trace of thread 2:
                #0  0x00007f3ed091d155 n/a (/usr/lib/x86_64-linux-gnu/GL/default/lib/libEGL_mesa.so.0.0.0 + 0x2d155)
                #1  0x00007f3ed091e6b1 n/a (/usr/lib/x86_64-linux-gnu/GL/default/lib/libEGL_mesa.so.0.0.0 + 0x2e6b1)
                #2  0x00007f3ed092162a n/a (/usr/lib/x86_64-linux-gnu/GL/default/lib/libEGL_mesa.so.0.0.0 + 0x3162a)
                #3  0x00007f3ed0916c98 n/a (/usr/lib/x86_64-linux-gnu/GL/default/lib/libEGL_mesa.so.0.0.0 + 0x26c98)
                #4  0x00007f3ed09056a8 n/a (/usr/lib/x86_64-linux-gnu/GL/default/lib/libEGL_mesa.so.0.0.0 + 0x156a8)
                #5  0x00000000028cd0e0 n/a (/app/blender/blender + 0x24cd0e0)
                ELF object binary architecture: AMD x86-64

Does anyone know what’s going on here? Any help or insight would be greatly appreciated.
In the worst case scenario, I’ll just rollback to 39 for X11.

2

It’s not that severe. At worst you can point to a different commit of the Blender Flatpak to try. So, give me a moment and I’ll get back to you.

1 Like
3

Can you try to update to a previous Commit ?

flatpak remote-info --log flathub org.blender.Blender

Find the commit you want to revert to :

flatpak update --commit=<commit_id> org.blender.Blender

1 Like
4

You can, but for sure this is a workaround.

Kwin is no longer built with wayland support so you would need to do your own build, use updated upstream kwin but with x11, make a copr, remove kwin and replace it with that one.

1 Like
5

Hello, thank you for this. I didn’t know flatpak had a rollback feature.

I checked the --log commits like you mentioned, and found the earliest one listed for me was Blender 4.0.2. I reverted to this version and tried to open Blender, but it crashed same as before.

Maybe I’d have luck with their LTS release Blender 3.6.13, but that’s going back quite a ways and I’d really rather just solve the root issue if I can…
But if all else fails, I’ll go this route. I’ll have to look up the commit number for 3.6.13.

6

This one is a bit beyond me, I’m afraid… I’d definitely break something in the process.

7

It is not a roolback per-say. You are pointing to a certain commit and updating to it.

You mean like this ?

You know the Flathub/Blender repo is in Github. Just copy the commit number and you are good.

1 Like
8

Yeah I also think so.

There is a nobara COPR and it has kwin with X11 support. But I guess you need to download the .rpm file. If you would add the COPR, random packages could get swapped out.

For example this one

Then rpm-ostree install packagename.rpm

Or you could modify the COPR .repo file to only allow the kwin package. Otherwise you may get unwanted updates that are intended for Nobara.

I could not find any way to do this.

1 Like
9

Removed f39, intel, nvidia

10

Added wayland, x11-wayland-transition

11

You don’t need to rebuild packages. Both plasma-workspace-x11 and kwin-x11 are still available in the Fedora repositories, but not supported by the KDE SIG nor installed by default.

2 Likes
12

I apologize for the late followup.

This issue was thankfully solved for me with the release of Blender 4.2 LTS. Updating to this version today, along with a slew of other system and program updates, allowed Blender to boot and render normally.

Before this, I was preparing to see if this issue was being caused by a problem with the ROCm drivers, as I have AMD hardware, and have read that Blender may rely on those drivers in Fedora for AMD hardware.

Regardless, this issue is solved. Thank you to all who gave advice and insight, and to the skilled maintainers at Blender and Fedora.

13

Cycles rendering demands it !

1 Like