Hello,
Version 3.2 crashes. I removed it and reinstalled again. Still crashes.
$ blender
ERROR (gpu.shader): gpu_shader_2D_widget_base FragShader:
|
81 | layout(depth_any) out float gl_FragDepth;
| ^
| Error: unrecognized layout identifier `depth_any'
Writing: /tmp/blender.crash.txt
Segmentation fault (core dumped)
Please advice.
What are you doing that causes it to crash?
More specifically, what happens before the crash? Between opening Blender and the crash, what do you see? What do you do? What do you type, click on, or interact with?
Just started Blender (doubled-click). After it crashed several times I removed it and installed again.
Below is an output of blender.crash.txt
# Blender 3.2.0, Commit date: 2022-06-08 10:22, Hash e05e1e369187
# backtrace
/snap/blender/2474/blender(BLI_system_backtrace+0x20) [0xc1491e0]
/snap/blender/2474/blender() [0x11d8e2a]
/lib/x86_64-linux-gnu/libc.so.6(+0x43090) [0x7f44fc277090]
/snap/blender/2474/blender(GPU_shader_get_builtin_uniform+0) [0xad8a590]
/snap/blender/2474/blender(GPU_matrix_bind+0x1b) [0xad8729b]
/snap/blender/2474/blender(UI_widgetbase_draw_cache_flush+0xb5) [0x23d5e65]
/snap/blender/2474/blender() [0x23d92b2]
/snap/blender/2474/blender(ui_draw_but+0xc9c) [0x23dd30c]
/snap/blender/2474/blender(UI_block_draw+0x2fe) [0x237b95e]
/snap/blender/2474/blender(UI_blocklist_draw+0x34) [0x237b9e4]
/snap/blender/2474/blender(ED_region_header_draw+0x77) [0x1c5fc27]
/snap/blender/2474/blender(ED_region_do_draw+0x841) [0x1c631c1]
/snap/blender/2474/blender(wm_draw_update+0x7a3) [0x179dd13]
/snap/blender/2474/blender(WM_main+0x30) [0x179aa40]
/snap/blender/2474/blender(main+0x322) [0x10d47e2]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f44fc258083]
/snap/blender/2474/blender() [0x11d570c]
# Python backtrace
So you are on Linux… (debian here). You may also give info about distro, version…
This might be a problem with snap? Try the original files from blender.org and do
tar -xJf ~/Downloads/blender-3.2.XYZ-linux-x64.tar.xz
in any folder you like (with the correct name of your download folder and blender archive).
Broken,
Tarball installs but Blender does not start even from command line. When I install snap it starts to load for a split of second then crashes.
Previous version was fine.
It crashes silently ?? See also https://docs.blender.org/manual/en/latest/troubleshooting/crash.html.
I too experience “silent” crashes from 3.2 but in win 10 far more often than 3.1.2, especially while working with geo nodes (I just had 4 in a row) - I did a search for crash.txt files and couldn’t find any…
As I said it crashes during loading Blender.
Usually an update runs in the background, and when load Blender you notice that version has been updated. Same thing happened now, it’s updated after that does not open.
See blender.crash.txt
# Blender 3.2.0, Commit date: 2022-06-08 10:22, Hash e05e1e369187
# backtrace
/snap/blender/2474/blender(BLI_system_backtrace+0x20) [0xc1491e0]
/snap/blender/2474/blender() [0x11d8e2a]
/lib/x86_64-linux-gnu/libc.so.6(+0x43090) [0x7f1d2b849090]
/snap/blender/2474/blender(GPU_shader_get_builtin_uniform+0) [0xad8a590]
/snap/blender/2474/blender(GPU_matrix_bind+0x1b) [0xad8729b]
/snap/blender/2474/blender(UI_widgetbase_draw_cache_flush+0xb5) [0x23d5e65]
/snap/blender/2474/blender() [0x23d92b2]
/snap/blender/2474/blender(ui_draw_but+0xc9c) [0x23dd30c]
/snap/blender/2474/blender(UI_block_draw+0x2fe) [0x237b95e]
/snap/blender/2474/blender(UI_blocklist_draw+0x34) [0x237b9e4]
/snap/blender/2474/blender(ED_region_header_draw+0x77) [0x1c5fc27]
/snap/blender/2474/blender(ED_region_do_draw+0x841) [0x1c631c1]
/snap/blender/2474/blender(wm_draw_update+0x7a3) [0x179dd13]
/snap/blender/2474/blender(WM_main+0x30) [0x179aa40]
/snap/blender/2474/blender(main+0x322) [0x10d47e2]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f1d2b82a083]
/snap/blender/2474/blender() [0x11d570c]
# Python backtrace
We already know your snap version throughs errors (now a little differrent about libc). To isolate the posssible error it would be interesting what the downloaded version has told you… It’s called fault isolation or also analysis of error. Repeating the same thing again if it fails doesn’t help… it just doesn’t work repeatedly.
No warnings, nothing. As I said it upgraded to 3.2 silently. Day before it worked fine, next day it crashed.
When I ran crash file noticed that it’s 3.2.
Is it possible to downgrade or rollback?
I was able to start v. 2.92.0 after $ sudo apt install llvm-6.0
Installed v. 3.0.1 using https://askubuntu.com/questions/1105556/how-to-completely-uninstall-blender
Then this has something to do with snap and incorrect dependencies. I’m running blender on (something older) debian 9 (want to install 11) without any llvm (*Low Level Virtual Machine ) and…
we still don’t know your distro and version… How should we help ?
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.4 LTS
Release: 20.04
Codename: focal