Register for a free account now!
This is the place to discus everything about the free video editing software DaVinci Resolve. Members help other members. Reserve your preferred username before someone else takes it.
A quick check on Gemini says it's a fault when the program tries to access a memory location that it's not allowed to touch. Gemini and probably other AI Chatbots will give you a detailed explanation and clues on how to fix it.
…then the issue is almost certainly caused by Resolve not being able to write to its own log directory. This usually happens if Resolve was ever run with sudo, which causes the config/log folders to become owned by root.
The “ActCCMessage Already in Table” lines are harmless and not related to the crash.
Sadly I've gotten the same thing.Even after renaming the folder.
Is there a guide for Debian 13 as this setup is absolutely torturous.
Was planning to buy the paid version but not if I can't even get the free one up and running.
I include the driver version of Nvidia I'm on
If I then click update configuration I cannot see my GPU in GPU configuration. Is there something I need to do to get Davinci Resolve to recognise my GPU card?
I am not running Debian 13, so it's difficult for me to answer precisely what the issue is. I found an article that was updated Jan 17, 2026 that might answer some questions for you a little better.
Edit: A little more research showed me that Debian 13.4 (trixie) has the latest security updates.
1. DaVinci Resolve on Linux requires CUDA to utilize NVIDIA GPUs
2. Common issues on Debian is that Resolve looks for libraries in paths used by CentOS and Rocky Linux distros. You can often force Resolve to see the driver by preloading the library.
Try launching Resolve from the terminal with this command: