Lack of "Unsupported GPU" GUI message when Blender crashes on startup on linux. #126136

New Issue

MechDR · 2024-08-09T14:12:55+02:00

MechDR commented

2024-08-09 14:12:55 +02:00

System Information
Operating system: Void Linux (x86_64-glibc)
Graphics card:

glxinfo -B

Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Mesa (0x1002)
    Device: AMD RV730 (DRM 2.50.0 / 6.6.44_1, LLVM 18.1.8) (0x9498)
    Version: 24.1.4
    Accelerated: yes
    Video memory: 2048MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 3.3
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.0
Memory info (GL_ATI_meminfo):
    VBO free memory - total: 2047 MB, largest block: 2047 MB
    VBO free aux. memory - total: 1021 MB, largest block: 1021 MB
    Texture free memory - total: 2047 MB, largest block: 2047 MB
    Texture free aux. memory - total: 1021 MB, largest block: 1021 MB
    Renderbuffer free memory - total: 2047 MB, largest block: 2047 MB
    Renderbuffer free aux. memory - total: 1021 MB, largest block: 1021 MB
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 2048 MB
    Total available memory: 3069 MB
    Currently available dedicated video memory: 2047 MB
OpenGL vendor string: Mesa
OpenGL renderer string: AMD RV730 (DRM 2.50.0 / 6.6.44_1, LLVM 18.1.8)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 24.1.4
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.0 Mesa 24.1.4
OpenGL shading language version string: 1.30
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.0 Mesa 24.1.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

Blender Version
Broken: (4.0.2, main, 9be62e85b7, 2023-12-05)
Worked: (I have no idea, it's the first time I use Blender)

Short description of error

You launch the application from the terminal, it crashes.

Content of blender.crash.txt.

blender.crash.txt

# Blender 4.0.2, Unknown revision

# backtrace
blender(+0xf43dd3) [0x5568b1097dd3]
blender(+0x862ea9) [0x5568b09b6ea9]
/usr/lib/libc.so.6(+0x3f8c0) [0x7f90396558c0]
blender(+0xf8a15c) [0x5568b10de15c]
blender(+0xf8a1bd) [0x5568b10de1bd]
blender(+0xf53d04) [0x5568b10a7d04]
blender(+0xf6998e) [0x5568b10bd98e]
blender(+0xf6f124) [0x5568b10c3124]
blender(+0x8385e8) [0x5568b098c5e8]
/usr/lib/libc.so.6(+0x29c4c) [0x7f903963fc4c]
/usr/lib/libc.so.6(__libc_start_main+0x85) [0x7f903963fd05]
blender(+0x85e8b1) [0x5568b09b28b1]

# Python backtrace

Terminal output with debug symbols when loaded in gdb (gdb blender).

gdb blender

#0  wm_window_set_drawable (activate=false, win=0x0, wm=0x7fffe4bc6c08) at ../source/blender/windowmanager/intern/wm_window.cc:1235
#1  wm_window_ghostwindow_add (title=0x555558d9b801 "Blender", is_dialog=<optimized out>, win=0x7fffe43acd08, wm=0x7fffe4bc6c08)
    at ../source/blender/windowmanager/intern/wm_window.cc:785
#2  wm_window_ghostwindow_ensure (wm=0x7fffe4bc6c08, win=0x7fffe43acd08, is_dialog=<optimized out>)
    at ../source/blender/windowmanager/intern/wm_window.cc:817
#3  0x00005555564de1bd in wm_window_ghostwindows_ensure (wm=wm@entry=0x7fffe4bc6c08)
    at ../source/blender/windowmanager/intern/wm_window.cc:874
#4  0x00005555564a7d04 in WM_check (C=C@entry=0x7fffe6398b88) at ../source/blender/windowmanager/intern/wm.cc:483
#5  0x00005555564bd98e in wm_homefile_read_ex (C=C@entry=0x7fffe6398b88, params_homefile=params_homefile@entry=0x7fffffffe6b0, 
    reports=reports@entry=0x0, r_params_file_read_post=r_params_file_read_post@entry=0x7fffffffe6a8)
    at ../source/blender/windowmanager/intern/wm_files.cc:1476
#6  0x00005555564c3124 in WM_init (C=C@entry=0x7fffe6398b88, argc=argc@entry=1, argv=argv@entry=0x7fffffffe888)
    at ../source/blender/windowmanager/intern/wm_init_exit.cc:302
#7  0x0000555555d8c5e8 in main (argc=1, argv=0x7fffffffe888) at ../source/creator/creator.cc:537

Terminal output from blender --debug-all.

blender --debug-all

Switching to fully guarded memory allocator.
graph_id_tag_update: id=SCScene flags=BASE_FLAGS source=USER_EDIT
DEG_relations_tag_update: Tagging relations for update.
graph_id_tag_update: id=GRScene Collection flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=SCScene flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GRCollection flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GROVERRIDE_RESYNC_LEFTOVERS flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GRScene Collection flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=SCScene flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GRCollection flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GROVERRIDE_RESYNC_LEFTOVERS flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GRScene Collection flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=SCScene flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GRCollection flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GROVERRIDE_RESYNC_LEFTOVERS flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GRScene Collection flags=TRANSFORM, GEOMETRY, COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=SCScene flags=TRANSFORM, GEOMETRY, COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=SCScene flags=TRANSFORM, GEOMETRY, COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GRScene Collection flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=SCScene flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GRCollection flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GROVERRIDE_RESYNC_LEFTOVERS flags=COPY_ON_WRITE source=USER_EDIT
DEG_relations_tag_update: Tagging relations for update.
DEG_relations_tag_update: Tagging relations for update.
DEG_relations_tag_update: Tagging relations for update.
graph_id_tag_update: id=GRScene Collection flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=SCScene flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=GRCollection flags=COPY_ON_WRITE source=USER_EDIT
Received X11 Error:
	error code:   170
	request code: 153
	minor code:   0
	error text:   GLXBadFBConfig
Received X11 Error:
	error code:   170
	request code: 153
	minor code:   0
	error text:   GLXBadFBConfig
Received X11 Error:
	error code:   170
	request code: 153
	minor code:   0
	error text:   GLXBadFBConfig
Received X11 Error:
	error code:   170
	request code: 153
	minor code:   0
	error text:   GLXBadFBConfig
Writing: /tmp/blender.crash.txt
fish: Job 1, 'blender --debug-all' terminated by signal SIGSEGV (Address boundary error)

The same error appears from the Blender flatpak, so it's probably not a building/packaging issue.

It's also worth noting that I don't own a card that can run Blender.

Here is a downstream reference link with the issue: https://github.com/void-linux/void-packages/issues/49763. There are some pointers there on where the issue may lay from @fruitiestPunch.

Exact steps for others to reproduce the error

Try to run Blender >= 4.0.0 on an unsupported GPU (VM with no GPU passthrough will do nicely).

