Can´t use Davinci Resolve Studio | Crash to Desktop

SFoX · January 31, 2026, 3:05am

My system:
OS: EndeavourOS
Graphics card: AMD Radeon 6700 XT
RAM: 24GB DDR4
Processor: AMD Ryzen 5 3600
Kernel: 6.18.7-zen1-1-zen
Desktop: KDE Plasma 6.5.5

Hi everyone,

Yesterday I treated myself to a DaVinci Resolve Studio license and wanted to start using it. Unfortunately, I’m having serious problems. The installation always runs smoothly, whether I unzip the .ZIP and double-click the .run file, copy the .zip to /home/sfox/.cache/yay/davinci-resolve-studio/ and install via yay -S davinci-resolve-studio, or follow these methods: (https://forum.endeavouros.com/t/how-to-install-davinci-resolve-studio-20-3-1-on-arch-linux-new-method-also-free-version-info/77098)

However, when starting the software, there were always some issues. I managed to fix those with lots of googling and reading, but it didn’t help much. Now the following happens:

DaVinci starts (since I entered the license key, it goes straight to the project selection)
I create a new project
The main program loads
I click on CUT or EDIT or try to import a video
Crash

In the console, I get:

[sfox~]$ /opt/resolve/bin/resolve  
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  
20.3.1.0006 Linux/Clang x86_64  
Main thread starts: D71D0000  
0x7fd5d71d0000 | Undefined            | INFO  | 2026-01-30 16:11:01,630 | --------------------------------------------------------------------------------  
0x7fd5d71d0000 | Undefined            | INFO  | 2026-01-30 16:11:01,630 | Loaded log config from /home/sfox/.local/share/DaVinciResolve/configs/log-conf.xml  
0x7fd5d71d0000 | Undefined            | INFO  | 2026-01-30 16:11:01,630 | --------------------------------------------------------------------------------  
FusionScript Server [36924] Started  
Host 'Resolve' [36476] Added  
Host 'Resolve' Killed  
FusionScript Server [36924] Terminated  
[sfox~]$

And the log file ends with:

==========[CRASH DUMP]==========  
#TIME Fri Jan 30 16:00:08 2026 - Uptime 00:00:15 (hh:mm:ss)  
#PROGRAM_NAME DaVinci Resolve Studio v20.3.1.0006 (Linux/Clang x86_64)  
#BMD_ARCHITECTURE x86_64  
#BMD_BUILD_UUID 5f90fb54-d661-4f14-9db1-3148eb6eb0f  
#BMD_GIT_COMMIT d031039b09e055f0d8d437a51ff3d87f364f4765  
#BMD_UTIL_VERSION 20.3.1.0006  
#OS Linux  
  
/opt/resolve/bin/resolve() [0x6087e49]  
/opt/resolve/bin/resolve() [0x6087012]  
/usr/lib/libc.so.6(+0x3e4d0) [0x7f4543c4d4d0]  
/opt/resolve/bin/../libs/libProResRAW.so(_ZNSt10filesystem7__cxx114path14_M_split_cmptsEv+0x38) [0x7f45358da708]  
/usr/lib/libRusticlOpenCL.so.1(+0xb17c39) [0x7f44e9517c39]  
/usr/lib/libRusticlOpenCL.so.1(+0xb1fcea) [0x7f44e951fcea]  
/usr/lib/libRusticlOpenCL.so.1(+0xb109b6) [0x7f44e95109b6]  
/usr/lib/libRusticlOpenCL.so.1(+0x25a902) [0x7f44e8c5a902]  
/usr/lib/libRusticlOpenCL.so.1(+0x235bf7) [0x7f44e8c35bf7]  
/usr/lib/libRusticlOpenCL.so.1(+0x2350a4) [0x7f44e8c350a4]  
/usr/lib/libRusticlOpenCL.so.1(+0x170400) [0x7f44e8b70400]  
/usr/lib/libRusticlOpenCL.so.1(+0x4039e5) [0x7f44e8e039e5]  
/usr/lib/libRusticlOpenCL.so.1(+0x44c2dd) [0x7f44e8e4c2dd]  
/usr/lib/libc.so.6(+0x9698b) [0x7f4543ca598b]  
/usr/lib/libc.so.6(+0x11aa0c) [0x7f4543d29a0c]  
Signal Number = 11  
  
================================

I’m really out of ideas now. I’ve tried every tip on the internet, even reinstalled the old X11 and installed it that way. I’ve tested RocM-OpenCL, opencl-amd, and opencl-mesa…
With RocM-OpenCL nothing changes, with opencl-amd the program just won’t start at all, and opencl-mesa is my standard driver which I also use for gaming and so on. That one always works fine and clinfo doesn’t complain either.
Only with DaVinci Resolve there seem to be issues.

So if anyone knows what to do, that would be my lifesaver.

Bink · January 31, 2026, 8:31am

Perhaps have a look here @SFoX :

This is how I got it working with my AMD GPU.

In a nutshell, try running this command to launch Resolve:

ROC_ENABLE_PRE_VEGA=1 RUSTICL_ENABLE=amdgpu,amdgpu-pro,radv,radeon,radeonsi DRI_PRIME=1 QT_QPA_PLATFORM=xcb /opt/resolve/bin/resolve

xircon · January 31, 2026, 9:41am

What @Bink said, but also install from aur it ensures you have everything needed.

2 aur/davinci-resolve 20.3.1-2 (+175 4.88) (Installed)
    Professional A/V post-production software suite from Blackmagic Design
1 cachyos/davinci-resolve 20.3.1-2 (2.9 GiB 6.7 GiB) (Installed)
    Professional A/V post-production software suite from Blackmagic Design

SFoX · February 1, 2026, 5:09pm

Hey, thank you guys for the response. Unfortunately, the problem persists. The program fires up (when I use the mentioned command:
”ROC_ENABLE_PRE_VEGA=1 RUSTICL_ENABLE=amdgpu,amdgpu-pro,radv,radeon,radeonsi DRI_PRIME=1 QT_QPA_PLATFORM=xcb /opt/resolve/bin/resolve” )
it has a different boot sequence:

[sfox~]$ ROC_ENABLE_PRE_VEGA=1 RUSTICL_ENABLE=amdgpu,amdgpu-pro,radv,radeon,radeonsi DRI_PRIME=1 QT_QPA_PLATFORM=xcb /opt/resolve/bin/resolve
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
20.3.1.0006 Linux/Clang x86_64
Main thread starts: DB8E8000
0x7f57db8e8000 | Undefined | INFO | 2026-02-01 12:54:39,644 | --------------------------------------------------------------------------------
0x7f57db8e8000 | Undefined | INFO | 2026-02-01 12:54:39,645 | Loaded log config from /home/sfox/.local/share/DaVinciResolve/configs/log-conf.xml
0x7f57db8e8000 | Undefined | INFO | 2026-02-01 12:54:39,645 | --------------------------------------------------------------------------------
Inconsistent value (1) for DRI_PRIME. Should be < 1 (GPU devices count). Using: 0
Inconsistent value (1) for DRI_PRIME. Should be < 1 (GPU devices count). Using: 0
Inconsistent value (1) for DRI_PRIME. Should be < 1 (GPU devices count). Using: 0
FusionScript Server [19781] Started
Host 'Resolve' [19335] Added)

