Similar to bug #880671 Blender crashes on start. This is the version installed with the USE flags set: Installed versions: 4.1.1-r2(4.1)^t(10:42:01 AM 07/22/2024)(X bullet color-management cycles cycles-bin-kernels embree ffmpeg fftw fluid gmp jpeg2k nanovdb nls oidn openexr openmp opensubdiv openvdb otf pdf potrace pugixml pulseaudio sdl sndfile tbb tiff vulkan wayland webp -alembic -collada -cuda -debug -doc -experimental -gnome -hip -jack -jemalloc -man -ndof -oneapi -openal -openpgl -optix -osl -renderdoc -test -valgrind LLVM_SLOT="17 -15 -16 -18" PYTHON_SINGLE_TARGET="python3_12 -python3_11") I'm running current stable plasma, the window manager being kde-plasma/kwin-5.27.11-r1. I'm mentioning the window manager, since the backtrace points to an issue related to that: Core was generated by `blender-4.1'. Program terminated with signal SIGSEGV, Segmentation fault. #0 wm_window_set_drawable (activate=false, win=0x0, wm=0x56521a8a4288) at /home/portage/media-gfx/blender-4.1.1-r2/work/blender-4.1.1/source/blender/windowmanager/intern/wm_window.cc:1249 warning: 1249 /home/portage/media-gfx/blender-4.1.1-r2/work/blender-4.1.1/source/blender/windowmanager/intern/wm_window.cc: No such file or directory [Current thread is 1 (Thread 0x7f269f407000 (LWP 10761))] (gdb) bt #0 wm_window_set_drawable (activate=false, win=0x0, wm=0x56521a8a4288) at /home/portage/media-gfx/blender-4.1.1-r2/work/blender-4.1.1/source/blender/windowmanager/intern/wm_window.cc:1249 #1 wm_window_ghostwindow_add (title=0x5652159ba3f4 "Blender", is_dialog=<optimized out>, win=0x56521a8a4858, wm=0x56521a8a4288) at /home/portage/media-gfx/blender-4.1.1-r2/work/blender-4.1.1/source/blender/windowmanager/intern/wm_window.cc:799 #2 wm_window_ghostwindow_ensure (wm=0x56521a8a4288, win=0x56521a8a4858, is_dialog=<optimized out>) at /home/portage/media-gfx/blender-4.1.1-r2/work/blender-4.1.1/source/blender/windowmanager/intern/wm_window.cc:831 #3 0x0000565213087e95 in wm_window_ghostwindows_ensure (wm=wm@entry=0x56521a8a4288) at /home/portage/media-gfx/blender-4.1.1-r2/work/blender-4.1.1/source/blender/windowmanager/intern/wm_window.cc:888 #4 0x000056521304c098 in WM_check (C=C@entry=0x565219ffeba8) at /home/portage/media-gfx/blender-4.1.1-r2/work/blender-4.1.1/source/blender/windowmanager/intern/wm.cc:501 #5 0x00005652130647e8 in wm_homefile_read_ex (C=C@entry=0x565219ffeba8, params_homefile=params_homefile@entry=0x7ffcf1522960, reports=reports@entry=0x0, r_params_file_read_post=r_params_file_read_post@entry=0x7ffcf1522958) at /home/portage/media-gfx/blender-4.1.1-r2/work/blender-4.1.1/source/blender/windowmanager/intern/wm_files.cc:1481 #6 0x0000565213069204 in WM_init (C=C@entry=0x565219ffeba8, argc=argc@entry=1, argv=argv@entry=0x7ffcf1522b38) at /home/portage/media-gfx/blender-4.1.1-r2/work/blender-4.1.1/source/blender/windowmanager/intern/wm_init_exit.cc:287 #7 0x0000565212844be0 in main (argc=1, argv=0x7ffcf1522b38) at /home/portage/media-gfx/blender-4.1.1-r2/work/blender-4.1.1/source/creator/creator.cc:525
Created attachment 898099 [details] emerge --info
Created attachment 898100 [details] backtrace
My system was upgraded to LLVM/Clang 18, and due to the LLVM_SLOT change blender was rebuilt. The behaviour persists, and the backtrace looks the same: Program terminated with signal SIGSEGV, Segmentation fault. #0 wm_window_set_drawable (activate=false, win=0x0, wm=0x55689b27bff8) at /home/portage/media-gfx/blender-4.1.1-r2/work/blender-4.1.1/source/blender/windowmanager/intern/wm_window.cc:1249 warning: 1249 /home/portage/media-gfx/blender-4.1.1-r2/work/blender-4.1.1/source/blender/windowmanager/intern/wm_window.cc: No such file or directory [Current thread is 1 (Thread 0x7f44c0166000 (LWP 19249))] (gdb) bt #0 wm_window_set_drawable (activate=false, win=0x0, wm=0x55689b27bff8) at /home/portage/media-gfx/blender-4.1.1-r2/work/blender-4.1.1/source/blender/windowmanager/intern/wm_window.cc:1249 #1 wm_window_ghostwindow_add (title=0x55689702b3f4 "Blender", is_dialog=<optimized out>, win=0x55689b27c5c8, wm=0x55689b27bff8) at /home/portage/media-gfx/blender-4.1.1-r2/work/blender-4.1.1/source/blender/windowmanager/intern/wm_window.cc:799 #2 wm_window_ghostwindow_ensure (wm=0x55689b27bff8, win=0x55689b27c5c8, is_dialog=<optimized out>) at /home/portage/media-gfx/blender-4.1.1-r2/work/blender-4.1.1/source/blender/windowmanager/intern/wm_window.cc:831 #3 0x00005568946f8e95 in wm_window_ghostwindows_ensure (wm=wm@entry=0x55689b27bff8) at /home/portage/media-gfx/blender-4.1.1-r2/work/blender-4.1.1/source/blender/windowmanager/intern/wm_window.cc:888 #4 0x00005568946bd098 in WM_check (C=C@entry=0x55689a9d6ba8) at /home/portage/media-gfx/blender-4.1.1-r2/work/blender-4.1.1/source/blender/windowmanager/intern/wm.cc:501 #5 0x00005568946d57e8 in wm_homefile_read_ex (C=C@entry=0x55689a9d6ba8, params_homefile=params_homefile@entry=0x7ffcbcce61f0, reports=reports@entry=0x0, r_params_file_read_post=r_params_file_read_post@entry=0x7ffcbcce61e8) at /home/portage/media-gfx/blender-4.1.1-r2/work/blender-4.1.1/source/blender/windowmanager/intern/wm_files.cc:1481 #6 0x00005568946da204 in WM_init (C=C@entry=0x55689a9d6ba8, argc=argc@entry=1, argv=argv@entry=0x7ffcbcce63c8) at /home/portage/media-gfx/blender-4.1.1-r2/work/blender-4.1.1/source/blender/windowmanager/intern/wm_init_exit.cc:287 #7 0x0000556893eb5be0 in main (argc=1, argv=0x7ffcbcce63c8) at /home/portage/media-gfx/blender-4.1.1-r2/work/blender-4.1.1/source/creator/creator.cc:525
As I said, I really don't think this to do with LLVM at all. The crash looks completely different to the usual ones for that class of problem. It coming up in Void as https://github.com/void-linux/void-packages/issues/49763 supports that theory too.
According to https://projects.blender.org/blender/blender/issues/126136 really seems to be caused by unsupported (non-dedicated) GPU?
(In reply to Andreas Sturmlechner from comment #5) > According to > > https://projects.blender.org/blender/blender/issues/126136 > > really seems to be caused by unsupported (non-dedicated) GPU? It seems so, I have a Sandy Bridge integrated GPU, which is no longer supported. But this shouldn't lead to crash... I tried downgrading to the stable 3.6 branch, but it forces Python 3.10 or Python 3.11, while the current stable Python is 3.12. I wouldn't downgrade Python just to get Blender working. Is there a way to add Python 3.12 support to the Blender 3.6.15 ebuild?
You can have multiple python versions installed on you system at the same time. So you don't have to abandon python 3.12 if you want to run older blender versions. If you just want to test if 3.6 still works, then you can download and run the official release: https://www.blender.org/download/lts/3-6/#versions You can also try the latest 4.3 daily build and see if you get the unsupported GPU popup on X11: https://builder.blender.org/download/daily/
Thank you for the tips Sebastian. (In reply to Sebastian Parborg from comment #7) > You can have multiple python versions installed on you system at the same > time. > So you don't have to abandon python 3.12 if you want to run older blender > versions. Sure, but the problem I see is with the PYTHON_SINGLE_TARGET, since it's not only blender that needs it set to Python 3.11, but also it's dependencies. I didn't go down the rabbit hole of checking if it would work, it might, but it's a lot of work, and it makes my setup more complex. > > If you just want to test if 3.6 still works, then you can download and run > the official release: https://www.blender.org/download/lts/3-6/#versions Yes, 3.6 works on my very old system. > > You can also try the latest 4.3 daily build and see if you get the > unsupported GPU popup on X11: https://builder.blender.org/download/daily/ Indeed, the latest build doesn't crash, and I do get the unsupported GPU popup.
I'm planning on adding a "blender-bin" package in the future. This should make it much easier to have multiple versions or older installed at the same time. Lori, do you perhaps want to work with me on finishing up the "blender-bin" ebuilds? Here is my current ebuild that grabs the latest daily binary builds: https://projects.blender.org/ZedDB/blender-studio-overlay/src/branch/master/media-gfx/blender-bin/blender-bin-9999.ebuild You can already use it to download any release of Blender by using the "BLENDER_BIN_URL" environment variable. This way, you can install the official 3.6 release via portage.
Having a -bin package is a great idea, thanks for creating it. I added the whole blender overlay to my system the Gentoo way: sudo eselect repository add blender-studio-overlay git https://projects.blender.org/ZedDB/blender-studio-overlay Then I tried to emerge the package, taking the download URL from the web site, like this: sudo env BLENDER_BIN_URL="https://www.blender.org/download/release/Blender3.6/blender-3.6.15-linux-x64.tar.xz" emerge -av blender-bin This failed however, since that link goes to a redirect first that wget doesn't handle well. So I tracked down a direct link, setting BLENDER_BIN_URL="https://download.blender.org/release/Blender3.6/blender-3.6.15-linux-x64.tar.xz", and that worked! I can successfully launch blender from my KDE start menu, so the desktop integration works for me. Is there anything that I can help you with to finalize this ebuild and get it upstreamed?
It is mostly cleaning up the ebuild and creating non live versions of it that can be slotted. Not too hard, but I have a lot of things I'm tied up with ATM my self.
