Page MenuHome

Segmentation fault crash starting Blender 2.8 under Linux
Closed, ResolvedPublic

Description

System Information
Ubuntu 15.04 64 bit - Nvidia Geforce GT 320M

Blender Version
Broken: blender-2.80-53c63db2ee1-linux-glibc219-x86_64
Worked: (optional) night builds from some month ago

Blender 2.8 just don't open, it crashes at start with segmentation fault; here following I pasted the console output:

env@env-K50ID:~$ '/home/env/blender_download/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/blender'
Received X11 Error:
error code: 8
request code: 154
minor code: 34
error text: BadMatch (invalid parameter attributes)
Received X11 Error:
error code: 2
request code: 154
minor code: 34
error text: BadValue (integer parameter out of range for operation)
Received X11 Error:
error code: 2
request code: 154
minor code: 34
error text: BadValue (integer parameter out of range for operation)
Received X11 Error:
error code: 2
request code: 154
minor code: 34
error text: BadValue (integer parameter out of range for operation)
Received X11 Error:
error code: 2
request code: 154
minor code: 34
error text: BadValue (integer parameter out of range for operation)
Received X11 Error:
error code: 2
request code: 154
minor code: 34
error text: BadValue (integer parameter out of range for operation)
Received X11 Error:
error code: 8
request code: 154
minor code: 34
error text: BadMatch (invalid parameter attributes)
Received X11 Error:
error code: 2
request code: 154
minor code: 34
error text: BadValue (integer parameter out of range for operation)
Received X11 Error:
error code: 2
request code: 154
minor code: 34
error text: BadValue (integer parameter out of range for operation)
Received X11 Error:
error code: 2
request code: 154
minor code: 34
error text: BadValue (integer parameter out of range for operation)
Received X11 Error:
error code: 2
request code: 154
minor code: 34
error text: BadValue (integer parameter out of range for operation)
Received X11 Error:
error code: 2
request code: 154
minor code: 34
error text: BadValue (integer parameter out of range for operation)
found bundled python: /home/env/blender_download/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/python
(2, 74, 0)
Traceback (most recent call last):

File "/home/env/blender_download/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/modules/addon_utils.py", line 359, in enable
  raise Exception(f"Add-on '{module_name:s}' has not been upgraded to 2.8, ignoring")

Exception: Add-on 'io_scene_3ds' has not been upgraded to 2.8, ignoring
(2, 79, 1)
Traceback (most recent call last):

File "/home/env/blender_download/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/modules/addon_utils.py", line 359, in enable
  raise Exception(f"Add-on '{module_name:s}' has not been upgraded to 2.8, ignoring")

Exception: Add-on 'io_scene_fbx' has not been upgraded to 2.8, ignoring
(2, 74, 0)
Traceback (most recent call last):

File "/home/env/blender_download/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/modules/addon_utils.py", line 359, in enable
  raise Exception(f"Add-on '{module_name:s}' has not been upgraded to 2.8, ignoring")

Exception: Add-on 'io_anim_bvh' has not been upgraded to 2.8, ignoring
(2, 74, 0)
Traceback (most recent call last):

File "/home/env/blender_download/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/modules/addon_utils.py", line 359, in enable
  raise Exception(f"Add-on '{module_name:s}' has not been upgraded to 2.8, ignoring")

Exception: Add-on 'io_mesh_ply' has not been upgraded to 2.8, ignoring
(2, 78, 0)
Traceback (most recent call last):

File "/home/env/blender_download/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/modules/addon_utils.py", line 359, in enable
  raise Exception(f"Add-on '{module_name:s}' has not been upgraded to 2.8, ignoring")

Exception: Add-on 'io_scene_obj' has not been upgraded to 2.8, ignoring
(2, 76, 0)
Traceback (most recent call last):

File "/home/env/blender_download/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/modules/addon_utils.py", line 359, in enable
  raise Exception(f"Add-on '{module_name:s}' has not been upgraded to 2.8, ignoring")

Exception: Add-on 'io_scene_x3d' has not been upgraded to 2.8, ignoring
(2, 74, 0)
Traceback (most recent call last):

File "/home/env/blender_download/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/modules/addon_utils.py", line 359, in enable
  raise Exception(f"Add-on '{module_name:s}' has not been upgraded to 2.8, ignoring")