Then I can choose a project or start a new one. After that, the main program launches. At this point I can:
→ click on Fusion, Color, Fairlight, or Export
→ but the program immediately crashes if I import a media file or click on “Media”, “Cut”, or the “Edit” tab.

The ResolveDebug.txt ends with “Signal Number = 11” again, so nothing really changed.

Regarding the libraries and drivers, I have installed:
extra/glu 9.0.3-2
extra/mesa 1:25.3.4-1
extra/mesa-utils 9.0.0-7
extra/opencl-mesa 1:25.3.4-1
extra/vulkan-mesa-implicit-layers 1:25.3.4-1
multilib/lib32-mesa 1:25.3.4-1
multilib/lib32-vulkan-mesa-implicit-layers 1:25.3.4-1
extra/hsa-rocr 7.1.1-2
extra/rocm-core 7.1.1-1
extra/rocm-device-libs 2:7.1.1-2
extra/rocm-llvm 2:7.1.1-2
extra/rocm-opencl-runtime 7.1.1-1

These are different versions than the ones you mentioned. But is it a smart idea to downgrade? Would that really help? And how could I prevent these packages from being updated again the next time I run -Syu?

Thanks in advance.

xayber · February 2, 2026, 3:31pm

Hi! I’m an Arch user with a Radeon RX 7600 and Davinci Resolve.

Last week opencl-amd updated from 7.1.1 to 7.2.0 and break DaVinci Resolve.

