Fedora Account System
Red Hat Associate
Red Hat Customer
blender: symbol lookup error: /lib64/libclang-cpp.so.19.1: undefined symbol: LLVMInitializePowerPCAsmPrinter, version LLVM_19.1 Reproducible: Always Steps to Reproduce: 1.blender Actual Results: Not working Expected Results: That it works, or at least that error doesn't appear. ~ blender blender: symbol lookup error: /lib64/libclang-cpp.so.19.1: undefined symbol: LLVMInitializePowerPCAsmPrinter, version LLVM_19.1 ~ nm -D /lib64/libLLVM.so.19.1 | grep -i LLVMInitialize 00000000049991b0 T LLVMInitializeAMDGPUAsmParser@@LLVM_19.1 000000000467ad30 T LLVMInitializeAMDGPUAsmPrinter@@LLVM_19.1 00000000049eb120 T LLVMInitializeAMDGPUDisassembler@@LLVM_19.1 00000000047e80e0 T LLVMInitializeAMDGPUTarget@@LLVM_19.1 0000000004ad8260 T LLVMInitializeAMDGPUTargetInfo@@LLVM_19.1 0000000004acfa80 T LLVMInitializeAMDGPUTargetMC@@LLVM_19.1 0000000004a64430 T LLVMInitializeAMDGPUTargetMCA@@LLVM_19.1 0000000004b2ef70 T LLVMInitializeBPFAsmParser@@LLVM_19.1 0000000004afcb40 T LLVMInitializeBPFAsmPrinter@@LLVM_19.1 0000000004b31620 T LLVMInitializeBPFDisassembler@@LLVM_19.1 0000000004b0d900 T LLVMInitializeBPFTarget@@LLVM_19.1 0000000004b357a0 T LLVMInitializeBPFTargetInfo@@LLVM_19.1 0000000004b33600 T LLVMInitializeBPFTargetMC@@LLVM_19.1 00000000027c4500 T LLVMInitializeFunctionPassManager@@LLVM_19.1 00000000044b59e0 T LLVMInitializeMCJITCompilerOptions@@LLVM_19.1 0000000004b9fad0 T LLVMInitializeWebAssemblyAsmParser@@LLVM_19.1 0000000004b39c40 T LLVMInitializeWebAssemblyAsmPrinter@@LLVM_19.1 0000000004ba82f0 T LLVMInitializeWebAssemblyDisassembler@@LLVM_19.1 0000000004b91410 T LLVMInitializeWebAssemblyTarget@@LLVM_19.1 0000000004baf400 T LLVMInitializeWebAssemblyTargetInfo@@LLVM_19.1 0000000004bad090 T LLVMInitializeWebAssemblyTargetMC@@LLVM_19.1 0000000004e6c930 T LLVMInitializeX86AsmParser@@LLVM_19.1 0000000004bb3110 T LLVMInitializeX86AsmPrinter@@LLVM_19.1 0000000004e870a0 T LLVMInitializeX86Disassembler@@LLVM_19.1 0000000004e28d90 T LLVMInitializeX86Target@@LLVM_19.1 0000000004ead7b0 T LLVMInitializeX86TargetInfo@@LLVM_19.1 0000000004ea2fe0 T LLVMInitializeX86TargetMC@@LLVM_19.1 0000000004e8a1a0 T LLVMInitializeX86TargetMCA@@LLVM_19.1
FEDORA-2025-13d9605fa0 (blender-4.4.0-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-13d9605fa0
FEDORA-2025-7d46c08fda (blender-4.2.8-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2025-7d46c08fda
FEDORA-2025-13d9605fa0 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-13d9605fa0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-13d9605fa0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-7d46c08fda has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-7d46c08fda` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-7d46c08fda See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-4a498908a2 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-4a498908a2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-4a498908a2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
That command caused me to run out of free space. Updating the entire system isn't helpful. I'd like to update only the packages that fix Blender; I don't have any free space.
(In reply to passymas from comment #6) > I'd like to update only the packages that fix Blender; I don't have any free > space. That should be already be what the command with --advisory does. Blender is a rather large package, and updating it will unavoidably require quite a bit of temporary storage.
I managed to download all the packages into RAM so as not to use disk space, but it gives me an error and doesn't allow me to update. Blender still has the same error. blender blender: symbol lookup error: /lib64/libclang-cpp.so.19.1: undefined symbol: LLVMInitializePowerPCAsmPrinter, version LLVM_19.1
I was getting an error that didn't allow me to update, then I was able to update, but I still have the same Blender error.
blender --advisory blender: symbol lookup error: /lib64/libclang-cpp.so.19.1: undefined symbol: LLVMInitializePowerPCAsmPrinter, version LLVM_19.1 ~ dnf upgrade --enablerepo=updates-testing --refresh --advisory Missing value for named argument "--advisory". Add "--help" for more information about the arguments.
Right, see one of the automated comments from Fedora Update System for the proper use of --advisory to name a particular update.
dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-13d9605fa0 Updating and loading repositories: Fedora 40 - x86_64 100% | 4.1 KiB/s | 6.1 KiB | 00m01s Fedora rawhide - x86_64 - Test Updates 100% | 27.0 KiB/s | 53.4 KiB | 00m02s Fedora - Rawhide - Developmental packages for the next Fedora release 100% | 38.3 KiB/s | 53.4 KiB | 00m01s brave 100% | 13.2 KiB/s | 2.0 KiB | 00m00s google-chrome 100% | 17.4 KiB/s | 1.3 KiB | 00m00s microsoft-edge 100% | 5.4 KiB/s | 1.5 KiB | 00m00s opera-browser 100% | 4.1 KiB/s | 3.0 KiB | 00m01s RPM Fusion for Fedora Rawhide - Free 100% | 1.6 KiB/s | 2.2 KiB | 00m01s RPM Fusion for Fedora Rawhide - Nonfree 100% | 2.7 KiB/s | 2.6 KiB | 00m01s vivaldi-browser 100% | 35.4 KiB/s | 3.0 KiB | 00m00s teams 100% | 6.2 KiB/s | 1.5 KiB | 00m00s Terra rawhide 100% | 5.2 KiB/s | 6.0 KiB | 00m01s vscode 100% | 15.9 KiB/s | 1.5 KiB | 00m00s yandex-browser 100% | 1.6 KiB/s | 3.0 KiB | 00m02s google-chrome 100% | 29.1 KiB/s | 3.2 KiB | 00m00s Repositories loaded. Nothing to do.
So what the bot does is show the program updates in this issue, even if the issue has not been resolved? The problem persists.
While they fix Blender I'll take advantage of this space to say by the way, I visited your website musicinmybrain.net and it's not working "No page found".
(In reply to passymas from comment #14) > So what the bot does is show the program updates in this issue, even if the > issue has not been resolved? > > The problem persists. The bot reports that an update *that someone specifically associated with this bug* is available for testing. Eventually, it will report when the update reaches stable repos, too. So, if (as it appears from the output you pasted), you are running Fedora 40, and you followed the instructions in https://bugzilla.redhat.com/show_bug.cgi?id=2356053#c4 and ran `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-7d46c08fda`, the update installed successfully, and now the problem is still present, then it suggests that either the update was supposed to fix the bug but didn’t, or someone made an error in associating the bug with that particular update. I notice that updates for all Fedora releases are all associated with all open bugs for Blender. That doesn’t seem strictly correct, since some of them ship different versions than others. While I’m formally a co-maintainer of the blender package in Fedora, this is mostly because I frequently need to rebuild it for dependency updates, and I haven’t always been able to do that as a provenpackager. I do help fix bugs occasionally when I can, but I don’t consider myself a primary maintainer, and I don’t like to spend a lot of time on the package. I tried to reproduce what you’re seeing in an emulated ppc64le chroot on my x86_64 workstation as follows: $ mock -r fedora-40-ppc64le --clean $ mock -r fedora-40-ppc64le -i blender $ mock -r fedora-40-ppc64le --chroot 'blender --help' This printed the help output as expected. Then I tried again with $ mock -r fedora-40-ppc64le -i blender xorg-x11-server-Xvfb $ mock -r fedora-40-ppc64le --chroot 'xvfb-run -- blender' There were some complaints about XDG_RUNTIME_DIR and home directory accessibility due to the weird environment I was using, but the program seemed to start up in the invisible-to-me X11 session provided by xvfb-run without crashing. The next step in trying to reproduce this would be to try to install and launch blender in a full interactive virtual machine under qemu emulation. This is easy enough to do via virt-manager, but it’s unlikely this will be enough of a priority for me personally to attempt it in the near future. > While they fix Blender I'll take advantage of this space to say by the way, I visited your website musicinmybrain.net and it's not working "No page found". Thanks. This is intentional. I have used the domain for email and other purposes for many years, but it has never hosted a web site.
The problem is with the dependency libLLVM.so.19.1, which doesn't have the symbol LLVMInitializePowerPCAsmPrinter, it would be good to remove PowerPC support for the x86_64 architecture, I don't know the purpose of including other architectures in x86_64, that prevents Blender from working on x86_64. I tried to run those commands and got a pretty strange metalink error. /usr/bin/dnf5 --installroot /var/lib/mock/fedora-rawhide-ppc64le/root/ --releasever 43 install @buildsys-build --setopt=deltarpm=False --setopt=allow_vendor_change=yes --allowerasing --forcearch ppc64le Updating and loading repositories: fedora 100% | 13.7 KiB/s | 12.0 KiB | 00m01s Repositories loaded. Package "tar-2:1.35-5.fc42.ppc64le" is already installed. Package "bzip2-1.0.8-20.fc42.ppc64le" is already installed. Package "redhat-rpm-config-342-2.fc42.noarch" is already installed. Package "rpm-build-4.20.1-3.fc43.ppc64le" is already installed. Package "unzip-6.0-66.fc42.ppc64le" is already installed. Package "cpio-2.15-2.fc41.ppc64le" is already installed. Package "which-2.23-1.fc42.ppc64le" is already installed. Package "bash-5.2.37-3.fc43.ppc64le" is already installed. Package "coreutils-9.6-2.fc43.ppc64le" is already installed. Package "grep-3.11-10.fc42.ppc64le" is already installed. Package "patch-2.8-1.fc43.ppc64le" is already installed. Package "sed-4.9-4.fc42.ppc64le" is already installed. Package "shadow-utils-2:4.17.4-1.fc43.ppc64le" is already installed. Package "util-linux-2.40.4-7.fc43.ppc64le" is already installed. Package "diffutils-3.11-3.fc43.ppc64le" is already installed. Package "fedora-release-common-43-0.8.noarch" is already installed. Package "findutils-1:4.10.0-5.fc42.ppc64le" is already installed. Package "gawk-5.3.1-1.fc42.ppc64le" is already installed. Package "glibc-minimal-langpack-2.41.9000-7.fc43.ppc64le" is already installed. Package "gzip-1.13-3.fc42.ppc64le" is already installed. Package "info-7.2-3.fc42.ppc64le" is already installed. Package "xz-1:5.8.0-1.fc43.ppc64le" is already installed. Package Arch Version Repository Size Installing groups: Buildsystem building group Transaction Summary: After this operation, 0 B extra will be used (install 0 B, remove 0 B). Running transaction Complete! ---- mock -r fedora-43-ppc64le --chroot 'blender --help' INFO: Unable to build arch ppc64le natively on arch x86_64. Setting forcearch to use software emulation. INFO: mock.py version 6.1 starting (python version = 3.13.2, NVR = mock-6.1-1.fc43), args: /usr/libexec/mock/mock -r fedora-43-ppc64le --chroot 'blender --help' Start(bootstrap): init plugins INFO: selinux disabled Finish(bootstrap): init plugins Start: init plugins INFO: selinux disabled Finish: init plugins INFO: Signal handler active Start: run Mock Version: 6.1 INFO: Mock Version: 6.1 Start(bootstrap): chroot init INFO: calling preinit hooks INFO: enabled root cache INFO: enabled package manager cache Start(bootstrap): cleaning package manager metadata Finish(bootstrap): cleaning package manager metadata INFO: Package manager dnf5 detected and used (fallback) Finish(bootstrap): chroot init Start: chroot init INFO: calling preinit hooks INFO: enabled root cache INFO: enabled package manager cache Start: cleaning package manager metadata Finish: cleaning package manager metadata INFO: enabled HW Info plugin INFO: Package manager dnf5 detected and used (direct choice) Start: installing minimal buildroot with dnf5 Updating and loading repositories: fedora ???% | 0.0 B/s | 0.0 B | 00m00s >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Librepo error: Cannot prepare internal mirrorlist: Curl error (6): Could not Failed to download metadata (metalink: "https://mirrors.fedoraproject.org/metalink?repo=rawhide&arch=ppc64le") for repository "fedora" Librepo error: Cannot prepare internal mirrorlist: Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject.org/metalink?repo=rawhide&arch=ppc64le [Could not resolve host: mirrors.fedoraproject.org] ERROR: Command failed: # /usr/bin/dnf5 --installroot /var/lib/mock/fedora-rawhide-ppc64le/root/ --releasever 43 install @buildsys-build --setopt=deltarpm=False --setopt=allow_vendor_change=yes --allowerasing --forcearch ppc64le Updating and loading repositories: fedora ???% | 0.0 B/s | 0.0 B | 00m00s >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject >>> Librepo error: Cannot prepare internal mirrorlist: Curl error (6): Could not Failed to download metadata (metalink: "https://mirrors.fedoraproject.org/metalink?repo=rawhide&arch=ppc64le") for repository "fedora" Librepo error: Cannot prepare internal mirrorlist: Curl error (6): Could not resolve hostname for https://mirrors.fedoraproject.org/metalink?repo=rawhide&arch=ppc64le [Could not resolve host: mirrors.fedoraproject.org]
Sorry, I was confused. I missed that you are on x86_64. I thought you were running PowerPC and this was a PowerPC bug. Then I have been going about trying to reproduce this incorrectly.
I did a test with the annocheck command on the LLVM library and got these errors, maybe it helps. annocheck --ignore-unknown --verbose --profile=rawhide --debug-dir=/usr/lib/debug/ /lib64/libLLVM.so.19.1 annocheck: Version 12.93. Hardened: /lib64/libLLVM.so.19.1: PASS: pie test because the ELF file header has the correct type Hardened: /lib64/libLLVM.so.19.1: PASS: writable-got test Hardened: /lib64/libLLVM.so.19.1: PASS: dynamic-segment test Hardened: /lib64/libLLVM.so.19.1: FAIL: bind-now test because not linked with -Wl,-z,now Hardened: /lib64/libLLVM.so.19.1: info: For more information visit: https://sourceware.org/annobin/annobin.html/Test-bind-now.html Hardened: /lib64/libLLVM.so.19.1: info: seen tool Clang version 19. Hardened: /lib64/libLLVM.so.19.1: info: seen tool GCC version 14. Hardened: /lib64/libLLVM.so.19.1: skip: entry test because shared libraries do not use entry points Hardened: /lib64/libLLVM.so.19.1: PASS: gnu-relro test Hardened: /lib64/libLLVM.so.19.1: PASS: gnu-stack test because stack segment exists with the correct permissions Hardened: /lib64/libLLVM.so.19.1: skip: gaps test because no notes found - therefore there are no gaps! Hardened: /lib64/libLLVM.so.19.1: MAYB: test: notes, reason: notes not found and no DWARF info found (could there be a separate debuginfo file ?) Hardened: /lib64/libLLVM.so.19.1: info: For more information visit: https://sourceware.org/annobin/annobin.html/Test-notes.html Hardened: /lib64/libLLVM.so.19.1: skip: branch-protection test because not an AArch64 binary Hardened: /lib64/libLLVM.so.19.1: FAIL: cf-protection test because no .note.gnu.property section = no control flow information Hardened: /lib64/libLLVM.so.19.1: info: For more information visit: https://sourceware.org/annobin/annobin.html/Test-cf-protection.html Hardened: /lib64/libLLVM.so.19.1: skip: dynamic-tags test because AArch64 specific Hardened: /lib64/libLLVM.so.19.1: PASS: fast test because no negative result detected Hardened: /lib64/libLLVM.so.19.1: skip: fortify test because no compiled C/C++ code found Hardened: /lib64/libLLVM.so.19.1: skip: glibcxx-assertions test because source language not C++ Hardened: /lib64/libLLVM.so.19.1: skip: go-revision test because no GO compiled code found Hardened: /lib64/libLLVM.so.19.1: skip: implicit-values test because These tests are only relevent to C source code Hardened: /lib64/libLLVM.so.19.1: PASS: instrumentation test because no negative result detected Hardened: /lib64/libLLVM.so.19.1: PASS: load-segments test because no negative result detected Hardened: /lib64/libLLVM.so.19.1: skip: lto test because not compiled from C/C++ code Hardened: /lib64/libLLVM.so.19.1: MAYB: test: optimization, reason: annobin notes regarding this feature not found Hardened: /lib64/libLLVM.so.19.1: info: For more information visit: https://sourceware.org/annobin/annobin.html/Test-optimization.html Hardened: /lib64/libLLVM.so.19.1: WARN: no annnobin notes were found - could they be in a separate file ? Hardened: /lib64/libLLVM.so.19.1: MAYB: test: pic, reason: no valid notes found regarding this test Hardened: /lib64/libLLVM.so.19.1: info: For more information visit: https://sourceware.org/annobin/annobin.html/Test-pic.html Hardened: /lib64/libLLVM.so.19.1: PASS: production test because no negative result detected Hardened: /lib64/libLLVM.so.19.1: FAIL: property-note test because no .note.gnu.property section found Hardened: /lib64/libLLVM.so.19.1: info: For more information visit: https://sourceware.org/annobin/annobin.html/Test-property-note.html Hardened: /lib64/libLLVM.so.19.1: PASS: run-path test because no negative result detected Hardened: /lib64/libLLVM.so.19.1: PASS: short-enums test because no negative result detected Hardened: /lib64/libLLVM.so.19.1: MAYB: test: stack-clash, reason: annobin notes regarding this feature not found Hardened: /lib64/libLLVM.so.19.1: info: For more information visit: https://sourceware.org/annobin/annobin.html/Test-stack-clash.html Hardened: /lib64/libLLVM.so.19.1: WARN: no annnobin notes were found - could they be in a separate file ? Hardened: /lib64/libLLVM.so.19.1: MAYB: test: stack-prot, reason: annobin notes regarding this feature not found Hardened: /lib64/libLLVM.so.19.1: info: For more information visit: https://sourceware.org/annobin/annobin.html/Test-stack-prot.html Hardened: /lib64/libLLVM.so.19.1: WARN: no annnobin notes were found - could they be in a separate file ? Hardened: /lib64/libLLVM.so.19.1: skip: stack-realign test because not an i686 executable Hardened: /lib64/libLLVM.so.19.1: PASS: textrel test because no negative result detected Hardened: /lib64/libLLVM.so.19.1: PASS: threads test because no negative result detected Hardened: /lib64/libLLVM.so.19.1: PASS: unicode test because no negative result detected Hardened: /lib64/libLLVM.so.19.1: skip: warnings test because no compiled C/C++ code found Hardened: /lib64/libLLVM.so.19.1: Overall: FAIL.
Created attachment 2083354 [details] Blender running on Rawhide through GNOME Boxes I vainly tried to reproduce the issue on Rawhide as the LLVM PowerPC part is very odd. Blender uses LLVM 18 hence LLVM18 needed for HIP from the spec file: "https://src.fedoraproject.org/rpms/blender/blob/rawhide/f/blender.spec#_33" suggesting a possible clash between two version of LLVM during an update in your system. Can you tried to reinstall Blender and LLVM or distro-sync to see if the problem goes away in Rawhide?
FEDORA-2025-13d9605fa0 (blender-4.4.0-3.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
I reinstalled LLVM and Blender and the problem persists. Blender depends on liboslcomp.so.1.13.12, which depends on LLVM 19. BuildRequires: pkgconfig(oslcomp) ~ ldd /lib64/liboslcomp.so.1.13.12 linux-vdso.so.1 (0x00007ffedcdb9000) libclang-cpp.so.19.1 => /lib64/libclang-cpp.so.19.1 (0x00007f49e8e0f000) libLLVM.so.19.1 => /lib64/libLLVM.so.19.1 (0x00007f49e385b000) libOpenImageIO_Util.so.2.5 => /lib64/libOpenImageIO_Util.so.2.5 (0x00007f49e3753000) libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f49e34dd000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f49e34b1000) libc.so.6 => /lib64/libc.so.6 (0x00007f49e32be000) libm.so.6 => /lib64/libm.so.6 (0x00007f49e31ce000) /lib64/ld-linux-x86-64.so.2 (0x00007f49ed649000) libffi.so.8 => /lib64/libffi.so.8 (0x00007f49e31be000) libedit.so.0 => /lib64/libedit.so.0 (0x00007f49e3183000) libz.so.1 => /lib64/libz.so.1 (0x00007f49e3160000) libzstd.so.1 => /lib64/libzstd.so.1 (0x00007f49e309c000) libxml2.so.2 => /lib64/libxml2.so.2 (0x00007f49e2f37000) libImath-3_1.so.29 => /lib64/libImath-3_1.so.29 (0x00007f49e2ee7000) libboost_thread.so.1.83.0 => /lib64/libboost_thread.so.1.83.0 (0x00007f49e2ec6000) libtbb.so.2 => /lib64/libtbb.so.2 (0x00007f49e2e86000) libtinfo.so.6 => /lib64/libtinfo.so.6 (0x00007f49e2e59000) liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f49e2e22000)
Can you test this scratch build https://koji.fedoraproject.org/koji/taskinfo?taskID=131110845 to see if that resolves the issue?
The above build uses LLVM18.
What command do I use to install it? I don't understand.
The scratch build of openshadinglanguage package which includes liboslcomp.so.1.13.12 depends on llvm18. Install that version and see if the failure goes away.
I don't know what the command is to install a scratch build... Besides, it's the same build that LLVM19 uses. I still don't understand.
Select the x86_64 from the link (https://koji.fedoraproject.org/koji/taskinfo?taskID=131110889) and choose openshadinglanguage-libs to update. Alternatively, here is the short command ' sudo dnf upgrade https://kojipkgs.fedoraproject.org//work/tasks/889/131110889/openshadinglanguage-libs-1.13.12.0-5.fc43.x86_64.rpm ' That build depends on llvm18 instead of llvm19. We need to narrow down the issue
Thank you very much, I think I should close the issue now... It's not completely fixed, but the error no longer appears. I don't know why this happens, it must be some video driver problem. blender Illegal instruction (core dumped) If there was a better way to know why this happens, that would be nice.
dmesg traps: blender[40951] trap invalid opcode ip:55dd1ec36718 sp:7ffe28930110 error:0 in blender[55dd1e90e000+360f000]
Ok, glad to read the error went away.
FEDORA-2025-7d46c08fda (blender-4.2.8-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-4a498908a2 (blender-4.4.0-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.