Description of problem: The application crashed at the start. Running from the terminal showed the following: : CommandLine Error: Option 'use-dbg-addr' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options Aborted (core dumped) Version-Release number of selected component: darktable-4.2.1-1.fc38 Additional info: reporter: libreport-2.17.9 type: CCpp reason: darktable killed by SIGABRT journald_cursor: s=e81701c20d6a4afc932b64180bfce799;i=1460d7;b=baff9469eb8f460d930818d5d9b86f7b;m=212b77d62;t=5f8b73bdeba57;x=c05f6969cdd7672e executable: /usr/bin/darktable cmdline: /usr/bin/darktable cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.darktable.darktable-18096.scope rootdir: / uid: 1000 kernel: 6.2.9-300.fc38.x86_64 package: darktable-4.2.1-1.fc38 runlevel: N 5 backtrace_rating: 3 crash_function: llvm::report_fatal_error Truncated backtrace: Thread no. 1 (24 frames) #4 llvm::report_fatal_error at /usr/src/debug/llvm-16.0.0-2.fc38.x86_64/lib/Support/ErrorHandling.cpp:123 #6 (anonymous namespace)::CommandLineParser::addOption at /usr/src/debug/llvm-16.0.0-2.fc38.x86_64/lib/Support/CommandLine.cpp:241 #8 llvm::cl::Option::addArgument at /usr/src/debug/llvm-16.0.0-2.fc38.x86_64/lib/Support/CommandLine.cpp:445 #9 __cxx_global_var_init at /usr/src/debug/llvm-16.0.0-2.fc38.x86_64/lib/IR/DIBuilder.cpp:27 #10 _GLOBAL__sub_I_DIBuilder.cpp #11 call_init at dl-init.c:70 #13 _dl_init at dl-init.c:117 #14 _dl_catch_exception at dl-catch.c:211 #15 dl_open_worker at dl-open.c:808 #16 _dl_catch_exception at dl-catch.c:237 #17 _dl_open at dl-open.c:884 #18 dlopen_doit at dlopen.c:56 #19 _dl_catch_exception at dl-catch.c:237 #20 _dl_catch_error at dl-catch.c:256 #21 _dlerror_run at dlerror.c:138 #22 dlopen_implementation at dlopen.c:71 #23 ___dlopen at dlopen.c:81 #24 khrIcdOsLibraryLoad #25 khrIcdVendorAdd #26 khrIcdOsVendorsEnumerate #27 __pthread_once_slow at pthread_once.c:116 #28 clGetPlatformIDs #29 dt_opencl_init at /usr/src/debug/darktable-4.2.1-1.fc38.x86_64/src/common/opencl.c:921 #30 dt_init at /usr/src/debug/darktable-4.2.1-1.fc38.x86_64/src/common/darktable.c:1177
Created attachment 1956343 [details] File: proc_pid_status
Created attachment 1956344 [details] File: maps
Created attachment 1956345 [details] File: limits
Created attachment 1956346 [details] File: environ
Created attachment 1956347 [details] File: open_fds
Created attachment 1956348 [details] File: mountinfo
Created attachment 1956349 [details] File: os_info
Created attachment 1956350 [details] File: cpuinfo
Created attachment 1956351 [details] File: core_backtrace
Created attachment 1956352 [details] File: dso_list
Created attachment 1956353 [details] File: var_log_messages
Created attachment 1956354 [details] File: backtrace
Hello, it is a llvm bug, read https://github.com/darktable-org/darktable/issues/14145#issuecomment-1500808252 I am changing bugreport component to llvm Cheers
> #24 khrIcdOsLibraryLoad > #25 khrIcdVendorAdd > #26 khrIcdOsVendorsEnumerate @luya_tfz These calls are coming from /opt/rocm-5.4.3/lib/libamd_comgr.so.2.4.50403. This library does not appear to be provided by Fedora because it's installed under /opt. If this is indeed the case, I suggest to report this issue to the provider of this library.
''/opt/rocm-5.4.3/lib/libamd_comgr.so.2.4.50403' comes from ROCm c(RHEL 9.1) repository whose equivalent is rocm-comgr on Fedora (need an update anyway) required by rocm-opencl (available on both Fedora and ROCm). At first, removing rocm-opencl had no effect on the crash. However, removing the installed mesa-libOpenCL allowed Darktable to start properly. sudo dnf remove mesa-libOpenCL Dependencies resolved. ================================================================================ Package Arch Version Repository Size ================================================================================ Removing: mesa-libOpenCL x86_64 23.0.1-2.fc38 @updates-testing 22 M Removing unused dependencies: clang-libs x86_64 16.0.0-2.fc38 @updates-testing 114 M clang-resource-filesystem x86_64 16.0.0-2.fc38 @updates-testing 0 compiler-rt x86_64 16.0.0-1.fc38 @updates-testing 25 M libomp x86_64 16.0.0-1.fc38 @updates-testing 2.1 M libomp-devel x86_64 16.0.0-1.fc38 @updates-testing 17 M Transaction Summary ================================================================================ Remove 6 Packages Freed space: 180 M Is this ok [y/N]: y Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Erasing : mesa-libOpenCL-23.0.1-2.fc38.x86_64 1/6 Erasing : clang-libs-16.0.0-2.fc38.x86_64 2/6 Erasing : libomp-devel-16.0.0-1.fc38.x86_64 3/6 Erasing : compiler-rt-16.0.0-1.fc38.x86_64 4/6 Erasing : clang-resource-filesystem-16.0.0-2.fc38.x86_64 5/6 Erasing : libomp-16.0.0-1.fc38.x86_64 6/6 Verifying : clang-libs-16.0.0-2.fc38.x86_64 1/6 Verifying : clang-resource-filesystem-16.0.0-2.fc38.x86_64 2/6 Verifying : compiler-rt-16.0.0-1.fc38.x86_64 3/6 Verifying : libomp-16.0.0-1.fc38.x86_64 4/6 Verifying : libomp-devel-16.0.0-1.fc38.x86_64 5/6 Verifying : mesa-libOpenCL-23.0.1-2.fc38.x86_64 6/6 Removed: clang-libs-16.0.0-2.fc38.x86_64 clang-resource-filesystem-16.0.0-2.fc38.x86_64 compiler-rt-16.0.0-1.fc38.x86_64 libomp-16.0.0-1.fc38.x86_64 libomp-devel-16.0.0-1.fc38.x86_64 mesa-libOpenCL-23.0.1-2.fc38.x86_64 Complete! Disabling ROCm repository in order to use packages from Fedora repository installed the latest version rocm-opencl so using it still allows Darktable to run. Based on those research, mesa-libOpenCL built with Fedora llvm 15 is the culprit.
(In reply to Luya Tshimbalanga from comment #15) > Disabling ROCm repository in order to use packages from Fedora repository > installed the latest version rocm-opencl so using it still allows Darktable > to run. Based on those research, mesa-libOpenCL built with Fedora llvm 15 is > the culprit. Great! In that case, I'm going to close this bug report. Thanks!