Description of problem: Just attempting to launch blender Version-Release number of selected component: blender-1:2.93.4-1.fc34 Additional info: reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-blender-249284.scope cmdline: blender crash_function: std::__replacement_assert executable: /usr/bin/blender journald_cursor: s=ddbc815615424ba889b26a0bcf96f8f3;i=29c973;b=8d64d080c9144fbcbd3560dd4a6e4bc8;m=19fe18b0be;t=5ce57a68c3316;x=77c180641e9cf2e3 kernel: 5.14.10-200.fc34.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 1938324
Created attachment 1833186 [details] File: backtrace
Created attachment 1833187 [details] File: core_backtrace
Created attachment 1833188 [details] File: cpuinfo
Created attachment 1833189 [details] File: dso_list
Created attachment 1833190 [details] File: environ
Created attachment 1833191 [details] File: limits
Created attachment 1833192 [details] File: maps
Created attachment 1833193 [details] File: mountinfo
Created attachment 1833194 [details] File: open_fds
Created attachment 1833195 [details] File: proc_pid_status
sudo lshw -sanitize -C video *-display description: VGA compatible controller product: GF119 [GeForce GT 610] vendor: NVIDIA Corporation physical id: 0 bus info: pci@0000:09:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:79 memory:fb000000-fbffffff memory:e0000000-e7ffffff memory:e8000000-e9ffffff ioport:f000(size=128) memory:c0000-dffff
Hello Mike, Could you test https://bodhi.fedoraproject.org/updates/FEDORA-2021-dd777cc251 ?
Still crashing, on launch: blender --verbose 1000 Color management: using fallback mode for management Color management: Error could not find role data role. Color management: scene view "Filmic" not found, setting default "Standard". I1015 21:01:34.472770 219275 blender_python.cpp:195] Debug flags initialized to: CPU flags: AVX2 : True AVX : True SSE4.1 : True SSE3 : True SSE2 : True BVH layout : EMBREE Split : False CUDA flags: Adaptive Compile : False OptiX flags: CUDA streams : 1 OpenCL flags: Device type : ALL Debug : False Memory limit : 0 /usr/include/c++/11/bits/stl_deque.h:1328: std::deque<_Tp, _Alloc>::reference std::deque<_Tp, _Alloc>::operator[](std::deque<_Tp, _Alloc>::size_type) [with _Tp = nv50_ir::ValueRef; _Alloc = std::allocator<nv50_ir::ValueRef>; std::deque<_Tp, _Alloc>::reference = nv50_ir::ValueRef&; std::deque<_Tp, _Alloc>::size_type = long unsigned int]: Assertion '__n < this->size()' failed. [1] 219275 IOT instruction (core dumped) blender --verbose 1000
"/usr/include/c++/11/bits/stl_deque.h:1328: std::deque<_Tp, _Alloc>::reference std::deque<_Tp, _Alloc>::operator[](std::deque<_Tp, _Alloc>::size_type) [with _Tp = nv50_ir::ValueRef; _Alloc = std::allocator<nv50_ir::ValueRef>; std::deque<_Tp, _Alloc>::reference = nv50_ir::ValueRef&; std::deque<_Tp, _Alloc>::size_type = long unsigned int]: Assertion '__n < this->size()' failed." It appears a bug related to nouveau driver. Workaround may be using Nvidia driver to check if Blender successfully starts.
It looks like this bug is the same as: https://developer.blender.org/T76583 https://developer.blender.org/T85677 https://developer.blender.org/T85721 The last of those three bugs contains the clearest upstream summary: > For NVIDIA GPUs on Linux, the official recommendation (as also mentioned in the Blender manual) is to use the closed source drivers which do work. We are not currently considering Nouveau drivers to be the officially supported way to run Blender, and so this is not considered a bug we intend to fix in Blender. That’s a really frustrating situation, but I’m not sure there is anything that can be done downstream in Fedora for NVIDIA GPU users. It seems like this should be closed as CANTFIX.
*** Bug 2049376 has been marked as a duplicate of this bug. ***
*** Bug 2036159 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.