openSUSE Leap 15.5 The process has crashed #116300

New Issue

Stan-Nedeltchev · 2023-12-18T13:57:42+01:00

Stan-Nedeltchev commented

2023-12-18 13:57:42 +01:00

Good day,

The problem must be with my system but I cannot figure out what am I missing.

I have downloaded version "blender-4.0.2-linux-x64.tar.xz" on 15.12.2023. For some reason I got a "The process has crashed" message when trying to execute the "blender" file.

I'm using system:
openSUSE Leap 15.5 distribution with supposedly the latest system updates,
kernel version: 5.14.21-150500.55.39-default (64-bit)
Qt version: 5.15.8
KDE plasma version: 5.27.4
KDE Frameworks version: 5.103.0
Graphic platform: X11
glibc version: 2.31-150300.63.1
Attached are graphic related files: OpenCL, OpenGL (GLX), Vulkan and Server X.

Hardware:
an old laptop HP EliteBook 8570p
The graphical card is Mesa Intel HD Graphics 4000

Blender Version
Broken: Blender 4.0.2
Worked: (newest version of Blender that worked as expected) this is Blender 3.5.1

Short description of error
– when trying to start the file “blender” from Dolphin I get a message “The process has crashed”.
When starting from Terminal ./blender , the message is:
“Writing: /tmp/blender.crash.txt
Segmentation violation (segfault) (the memory is unloaded)”

Attached is the file “blender.crash.txt”

Exact steps for others to reproduce the error
I downloaded the file "blender-4.0.2-linux-x64.tar.xz"
Downloaded the checksum – correct!
Extracted in separate directory.
Executed file “blender”

Based on the default startup or an attached .blend file (as simple as possible).

Thank you for your time.
Regards
Stan

Good day, The problem must be with my system but I cannot figure out what am I missing. I have downloaded version "blender-4.0.2-linux-x64.tar.xz" on 15.12.2023. For some reason I got a "The process has crashed" message when trying to execute the "blender" file. I'm using system: openSUSE Leap 15.5 distribution with supposedly the latest system updates, kernel version: 5.14.21-150500.55.39-default (64-bit) Qt version: 5.15.8 KDE plasma version: 5.27.4 KDE Frameworks version: 5.103.0 Graphic platform: X11 glibc version: 2.31-150300.63.1 Attached are graphic related files: OpenCL, OpenGL (GLX), Vulkan and Server X. Hardware: an old laptop HP EliteBook 8570p The graphical card is Mesa Intel HD Graphics 4000 **Blender Version** Broken: Blender 4.0.2 Worked: (newest version of Blender that worked as expected) this is Blender 3.5.1 **Short description of error** – when trying to start the file “blender” from Dolphin I get a message “The process has crashed”. When starting from Terminal ./blender , the message is: “Writing: /tmp/blender.crash.txt Segmentation violation (segfault) (the memory is unloaded)” Attached is the file “blender.crash.txt” **Exact steps for others to reproduce the error** I downloaded the file "blender-4.0.2-linux-x64.tar.xz" Downloaded the checksum – correct! Extracted in separate directory. Executed file “blender” Based on the default startup or an attached .blend file (as simple as possible). Thank you for your time. Regards Stan

Vulkan log file.txt

42 KiB

Server X log file.txt

75 KiB

OpenGL (GLX) log file.txt

86 KiB

OpenCL log file.txt

333 B

blender.crash.txt

408 B

Stan-Nedeltchev added the

labels 2023-12-18 13:57:43 +01:00

Pratik Borhade commented

2023-12-19 06:51:46 +01:00

Intel HD Graphics 4000

Hi, thanks for the report. This iGPU is not supported anymore since 4.0 release: see release notes
Minimum requirements for Intel GPUs has been bumped to Skylake/broadwell architecture

> Intel HD Graphics 4000 Hi, thanks for the report. This iGPU is not supported anymore since 4.0 release: [see release notes](https://wiki.blender.org/wiki/Reference/Release_Notes/4.0#:~:text=Due%20to%20driver%20issues%2C%20support%20for%20Intel%20HD4000%20series%20GPUs%20has%20been%20dropped.) Minimum requirements for Intel GPUs has been bumped to Skylake/broadwell architecture

Pratik Borhade closed this issue

2023-12-19 06:51:48 +01:00

Blender Bot added

and removed

labels 2023-12-19 06:51:50 +01:00

Sign in to join this conversation.