**System Information** Operating system: Void Linux (x86_64-glibc) Graphics card: <details> <summary> `glxinfo -B` </summary> ```` Extended renderer info (GLX_MESA_query_renderer): Vendor: Mesa (0x1002) Device: AMD RV730 (DRM 2.50.0 / 6.6.44_1, LLVM 18.1.8) (0x9498) Version: 24.1.4 Accelerated: yes Video memory: 2048MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 3.3 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.0 Memory info (GL_ATI_meminfo): VBO free memory - total: 2047 MB, largest block: 2047 MB VBO free aux. memory - total: 1021 MB, largest block: 1021 MB Texture free memory - total: 2047 MB, largest block: 2047 MB Texture free aux. memory - total: 1021 MB, largest block: 1021 MB Renderbuffer free memory - total: 2047 MB, largest block: 2047 MB Renderbuffer free aux. memory - total: 1021 MB, largest block: 1021 MB Memory info (GL_NVX_gpu_memory_info): Dedicated video memory: 2048 MB Total available memory: 3069 MB Currently available dedicated video memory: 2047 MB OpenGL vendor string: Mesa OpenGL renderer string: AMD RV730 (DRM 2.50.0 / 6.6.44_1, LLVM 18.1.8) OpenGL core profile version string: 3.3 (Core Profile) Mesa 24.1.4 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 3.0 Mesa 24.1.4 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL ES profile version string: OpenGL ES 3.0 Mesa 24.1.4 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 ```` </details> **Blender Version** Broken: (4.0.2, main, `9be62e85b7`, 2023-12-05) Worked: (I have no idea, it's the first time I use Blender) **Short description of error** You launch the application from the terminal, it crashes. Content of `blender.crash.txt`. <details> <summary> `blender.crash.txt` </summary> ```` # Blender 4.0.2, Unknown revision # backtrace blender(+0xf43dd3) [0x5568b1097dd3] blender(+0x862ea9) [0x5568b09b6ea9] /usr/lib/libc.so.6(+0x3f8c0) [0x7f90396558c0] blender(+0xf8a15c) [0x5568b10de15c] blender(+0xf8a1bd) [0x5568b10de1bd] blender(+0xf53d04) [0x5568b10a7d04] blender(+0xf6998e) [0x5568b10bd98e] blender(+0xf6f124) [0x5568b10c3124] blender(+0x8385e8) [0x5568b098c5e8] /usr/lib/libc.so.6(+0x29c4c) [0x7f903963fc4c] /usr/lib/libc.so.6(__libc_start_main+0x85) [0x7f903963fd05] blender(+0x85e8b1) [0x5568b09b28b1] # Python backtrace ```` </details> Terminal output with debug symbols when loaded in gdb (`gdb blender`). <details> <summary> `gdb blender` </summary> ```` #0 wm_window_set_drawable (activate=false, win=0x0, wm=0x7fffe4bc6c08) at ../source/blender/windowmanager/intern/wm_window.cc:1235 #1 wm_window_ghostwindow_add (title=0x555558d9b801 "Blender", is_dialog=<optimized out>, win=0x7fffe43acd08, wm=0x7fffe4bc6c08) at ../source/blender/windowmanager/intern/wm_window.cc:785 #2 wm_window_ghostwindow_ensure (wm=0x7fffe4bc6c08, win=0x7fffe43acd08, is_dialog=<optimized out>) at ../source/blender/windowmanager/intern/wm_window.cc:817 #3 0x00005555564de1bd in wm_window_ghostwindows_ensure (wm=wm@entry=0x7fffe4bc6c08) at ../source/blender/windowmanager/intern/wm_window.cc:874 #4 0x00005555564a7d04 in WM_check (C=C@entry=0x7fffe6398b88) at ../source/blender/windowmanager/intern/wm.cc:483 #5 0x00005555564bd98e in wm_homefile_read_ex (C=C@entry=0x7fffe6398b88, params_homefile=params_homefile@entry=0x7fffffffe6b0, reports=reports@entry=0x0, r_params_file_read_post=r_params_file_read_post@entry=0x7fffffffe6a8) at ../source/blender/windowmanager/intern/wm_files.cc:1476 #6 0x00005555564c3124 in WM_init (C=C@entry=0x7fffe6398b88, argc=argc@entry=1, argv=argv@entry=0x7fffffffe888) at ../source/blender/windowmanager/intern/wm_init_exit.cc:302 #7 0x0000555555d8c5e8 in main (argc=1, argv=0x7fffffffe888) at ../source/creator/creator.cc:537 ```` </details> Terminal output from `blender --debug-all`. <details> <summary> `blender --debug-all` </summary> ```` Switching to fully guarded memory allocator. graph_id_tag_update: id=SCScene flags=BASE_FLAGS source=USER_EDIT DEG_relations_tag_update: Tagging relations for update. graph_id_tag_update: id=GRScene Collection flags=COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=SCScene flags=COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=GRCollection flags=COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=GROVERRIDE_RESYNC_LEFTOVERS flags=COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=GRScene Collection flags=COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=SCScene flags=COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=GRCollection flags=COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=GROVERRIDE_RESYNC_LEFTOVERS flags=COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=GRScene Collection flags=COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=SCScene flags=COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=GRCollection flags=COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=GROVERRIDE_RESYNC_LEFTOVERS flags=COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=GRScene Collection flags=TRANSFORM, GEOMETRY, COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=SCScene flags=TRANSFORM, GEOMETRY, COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=SCScene flags=TRANSFORM, GEOMETRY, COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=GRScene Collection flags=COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=SCScene flags=COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=GRCollection flags=COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=GROVERRIDE_RESYNC_LEFTOVERS flags=COPY_ON_WRITE source=USER_EDIT DEG_relations_tag_update: Tagging relations for update. DEG_relations_tag_update: Tagging relations for update. DEG_relations_tag_update: Tagging relations for update. graph_id_tag_update: id=GRScene Collection flags=COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=SCScene flags=COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=GRCollection flags=COPY_ON_WRITE source=USER_EDIT Received X11 Error: error code: 170 request code: 153 minor code: 0 error text: GLXBadFBConfig Received X11 Error: error code: 170 request code: 153 minor code: 0 error text: GLXBadFBConfig Received X11 Error: error code: 170 request code: 153 minor code: 0 error text: GLXBadFBConfig Received X11 Error: error code: 170 request code: 153 minor code: 0 error text: GLXBadFBConfig Writing: /tmp/blender.crash.txt fish: Job 1, 'blender --debug-all' terminated by signal SIGSEGV (Address boundary error) ```` </details> The same error appears from the Blender flatpak, so it's probably not a building/packaging issue. It's also worth noting that I don't own a card that can run Blender. Here is a downstream reference link with the issue: https://github.com/void-linux/void-packages/issues/49763. There are some pointers there on where the issue may lay from @fruitiestPunch. **Exact steps for others to reproduce the error** Try to run Blender >= 4.0.0 on an unsupported GPU (VM with no GPU passthrough will do nicely).

MechDR added the

labels 2024-08-09 14:12:56 +02:00

Alaska commented

2024-08-09 14:41:29 +02:00

Your GPU is too old for the current version of Blender (See our requirements page)

According to the requirements you need a GCN1 or newer AMD GPU, but you have a Terrascale GPU, which is lower than these requirements.

To fix this issue, you will need to get a newer GPU, or use a older version of Blender: https://download.blender.org/release/

Your GPU is too old for the current version of Blender (See our [requirements page](https://www.blender.org/download/requirements/)) According to the requirements you need a GCN1 or newer AMD GPU, but you have a Terrascale GPU, which is lower than these requirements. To fix this issue, you will need to get a newer GPU, or use a older version of Blender: https://download.blender.org/release/

Alaska closed this issue

2024-08-09 14:41:33 +02:00

Blender Bot added

and removed

labels 2024-08-09 14:41:34 +02:00

fruitspunch commented

2024-08-09 14:43:36 +02:00

I dug a little and compared Blender 4.0.1 with Blender 3.6.12 (this one and v3.3. work for me) and
GPU_context_active_set(static_cast<GPUContext *>(win->gpuctx));
lead me to
9be62e85b7/source/blender/gpu/GPU_context.h (L65)
where even the doc string states that it can be NULL (in v4 and v3.6).
This only difference is the STATIC_CASTING in v4.

I think GHOST_CreateWindow fails in v4, because it uses gpuSettings (9be62e85b7/source/blender/windowmanager/intern/wm_window.cc (L734C7-L734C18)) for the first time. Before it was glSettings (626a6b1c67/source/blender/windowmanager/intern/wm_window.c (L692)).
This would be in line with what @MechDR said about PCs without GPU Passthrough.

I hope this helps in any way

I dug a little and compared Blender 4.0.1 with Blender 3.6.12 (this one and v3.3. work for me) and `GPU_context_active_set(static_cast<GPUContext *>(win->gpuctx));` lead me to https://github.com/blender/blender/blob/9be62e85b7270d3d2e5bcc846420b91bab3988f9/source/blender/gpu/GPU_context.h#L65 where even the doc string states that it can be NULL (in v4 and v3.6). This only difference is the STATIC_CASTING in v4. I think `GHOST_CreateWindow` fails in v4, because it uses `gpuSettings` (https://github.com/blender/blender/blob/9be62e85b7270d3d2e5bcc846420b91bab3988f9/source/blender/windowmanager/intern/wm_window.cc#L734C7-L734C18) for the first time. Before it was `glSettings` (https://github.com/blender/blender/blob/626a6b1c67997ac2432e91e836db5ed0f2dd8c64/source/blender/windowmanager/intern/wm_window.c#L692). This would be in line with what @MechDR said about PCs without GPU Passthrough. I hope this helps in any way

Alaska commented

2024-08-09 14:49:04 +02:00

Sorry, I may of been too quick closing this issue. I will reopen it for someone else to review.

So the bug that's being reported is that Blender crashes on unsupported GPUs, when ideally a error message explain that the GPU is unsupported would be better (and already exists on Windows and maybe Linux)?

Sorry, I may of been too quick closing this issue. I will reopen it for someone else to review. So the bug that's being reported is that Blender crashes on unsupported GPUs, when ideally a error message explain that the GPU is unsupported would be better (and already exists on Windows and maybe Linux)?

Alaska reopened this issue

2024-08-09 14:49:07 +02:00

Blender Bot added

and removed

labels 2024-08-09 14:49:10 +02:00

Alaska changed title from ~~Blender crashes on startup~~ to Blender crashes on startup with unsupported GPU

2024-08-09 14:49:34 +02:00

MechDR commented

2024-08-09 14:56:21 +02:00

@Alaska Exactly. I really had no idea that my GPU wasn't supported, it's the first time I've run Blender, ever, I though it will probably show an error message that the GPU is not supported, but instead, I just got that. With digging, yes, you can find out that the unsupported GPU is the problem, but that shouldn't be so hard to find out.

fruitspunch commented

2024-08-09 14:57:27 +02:00

@Alaska Thankf for re-opening the issue.
It's not about the error message, although that would be helpful at least.
The problem is that gpuSettings and glSettings are almost identical in functionality, with gpuSettings having more features (as far as I have seen/understood), yet, in v3.6 with glSettings my graphics chip (no dedicated graphics card) was supported and in v4 it wasn't, although the code that checks and processes the gpu stayed mostly the same.

I wonder which part of the code was changed that first accepted my gpu and now doesn't anymore.

Any ideas where this might come from?

@Alaska Thankf for re-opening the issue. It's not about the error message, although that would be helpful at least. The problem is that `gpuSettings` and `glSettings` are almost identical in functionality, with `gpuSettings` having more features (as far as I have seen/understood), yet, in v3.6 with `glSettings` my graphics chip (no dedicated graphics card) was supported and in v4 it wasn't, although the code that checks and processes the gpu stayed mostly the same. I wonder which part of the code was changed that first accepted my gpu and now doesn't anymore. Any ideas where this might come from?

Alaska commented

2024-08-09 15:05:38 +02:00

Sorry, my knowledge of this area of the code is limited. I will leave triaging or further hints on the cause of this issue to someone else.

YimingWu commented

2024-08-12 09:56:16 +02:00

I think it might be possible to just show a message box on linux. On windows blender does prompt you that your GPU being unsupported with a Win32 MessageBox, there's not direct equivalent thing on x11 environment, but I think a simple message box implementation like this without involving GL would be adequate for such purposes since desktop users don't typically launch blender from terminal and they probably won't see whatever log messages are coming out from stdout. It can at least show simple ascii characters. Maybe a GTK/QT based message box can be doable but that would require a ton of other dependencies just for this one purpose...

I think it might be possible to just show a message box on linux. On windows blender does prompt you that your GPU being unsupported with a Win32 `MessageBox`, there's not direct equivalent thing on x11 environment, but I think a simple message box implementation [like this](https://github.com/Eleobert/MessageBox-X11) without involving GL would be adequate for such purposes since desktop users don't typically launch blender from terminal and they probably won't see whatever log messages are coming out from `stdout`. It can at least show simple ascii characters. Maybe a GTK/QT based message box can be doable but that would require a ton of other dependencies just for this one purpose...

YimingWu changed title from ~~Blender crashes on startup with unsupported GPU~~ to Lack of "Unsupported GPU" GUI message when Blender crashes on startup on linux.

2024-08-12 09:57:56 +02:00

YimingWu commented

2024-08-12 10:00:37 +02:00

Actually there's already a simple message box implementation in blender GHOST_SystemX11::showMessageBox. So I guess we could just use that.

Actually there's already a simple message box implementation in blender `GHOST_SystemX11::showMessageBox`. So I guess we could just use that.

YimingWu added