@nixit What GPU do you have? On my system, resolve hangs on startup before displaying any GUI. In the log file (rollinglog.txt), it stops at "Starting GPUDetect 1.2_3-a1". Attaching with GDB and doing a backtrace shows that it's stuck on some oneapi/tbb related stuff. I'm using an RTX 3070 GPU - maybe it doesn't get stuck there with other GPUs?
Backtrace:
#0 0x00007f1f180a3ab1 in ?? () from /usr/lib/libc.so.6
#1 0x00007f1f166c64a3 in clGetExtensionFunctionAddress () from /opt/intel/oneapi/compiler/2023.0.0/linux/lib/libOpenCL.so
#2 0x00007f1f166c56e7 in ?? () from /opt/intel/oneapi/compiler/2023.0.0/linux/lib/libOpenCL.so
#3 0x00007f1f166c9bd9 in ?? () from /opt/intel/oneapi/compiler/2023.0.0/linux/lib/libOpenCL.so
#4 0x00007f1f180a3b17 in ?? () from /usr/lib/libc.so.6
#5 0x00007f1f166c64a3 in clGetExtensionFunctionAddress () from /opt/intel/oneapi/compiler/2023.0.0/linux/lib/libOpenCL.so
#6 0x00007f1f16002fc4 in ?? () from /opt/cuda/lib64/libOpenCL.so.1
#7 0x00007f1f180a3b17 in ?? () from /usr/lib/libc.so.6
#8 0x00007f1f160048df in clGetPlatformIDs () from /opt/cuda/lib64/libOpenCL.so.1
#9 0x00007f1f24219627 in ?? () from /opt/resolve/bin/../libs/libgpudetect.so
#10 0x00007f1f2420e61f in ?? () from /opt/resolve/bin/../libs/libgpudetect.so
#11 0x00007f1f24222094 in ?? () from /opt/resolve/bin/../libs/libgpudetect.so
#12 0x00007f1f241c0afd in ?? () from /opt/resolve/bin/../libs/libgpudetect.so
#13 0x00007f1f241c05c4 in ?? () from /opt/resolve/bin/../libs/libgpudetect.so
#14 0x00000000023970a8 in ?? ()
#15 0x0000000002391e7d in ?? ()
#16 0x00007f1f1803c790 in ?? () from /usr/lib/libc.so.6
#17 0x00007f1f1803c84a in __libc_start_main () from /usr/lib/libc.so.6
#18 0x0000000002390c0b in ?? ()
Pinned Comments
Muflone commented on 2025-01-26 02:15 (UTC)
IMPORTANT!
Since version 19.1.3-2 this package will not download automatically the source file from the upstream site.
To build this package you will need to manually download the file from https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion and place it in the same directory with the PKGBUILD.
This would reduce the mess in this package, making it more readable and clear. Also bypassing the required information from the upstream URL is not allowed in an automated way.