DaVinci Resolve on Debian Linux (and makeresolvedeb)

I wonder if there is something happening due to the updated kernel or something.

Are there any messages in the system log?

Try running "sudo dmesg -w" in a terminal, connect the panel and watch for messages/errors/clues.

In dmesg, there are these messages:

When unplugging the panel:
[ 1026.437098] usb 3-2.2.1.4.4: USB disconnect, device number 17

When plugging the panel in:
[ 1066.058781] usb 3-2.2.1.4.4: new full-speed USB device number 18 using xhci_hcd
[ 1066.169714] usb 3-2.2.1.4.4: New USB device found, idVendor=1edb, idProduct=da0f, bcdDevice= 1.00
[ 1066.169734] usb 3-2.2.1.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1066.169736] usb 3-2.2.1.4.4: Product: DaVinci Resolve Micro Color Panel
[ 1066.169738] usb 3-2.2.1.4.4: Manufacturer: Blackmagic Design
[ 1066.169739] usb 3-2.2.1.4.4: SerialNumber: 5215907D6ACB4FED983765DA5870DBD2
[ 1066.179269] hid-generic 0003:1EDB:DA0F.000A: hiddev2,hidraw8: USB HID v1.10 Device [Blackmagic Design DaVinci Resolve Micro Color Panel] on usb-0000:00:14.0-2.2.1.4.4/input2



In syslog, I see:

When unplugging the panel:
2025-04-28T16:02:19.167137+01:00 Clevo-Temp kernel: usb 3-2.2.1.4.4: USB disconnect, device number 18


When plugging the panel in:
2025-04-28T16:02:53.925028+01:00 Clevo-Temp kernel: usb 3-2.2.1.4.4: new full-speed USB device number 19 using xhci_hcd
2025-04-28T16:02:54.034990+01:00 Clevo-Temp kernel: usb 3-2.2.1.4.4: New USB device found, idVendor=1edb, idProduct=da0f, bcdDevice= 1.00
2025-04-28T16:02:54.035005+01:00 Clevo-Temp kernel: usb 3-2.2.1.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2025-04-28T16:02:54.035014+01:00 Clevo-Temp kernel: usb 3-2.2.1.4.4: Product: DaVinci Resolve Micro Color Panel
2025-04-28T16:02:54.035015+01:00 Clevo-Temp kernel: usb 3-2.2.1.4.4: Manufacturer: Blackmagic Design
2025-04-28T16:02:54.035019+01:00 Clevo-Temp kernel: usb 3-2.2.1.4.4: SerialNumber: 5215907D6ACB4FED983765DA5870DBD2
2025-04-28T16:02:54.043968+01:00 Clevo-Temp kernel: hid-generic 0003:1EDB:DA0F.000B: hiddev2,hidraw9: USB HID v1.10 Device [Blackmagic Design DaVinci Resolve Micro Color Panel] on usb-0000:00:14.0-2.2.1.4.4/input2
2025-04-28T16:02:29.186260+01:00 Clevo-Temp gnome-shell[3806]: meta_window_stick: assertion '!window->override_redirect' failed
2025-04-28T16:02:54.047041+01:00 Clevo-Temp mtp-probe: checking bus 3, device 19: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2.2/3-2.2.1/3-2.2.1.4/3-2.2.1.4.4"
2025-04-28T16:02:54.047159+01:00 Clevo-Temp mtp-probe: bus: 3, device: 19 was not an MTP device
2025-04-28T16:02:54.060034+01:00 Clevo-Temp mtp-probe: checking bus 3, device 19: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2.2/3-2.2.1/3-2.2.1.4/3-2.2.1.4.4"
2025-04-28T16:02:54.060125+01:00 Clevo-Temp mtp-probe: bus: 3, device: 19 was not an MTP device

Have found I can cause resolve to crash in the test system by changing the grading panel from none to micro color panel and vice versa in settings.

It was working ok in before the package updates, but have only just tried it afterwards.

Will have a look at the logs later, and see if there's anything interesting.

This is crash_archive.txt after the crash when selecting the micro color panel in settings:


#TIME Tue Apr 29 20:05:34 2025 - Uptime 00:00:21 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve v19.1.4.0011 (Linux/Clang x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID be7a4cb2-27a9-4ac0-9889-f9250e5b955c
#BMD_GIT_COMMIT 755196be3de2c6b815963568c83e02811d250cbb
#BMD_UTIL_VERSION 19.1.4.0011
#OS Linux

/opt/resolve/bin/resolve() [0x4edb1a9]
/opt/resolve/bin/resolve() [0x4eda580]
/lib/x86_64-linux-gnu/libc.so.6(+0x45250) [0x7b0bed245250]
/lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x11c) [0x7b0bed2a3f1c]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x1e) [0x7b0bed24519e]
/lib/x86_64-linux-gnu/libc.so.6(abort+0xdf) [0x7b0bed228902]
/lib/x86_64-linux-gnu/libudev.so.1(+0x914a) [0x7b0c1908114a]
/lib/x86_64-linux-gnu/libudev.so.1(+0x17fab) [0x7b0c1908ffab]
/lib/x86_64-linux-gnu/libudev.so.1(+0x2ad7b) [0x7b0c190a2d7b]
/lib/x86_64-linux-gnu/libudev.so.1(udev_monitor_unref+0x39) [0x7b0c19086bd9]
/opt/resolve/bin/../libs/libDaVinciPanels.so(_ZN15HIDLinuxManager4StopEv+0x6d) [0x7b0bf7cb3cdd]
/opt/resolve/bin/../libs/libDaVinciPanels.so(_ZN15HIDLinuxManagerD1Ev+0x17) [0x7b0bf7cb4527]
/opt/resolve/bin/../libs/libDaVinciPanels.so(_ZN15HIDLinuxManagerD0Ev+0x9) [0x7b0bf7cb4569]
/opt/resolve/bin/../libs/libDaVinciPanels.so(_ZN10HIDManager20UnregisterDispatcherERKNS_3KeyEP13HIDDispatcher+0x9e) [0x7b0bf7cb25fe]
/opt/resolve/bin/../libs/libDaVinciPanels.so(_ZN18BMDLightDispatcherD1Ev+0x13c) [0x7b0bf7cbc91c]
/opt/resolve/bin/../libs/libDaVinciPanels.so(_ZN18BMDLightDispatcherD0Ev+0x9) [0x7b0bf7cbca69]
/opt/resolve/bin/../libs/libDaVinciPanels.so(_ZN15PanelControllerD1Ev+0x37) [0x7b0bf7c2bd07]
/opt/resolve/bin/../libs/libDaVinciPanels.so(_Z22BMD_DVP_RunPanelDaemoniPPc+0x18f) [0x7b0bf7d93b9f]
/opt/resolve/bin/resolve() [0x73b2983]
/opt/resolve/bin/resolve() [0x2b41648]
/lib/x86_64-linux-gnu/libc.so.6(+0xa1e2e) [0x7b0bed2a1e2e]
/lib/x86_64-linux-gnu/libc.so.6(+0x133a4c) [0x7b0bed333a4c]
Signal Number = 6

Greetings!

I've recently switched from Windows to Linux Mint 22.1 on my main system (older, Windows 11 not supported). I am running DVR Studio 19.1.4 b11 that I installed via makeresolvedeb.

The issue I am having is that there is no audio on any of the file formats I've tested. When going into the "Video and Audio I/O" options the only Audio I/O engine available is "System Audio." I'm seeing no signal on the mixer either. Audio works fine in any other application.

System Report info:

Audio:
Device-1: Intel 9 Series Family HD Audio vendor: ASUSTeK 9 driver: snd_hda_intel v: kernel
bus-ID: 00:1b.0 chip-ID: 8086:8ca0 class-ID: 0403
Device-2: NVIDIA GA104 High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
pcie: speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:228b class-ID: 0403
Device-3: Corsair VOID PRO Surround USB Adapter driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 3-11:3 chip-ID: 1b1c:0a1e class-ID: 0300
serial: <filter>
API: ALSA v: k6.8.0-59-generic status: kernel-api
Server-1: PipeWire v: 1.0.5 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin

Any suggestions? I'm very new to Linux, not scared of the terminal but don't have any of the command line stuff memorized.

[Dwaine Maggart]

Just to note: AAC audio is not supported by Resolve on Linux. Is it possible the files you tested were using AAC audio?

I've spent literal days trying to get DaVinci to launch on Linux Mint, and I finally figured it out!

First of all, something in the launch sequence prevents DaVinci from accessing user folders. The only way I was able to run DaVinci as a normal user was by using this script:

Code: Select all

#!/bin/bash
export HOME=/tmp/resolve-temp
mkdir -p "$HOME"
exec /opt/resolve/bin/resolve


The issue with this approach is that this folder gets wiped during reboot, meaning that it won't save any settings and act as a brand-new installation after every restart.

Unfortunately, this is the only solution that allowed me to run DaVinci as a normal user.

On the other hand, although this isn't recommended, running it as sudo solves almost every problem. DaVinci launches, it stores settings between sessions.

However - at least in my case - running it as root, completely breaks the audio out. It's not a codec issue, as a known working file doesn't even show up in the volume meter.

Fortunately, this is also solvable. All it takes, is to launch DaVinci with this command:

Code: Select all

sudo PULSE_SERVER=unix:/run/user/$USER_ID/pulse/native /opt/resolve/bin/resolve


And just like that, it will both save the config files, and allow the sound to work (without any delay, and without cutting off sound in other apps).

Now, running DaVinci as sudo is less than ideal, but so far, that's the only solution that worked for me.

What is the output when starting DR in the terminal without sudo?

go to the folder where DR is installed:

Code: Select all

cd /opt/resolve/bin/

and start resolve

Code: Select all

./resolve

I get this as an output

Code: Select all

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
PnlMsgActionStringAdapter Already in Table: Code= 615e, Mode=  0, Level=  0, CmdKey= -1, Option= 0
18.6.6.0007 Linux/Clang x86_64
Main thread starts: 40810180
Segmentation fault (core dumped)


Hello Blackmagic Debian Team and Community,

I am facing a critical issue after upgrading from DaVinci Resolve 19 to 20, running on Debian 12 (Bookworm) on X11. After the upgrade, whenever I press a modifier key such as Ctrl, Alt or Shift inside the Fusion tab, the application crashes and closes immediately without any error message.

I have run several tests and captured logs showing recurring warnings such as:

UI.ActionManager | WARN | The action [editCut] is not a valid global action
UI.ActionManager | WARN | The action [editBackspace] is not a valid global action
UI.ActionManager | WARN | The owner of the action [FusionWidget] is not active when updating the shortcut [editCopy] due to [No focused widget defined yet]
Fusion | WARN | Ignoring Fusion's crash notification during a Fusion API call

System environment:

OS: Debian 12 (X11 session confirmed via $XDG_SESSION_TYPE)

DaVinci Resolve version: 20 (latest)

NVIDIA drivers: Proprietary (570.153.02 Cuda 12.8)

Input devices: USB keyboard (SINO WEALTH USB Composite Device)

DaVinci launch via terminal: /opt/resolve/bin/resolve

Logs consistently report failures to register basic editing actions and Fusion API warnings. Crashes only occur within the Fusion tab.

Has anyone else experienced this issue with version 20?

Thanks in advance for any help or guidance.

Best regards,
Alexandre Soares

Yes, I have this same issue

Bertold

Installed Davinci Resolve Studio again today on Linux Mint 22 ( with makresolvedeb).
Which worked before on a non homefolder encrypted LM22.

After a reinstall, now encypted homefolder I've run into issues.
So maybe that Davinci Resolve Studio runs into these issues (not starting, only as root) because the home folder is encrypted?

Anyway, I got it running as root but the audio does not work at all, even with the suggested line posted by someone earlier. The files I use are working with audio outside of Resolve.

Running ./resolve give the already known error;

Code: Select all

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.0.0.0049 Linux/Clang x86_64
Main thread starts: F9931000
Segmentation fault (core dumped)


I hope this helps in finding the fault and hopefully fix this in the future, I expect more people hopping over to linux.
So back to Windows for now it seems although that is far from ideal.