Exception: Add-on 'io_mesh_stl' has not been upgraded to 2.8, ignoring
(2, 75, 0)
Traceback (most recent call last):

File "/home/env/blender_download/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/modules/addon_utils.py", line 359, in enable
  raise Exception(f"Add-on '{module_name:s}' has not been upgraded to 2.8, ignoring")

Exception: Add-on 'io_mesh_uv_layout' has not been upgraded to 2.8, ignoring
(2, 57, 0)
Traceback (most recent call last):

File "/home/env/blender_download/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/modules/addon_utils.py", line 359, in enable
  raise Exception(f"Add-on '{module_name:s}' has not been upgraded to 2.8, ignoring")

Exception: Add-on 'io_curve_svg' has not been upgraded to 2.8, ignoring
(2, 80, 0)
CUDA cuInit: Unknown error
GPUShader: compile error:
(0) : error C7011: implicit cast from "int" to "ivec2"

GPUShader: compile error:
(0) : error C7011: implicit cast from "int" to "ivec2"

Writing: /tmp/blender.crash.txt

Errore di segmentazione ("segmentation fault")

Also attached is the blender.crash.txt{F3892895}

Event Timeline

Bastien Montagne (mont29) lowered the priority of this task from 90 to 30.Jul 24 2018, 4:09 PM

Please do not paste walls of text like that directly in reports/comments, such reports must be attached as text files instead.
Also try again with latest 2.8 build, and ensure you are using latest official GPU drivers from NVidia (not the open source ones).

Hi Bastien,
my apologies for the wall of text, not my intention. :)

Just tried with the last build (blender-2.80-1882dfc47c1-linux-glibc219-x86_64), I'm using official drivers from Nvidia (so no open source drivers) but I still have segmentation fault at start. Btw, until the main "remaking" of the UI, Blender 2.8 worked like a charm on my system.
Attached is the new crash text file.

I could investigate and last version of Blender 2.8 that worked (and still does) under my system was night build 8b74741b9e of 2018-03-30.

Bastien Montagne (mont29) changed the task status from Unknown Status to Unknown Status.Aug 9 2018, 11:57 AM
Bastien Montagne (mont29) claimed this task.

Thanks for the report, but afaik GT 320m only supports OpenGL 2.1, we now require at the very least 3.1 iirc, so height years old low-end GPUs are no more an option…

No, accordingly to Nvidia site GT 320M supports OpenGL 3.2. This has also already clarified by Brecht in a earlier (very similar) occasion.

Brecht Van Lommel (brecht) changed the task status from Unknown Status to Unknown Status.Aug 9 2018, 5:38 PM

Yes, I think this card supports OpenGL 3.3 with the latest drivers.

From the first report it looks like some error in compiling shaders. Can you attach the output of running this with a recent build, so we get more detailed info?

./blender --debug-gpu --debug-gpu-shaders --factory-startup &> startup-log.txt

Also useful would be to attach Help > System Info saved from Blender 2.79, so we can see the exact driver version.

Hi Brecht,
ok, here attached is what you requested.
Thanks.

I forgot: with today build "blender-2.80-2e10c658f42-linux-glibc219-x86_64".

Sorry if I wasn't clear, I meant the startup-log.txt produced by running that command, which hopefully has more details than the backtrace.

I think you have been clear, that is the result of running the "./blender --debug-gpu --debug-gpu-shaders --factory-startup &> startup-log.txt" command string in the console after entering the blender 2.8 directory... something I have to do differently (you know, I'm very bad at linux scripting and stuff)?

Yes, there should be a file named startup-log.txt that you can attach here.

Of course you are right. :)
Here it is.

Brecht Van Lommel (brecht) raised the priority of this task from 30 to Normal.Aug 10 2018, 7:39 PM

This shader error seems like a driver bug related to textureGather() in the object_outline_detect_frag.glsl shader. The error happens on line (0), which doesn't really make sense and probably means it's in some code generated by the driver.

There's a similar error here, where the workaround was to disable textureGather() on NVIDIA:
https://github.com/Unvanquished/Unvanquished/issues/919

@Clément Foucault (fclem), It appears the 340.x driver is the latest supported NVIDIA driver versions for this GPU, so it seems this will not be fixed anymore. Perhaps we can add a workaround to disable texture gather on such old NVIDIA drivers? Maybe any NVIDIA GPU with OpenGL version < 4 or something like that.