Downgrading and pin it to 7.1.1 fixed the issue.

You could check the opencl-amd version in your system.

Also you could try the distrobox of davinci:

Hope this help you.

Bink · February 2, 2026, 8:53pm

I’d noted a “fix” shared in the AUR comments, but it was to essentially install/downgrade to the version of rocm-opencl-runtime @SFoX is already running

Welcome to the community @xayber

SFoX · February 3, 2026, 7:50pm

Hey folks, many thanks for the help here.

Unfortunately, I wasn’t able to find and install a 7.1.1 version of opencl-amd.
So no luck either via yay -S downgrade opencl-amd or by searching the internet.
I did manage to find some of the libraries, but not opencl-amd itself in particular.

I have no idea how I’m supposed to approach this.

Bink · February 3, 2026, 11:28pm

The advice in the AUR comments section was to uninstall opencl-amd, and install rocm-opencl-runtime instead.

sudomateo commented on 2026-01-31 21:17 (UTC)

Update: Turns out that this is happening because the update of opencl-amd package, the newest ROCm 7.2 drivers appear to not be compatible with DaVinci, I installed rocm-opencl-runtime from the extra repo since it still on 7.1.1 and now its working again.. It also doesn’t work with opencl-mesa, it crashes launching a project

This advice worked for me on the Framework Desktop. I uninstalled opencl-amd using sudo pacman -Rdd opencl-amd, installed rocm-opencl-runtime using sudo pacman -Sy rocm-opencl-runtime, and was able to successfully launch DaVinci Resolve and render a video using H.264 via VAAPI.

I haven’t had a chance to run tests on my AMD laptop again. My main workstation where I use DaVinci Resolve Studio is Nvidia based and doesn’t have these issues.

SFoX · February 4, 2026, 8:09pm

Hey, yeah, I know. But unfortunately this solution doesn’t work, because, as you already noticed, I’ve already installed that driver. That’s why I tried using the previous suggested solutions. But for that I’d have to downgrade .. and unfortunately that failed.

jake99 · February 4, 2026, 10:57pm

As described in this comment on the AUR page, as long as the packages for the older version are on the AMD’s site, you can always build opencl-amd manually.

For the version 7.1.1 of opencl-amd you will need this commit https://aur.archlinux.org/cgit/aur.git/commit/?h=opencl-amd&id=42c9eb7048bfa03b600cedc61f95b922c80dffa0

Check out this comment for detailed step by step instructions how to do it if you are more comfortable with git.

Bink · February 5, 2026, 10:33pm

I can’t vouch for the solution, but here’s the latest fix offered in the AUR comments:

rev.cressy commented on 2026-02-05 14:20 (UTC)

Thanks Aaron for the excellent post which made resolve work great.

aaron-rust commented on 2026-02-04 22:22 (UTC)

As freqmod mentioned already, davinci-resolve-studio does not start anymore with an AMD GPU after the latest upgrade containing AMD specific packages with version number 7.2.0. Packages with version numbers of 7.1.1 still work. Here is the complete downgrade command for ease of use:
sudo pacman -U https://archive.archlinux.org/packages/h/hsa-rocr/hsa-rocr-7.1.1-2-x86_64.pkg.tar.zst https://archive.archlinux.org/packages/s/spirv-llvm-translator/spirv-llvm-translator-21.1.3-1-x86_64.pkg.tar.zst https://archive.archlinux.org/packages/r/rocminfo/rocminfo-7.1.1-1-x86_64.pkg.tar.zst https://archive.archlinux.org/packages/r/rocm-core/rocm-core-7.1.1-1-x86_64.pkg.tar.zst https://archive.archlinux.org/packages/r/rocm-device-libs/rocm-device-libs-2%3A7.1.1-2-x86_64.pkg.tar.zst https://archive.archlinux.org/packages/r/rocm-opencl-runtime/rocm-opencl-runtime-7.1.1-1-x86_64.pkg.tar.zst https://archive.archlinux.org/packages/r/rocm-llvm/rocm-llvm-2%3A7.1.1-2-x86_64.pkg.tar.zst

SFoX · February 6, 2026, 1:57am

Thank you guys so, so much for your help! After completely downgrading to 7.1.1 and removing opencl-mesa, I’ve finally managed to use DaVinci properly again.
For now, I’ve added the packages to the IgnorePkg list so they survive the next system update.

At last, this chapter is closed. Thank you very much!

system · February 8, 2026, 1:58am

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.