You are not logged in.

#1 2025-09-20 22:27:53

ThePoultryman
Member
Registered: 2025-09-20
Posts: 7

DaVinci Resolve Runtime Crashes

I've installed DaVinci Resolve using davinci-resolve from AUR. I can launch it, and open a project, but if I try to import any media, or click the "edit" or "media" tab, it crashes. When switching to the "edit" or "media" tab, the display does update to reflect it, but only for a moment before immediately crashing.

Output of /home/user/.local/share/DaVinciResolve/logs/ResolveDebug.txt: https://0x0.st/KTdw.txt

Offline

#2 2025-09-21 12:20:06

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,303

Re: DaVinci Resolve Runtime Crashes

Please post the full outputs of


$ lspci -k
$ clinfo
$ eglinfo -B 
$ glxinfo -B

(install clinfo & mesa-utils packages to get the bottom 3 commands)

You are using the linux-zen kernel. Does the crash also happen with stock linux kernel ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#3 2025-09-21 18:22:18

ThePoultryman
Member
Registered: 2025-09-20
Posts: 7

Re: DaVinci Resolve Runtime Crashes

The crash also happen on the stock linux kernel.

For clarity: I'm going to be doing all further testing on the stock kernel, and the following were run on the stock kernel.

lspci -k: https://0x0.st/KA8h.txt
clinfo: https://0x0.st/KA8F.txt
eglinfo -B: https://0x0.st/KAKs.txt
glxinfo -B: https://0x0.st/KAKz.txt

Offline

#4 2025-09-21 18:51:23

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,303

Re: DaVinci Resolve Runtime Crashes

Outputs look fine, looked again at log

qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""

Are you running under wayland ?

Does starting with

QT_QPA_PLATFORM=xcb /opt/resolve/bin/resolve

make a difference ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#5 2025-09-21 23:53:26

ThePoultryman
Member
Registered: 2025-09-20
Posts: 7

Re: DaVinci Resolve Runtime Crashes

I am using Wayland, but using

 QT_QPA_PLATFORM=xcb /opt/resolve/bin/resolve

results in the same behavior. Here is resolve’s output of attempting to run with that command: https://0x0.st/KAbe.txt.

I did notice the following in the log:

Failed to connect to panel socket
DRIVER: open /var/tmp/davinci_socket failed

But I don’t know if that is an issue or if it is relevant to the crash.

Last edited by ThePoultryman (2025-09-22 00:23:14)

Offline

#6 2025-09-22 09:04:49

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,303

Re: DaVinci Resolve Runtime Crashes

Typically software uses a fallback option for such failures.

I noticed both logs end with the same lines

================================
ActCCMessage Already in Table: Code= c005, Mode= 13, Level=  1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c006, Mode= 13, Level=  1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= c007, Mode= 13, Level=  1, CmdKey= -1, Option= 0
ActCCMessage Already in Table: Code= 2282, Mode=  0, Level=  0, CmdKey= 8, Option= 0
log4cxx: No appender could be found for logger (UI).
log4cxx: Please initialize the log4cxx system properly.

Those lines are mentioned on https://wiki.archlinux.org/title/DaVinc … _(wayland) .

Please post the output of pacman -Qs "tbb|oneapi"


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#7 2025-09-22 16:00:14

ThePoultryman
Member
Registered: 2025-09-20
Posts: 7

Re: DaVinci Resolve Runtime Crashes

Output of pacman -Qs "tbb|oneapi":

local/intel-oneapi-common 2024.1.0-1
    Intel's oneAPI common variables and licensing
local/intel-oneapi-compiler-dpcpp-cpp-runtime-libs 2025.0.4-1
    Intel oneAPI Data Parallel C++ compiler: Minimal runtime libraries
local/intel-oneapi-compiler-shared-runtime-libs 2025.0.4-2
    Intel oneAPI compiler runtime libraries: Minimal compiler libraries
local/intel-oneapi-openmp 2025.0.4-1
    Intel oneAPI OpenMP runtime library
local/intel-oneapi-tbb 2021.12.0-2
    Intel oneAPI Threading Building Blocks
local/intel-oneapi-tcm 1.2.0-3
    Thread Composability Manager
local/level-zero-loader 1.24.2-1
    API for accessing low level interfaces in oneAPI platform devices (loader)
local/onetbb 2022.2.0-1
    oneAPI Threading Building Blocks - a high level abstract threading library

Offline

#8 2025-09-23 16:28:46

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,303

Re: DaVinci Resolve Runtime Crashes

That matches the wiki article.
The problem appears to be that DR gpudetect util somehow tries to use the libOpenCL.so that comes with intel oneapi.

Try temporarily renaming opt/intel/oneapi/compiler/2025.0/lib/libOpenCL.so to something else.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#9 2025-09-24 00:58:47

ThePoultryman
Member
Registered: 2025-09-20
Posts: 7

Re: DaVinci Resolve Runtime Crashes

I don't have "libOpenCL.so" in "/opt/intel/oneapi/compiler/2025.0/lib/" or anywhere in "/opt/intel/oneapi". There were some other shared libraries that had opencl in their name ("/opt/intel/oneapi/compiler/2025.0/lib/libomptarget.rtl.opencl.so", "/opt/intel/oneapi/compiler/2025.0/lib/libur_adapter_opencl.so", etc.), and i did try renaming them all, but still, the crash persisted.

Intrestingly, pkgfile said the following:

$ pkgfile /opt/intel/oneapi/compiler/2025.0/lib/libOpenCL.so
extra/intel-oneapi-basekit
extra/intel-oneapi-compiler-shared-runtime

However, after reinstalling intel-oneapi-compiler-shared-runtime (which is what i have installed), the file still does not appear.

Offline

#10 2025-09-24 10:28:24

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,303

Re: DaVinci Resolve Runtime Crashes

It looks like you have intel-oneapi-compiler-shared-runtime-libs which doesn't include that file .

There are 5 packages in official repos that provide libOpenCL.so .
Please run

$ sudo pacman -Fy
$ pacman -F libOpenCL.so

and post the output of the 2nd command.
(the first is to ensure the file database pasman uses is uptodate)

Last edited by Lone_Wolf (2025-09-24 10:29:59)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#11 2025-09-24 19:36:47

ThePoultryman
Member
Registered: 2025-09-20
Posts: 7

Re: DaVinci Resolve Runtime Crashes

Output of pacman -F libOpenCL.so:

extra/cuda 13.0.1-1
    opt/cuda/targets/x86_64-linux/lib/libOpenCL.so
extra/intel-oneapi-basekit 2025.0.1.46-1
    opt/intel/oneapi/2025.0/lib/libOpenCL.so
    opt/intel/oneapi/compiler/2025.0/lib/libOpenCL.so
extra/intel-oneapi-compiler-shared-runtime 2025.0.4-2
    opt/intel/oneapi/compiler/2025.0/lib/libOpenCL.so
extra/ocl-icd 2.3.3-1 [installed]
    usr/lib/libOpenCL.so
multilib/lib32-ocl-icd 2.3.3-1
    usr/lib32/libOpenCL.so

Offline

#12 2025-09-25 08:19:11

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,303

Re: DaVinci Resolve Runtime Crashes

So no other OpenCL libs known to pacman.

Are you using stuff (like steam and lutris) from multilib ?
If so, install lib32-ocl-icd and test if DR behaviour changes.

Let's see if there are OpenCL libs that are not managed by pacman :

Post the output of

$ find /opt /usr ~/ "libOpenCL.so*"

(you may get a few permission errors)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#13 2025-09-25 16:19:34

ThePoultryman
Member
Registered: 2025-09-20
Posts: 7

Re: DaVinci Resolve Runtime Crashes

find ended with:

find: 'libOpenCL.so*': No such file or directory

(Here's the full find output, if it is needed: https://0x0.st/Km6l.txt)

For thoroughness, I also ran:

sudo updatedb
locate "libOpenCL.so"

and got:

/btrfs/SteamLibrary/steamapps/common/SteamLinuxRuntime_soldier/var/tmp-NU8R02/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libOpenCL.so.1
/home/coal/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper/var/tmp-45ITD3/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libOpenCL.so.1
/home/coal/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier/var/tmp-O3H1C3/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libOpenCL.so.1
/home/coal/.local/share/Steam/steamrt64/steam-runtime-steamrt/var/tmp-1K8HD3/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libOpenCL.so.1
/home/coal/.local/share/umu/steamrt3/var/tmp-YBLPD3/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libOpenCL.so.1
/usr/lib/libOpenCL.so
/usr/lib/libOpenCL.so.1
/usr/lib/libOpenCL.so.1.0.0
/usr/share/man/man7/libOpenCL.so.7.gz

Edit: I also tested with lib32-ocl-icd and the crash persisted.

Last edited by ThePoultryman (2025-09-26 05:35:51)

Offline

Board footer

Powered by FluxBB