DaVinci Resolve on Linux - Install issues

black magic really needs to make this a flatpack, and fix some of the weird file locations, and gpu stuff.

yes -- fixing the obvious flaws of the actual installer, would be really an important improvement, but the other claim -- i.e. flatpack deliveries -- is IMHO nearly impossible to realize right now.

unfortunately there is no working solution available, to realize CUDA acceleration from within flatpack sandboxes (something similar to nvidia-docker). in case of appimage, which is much simpler and less isolated from the surrounding environment, this hindrance is easier to overcome, but on the other hand it doesn't solve all the incompatibilities and dependencies related to the actual system resp. runtime environment...

I am trying to run on gentoo. any clues.

ldd output
linux-vdso.so.1 (0x00007ffeadb80000)
libc++.so.1 => /opt/resolve/bin/./../libs/libc++.so.1 (0x00007fb421069000)
libc++abi.so.1 => /opt/resolve/bin/./../libs/libc++abi.so.1 (0x00007fb420e3a000)
libcudart.so.9.1 => /opt/resolve/bin/./../libs/libcudart.so.9.1 (0x00007fb420bcc000)
libnvrtc.so.9.1 => /opt/resolve/bin/./../libs/libnvrtc.so.9.1 (0x00007fb41f4a0000)
libQt5Concurrent.so.5 => /opt/resolve/bin/./../libs/libQt5Concurrent.so.5 (0x00007fb421567000)
libQt5Core.so.5 => /opt/resolve/bin/./../libs/libQt5Core.so.5 (0x00007fb41eec0000)
libQt5Gui.so.5 => /opt/resolve/bin/./../libs/libQt5Gui.so.5 (0x00007fb41e956000)
libQt5Multimedia.so.5 => /opt/resolve/bin/./../libs/libQt5Multimedia.so.5 (0x00007fb421481000)
libQt5Network.so.5 => /opt/resolve/bin/./../libs/libQt5Network.so.5 (0x00007fb42137c000)
libQt5OpenGL.so.5 => /opt/resolve/bin/./../libs/libQt5OpenGL.so.5 (0x00007fb41e8f3000)
libQt5Sql.so.5 => /opt/resolve/bin/./../libs/libQt5Sql.so.5 (0x00007fb41e7ac000)
libQt5Svg.so.5 => /opt/resolve/bin/./../libs/libQt5Svg.so.5 (0x00007fb41e753000)
libQt5Widgets.so.5 => /opt/resolve/bin/./../libs/libQt5Widgets.so.5 (0x00007fb41e0da000)
libQt5Xml.so.5 => /opt/resolve/bin/./../libs/libQt5Xml.so.5 (0x00007fb41e091000)
libQt5XmlPatterns.so.5 => /opt/resolve/bin/./../libs/libQt5XmlPatterns.so.5 (0x00007fb41dbff000)
libGLU.so.1 => /usr/lib64/libGLU.so.1 (0x00007fb41d94e000)
libGL.so.1 => /usr/lib64/opengl/nvidia/lib/libGL.so.1 (0x00007fb41d6aa000)
fusionscript.so => /opt/resolve/bin/./../libs/Fusion/fusionscript.so (0x00007fb41d088000)
libluajit-5.1.so.2 => /opt/resolve/bin/./../libs/libluajit-5.1.so.2 (0x00007fb41ce09000)
libtbbmalloc.so.2 => /opt/resolve/bin/./../libs/libtbbmalloc.so.2 (0x00007fb41cbca000)
libtbbmalloc_proxy.so.2 => /opt/resolve/bin/./../libs/libtbbmalloc_proxy.so.2 (0x00007fb41c9c5000)
libXxf86vm.so.1 => /usr/lib64/libXxf86vm.so.1 (0x00007fb41c7bf000)
libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007fb41c505000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007fb41c2f3000)
libSM.so.6 => /usr/lib64/libSM.so.6 (0x00007fb41c0eb000)
libICE.so.6 => /usr/lib64/libICE.so.6 (0x00007fb41bece000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007fb41bb91000)
libbz2.so.1 => /lib64/libbz2.so.1 (0x00007fb41b981000)
libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x00007fb41b61e000)
libm.so.6 => /lib64/libm.so.6 (0x00007fb41b2cd000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fb41b0c9000)
librt.so.1 => /lib64/librt.so.1 (0x00007fb41aec1000)
libavformat.so.57 => /opt/resolve/bin/./../libs/libavformat.so.57 (0x00007fb41aac7000)
libavcodec.so.57 => /opt/resolve/bin/./../libs/libavcodec.so.57 (0x00007fb41955f000)
libavutil.so.55 => /opt/resolve/bin/./../libs/libavutil.so.55 (0x00007fb4192ec000)
libMXF.so => /opt/resolve/bin/./../libs/libMXF.so (0x00007fb418fdc000)
libSMDK-Linux-x64.so.4.7 => /opt/resolve/bin/./../libs/libSMDK-Linux-x64.so.4.7 (0x00007fb418b32000)
libmp4decMT.so => /opt/resolve/bin/./../libs/libmp4decMT.so (0x00007fb418802000)
libmp4encMT.so => /opt/resolve/bin/./../libs/libmp4encMT.so (0x00007fb418296000)
libsonyxavcenc.so => /opt/resolve/bin/./../libs/libsonyxavcenc.so (0x00007fb418029000)
liblog4cxx.so.10 => /opt/resolve/bin/./../libs/liblog4cxx.so.10 (0x00007fb417b12000)
libapr-1.so.0 => /opt/resolve/bin/./../libs/libapr-1.so.0 (0x00007fb4178d6000)
libaprutil-1.so.0 => /opt/resolve/bin/./../libs/libaprutil-1.so.0 (0x00007fb4176a9000)
libopencv_calib3d.so.3.3 => /opt/resolve/bin/./../libs/libopencv_calib3d.so.3.3 (0x00007fb4172e9000)
libopencv_core.so.3.3 => /opt/resolve/bin/./../libs/libopencv_core.so.3.3 (0x00007fb416de5000)
libopencv_features2d.so.3.3 => /opt/resolve/bin/./../libs/libopencv_features2d.so.3.3 (0x00007fb416b36000)
libopencv_flann.so.3.3 => /opt/resolve/bin/./../libs/libopencv_flann.so.3.3 (0x00007fb4168ca000)
libopencv_highgui.so.3.3 => /opt/resolve/bin/./../libs/libopencv_highgui.so.3.3 (0x00007fb4166c1000)
libopencv_imgcodecs.so.3.3 => /opt/resolve/bin/./../libs/libopencv_imgcodecs.so.3.3 (0x00007fb416496000)
libopencv_imgproc.so.3.3 => /opt/resolve/bin/./../libs/libopencv_imgproc.so.3.3 (0x00007fb415d0d000)
libopencv_ml.so.3.3 => /opt/resolve/bin/./../libs/libopencv_ml.so.3.3 (0x00007fb415a59000)
libopencv_objdetect.so.3.3 => /opt/resolve/bin/./../libs/libopencv_objdetect.so.3.3 (0x00007fb41580c000)
libopencv_video.so.3.3 => /opt/resolve/bin/./../libs/libopencv_video.so.3.3 (0x00007fb4155c0000)
libopencv_videoio.so.3.3 => /opt/resolve/bin/./../libs/libopencv_videoio.so.3.3 (0x00007fb4153a9000)
libopencv_dnn.so.3.3 => /opt/resolve/bin/./../libs/libopencv_dnn.so.3.3 (0x00007fb414e9e000)
libcudnn.so.5 => /opt/resolve/bin/./../libs/libcudnn.so.5 (0x00007fb40fc2f000)
libSonyRawDev.so.3 => /opt/resolve/bin/./../libs/libSonyRawDev.so.3 (0x00007fb40f825000)
libOpenCL.so.1 => /usr/lib64/OpenCL/vendors/nvidia/libOpenCL.so.1 (0x00007fb40f61f000)
libgvc.so.6 => /opt/resolve/bin/./../libs/libgvc.so.6 (0x00007fb40f37e000)
libcgraph.so.6 => /opt/resolve/bin/./../libs/libcgraph.so.6 (0x00007fb40f168000)
libcdt.so.5 => /opt/resolve/bin/./../libs/libcdt.so.5 (0x00007fb40ef61000)
libxdot.so.4 => /opt/resolve/bin/./../libs/libxdot.so.4 (0x00007fb40ed5c000)
libpathplan.so.4 => /opt/resolve/bin/./../libs/libpathplan.so.4 (0x00007fb40eb54000)
libDNxHR.so => /opt/resolve/bin/./../libs/libDNxHR.so (0x00007fb40e3ba000)
libimf.so => /opt/resolve/bin/./../libs/libimf.so (0x00007fb40def7000)
libirc.so => /opt/resolve/bin/./../libs/libirc.so (0x00007fb40dc9f000)
libsvml.so => /opt/resolve/bin/./../libs/libsvml.so (0x00007fb40d0a2000)
libintlc.so.5 => /opt/resolve/bin/./../libs/libintlc.so.5 (0x00007fb40ce4c000)
libArriRawSDK.so.5 => /opt/resolve/bin/./../libs/libArriRawSDK.so.5 (0x00007fb40ae4f000)
libgvcodec.so => /opt/resolve/bin/./../libs/libgvcodec.so (0x00007fb40ac28000)
libCrmSdk.so.2.1 => /opt/resolve/bin/./../libs/libCrmSdk.so.2.1 (0x00007fb408968000)
libid3-3.8.so.3 => /opt/resolve/bin/./../libs/libid3-3.8.so.3 (0x00007fb40872b000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fb408509000)
libssl.so.1.0.0 => /opt/resolve/bin/./../libs/libssl.so.1.0.0 (0x00007fb408293000)
libcrypto.so.1.0.0 => /opt/resolve/bin/./../libs/libcrypto.so.1.0.0 (0x00007fb407e2a000)
librsvg-2.so.2 => /usr/lib64/librsvg-2.so.2 (0x00007fb407bf4000)
libCg.so => /opt/resolve/bin/./../libs/libCg.so (0x00007fb406c8c000)
libCgGL.so => /opt/resolve/bin/./../libs/libCgGL.so (0x00007fb406b0b000)
libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/libgcc_s.so.1 (0x00007fb4068f2000)
libc.so.6 => /lib64/libc.so.6 (0x00007fb406530000)
/lib64/ld-linux-x86-64.so.2 (0x00007fb42134b000)
libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/libstdc++.so.6 (0x00007fb40612d000)
libGLX.so.0 => /usr/lib64/opengl/nvidia/lib/libGLX.so.0 (0x00007fb405efd000)
libGLdispatch.so.0 => /usr/lib64/opengl/nvidia/lib/libGLdispatch.so.0 (0x00007fb405c2d000)
libpng16.so.16 => /usr/lib64/libpng16.so.16 (0x00007fb4059f7000)
libz.so.1 => /lib64/libz.so.1 (0x00007fb4057e0000)
libuuid.so.1 => /lib64/libuuid.so.1 (0x00007fb4055d9000)
libbsd.so.0 => /usr/lib64/libbsd.so.0 (0x00007fb4053c3000)
libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007fb405198000)
libicuuc.so.60 => /usr/lib64/libicuuc.so.60 (0x00007fb404de3000)
libexpat.so.1 => /usr/lib64/libexpat.so.1 (0x00007fb404bb9000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007fb404981000)
libcudart.so.7.5 => /opt/resolve/bin/./../libs/libcudart.so.7.5 (0x00007fb404721000)
libgdk_pixbuf-2.0.so.0 => /usr/lib64/libgdk_pixbuf-2.0.so.0 (0x00007fb4044fd000)
libgio-2.0.so.0 => /usr/lib64/libgio-2.0.so.0 (0x00007fb404164000)
libpangocairo-1.0.so.0 => /usr/lib64/libpangocairo-1.0.so.0 (0x00007fb403f55000)
libpango-1.0.so.0 => /usr/lib64/libpango-1.0.so.0 (0x00007fb403d0f000)
libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007fb403abc000)
libcairo.so.2 => /usr/lib64/libcairo.so.2 (0x00007fb403793000)
libcroco-0.6.so.3 => /usr/lib64/libcroco-0.6.so.3 (0x00007fb403557000)
libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007fb403244000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007fb40303e000)
libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007fb402e38000)
libicudata.so.60 => /usr/lib64/libicudata.so.60 (0x00007fb40128f000)
libgmodule-2.0.so.0 => /usr/lib64/libgmodule-2.0.so.0 (0x00007fb40108b000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fb400e74000)
libmount.so.1 => /lib64/libmount.so.1 (0x00007fb400c19000)
libpangoft2-1.0.so.0 => /usr/lib64/libpangoft2-1.0.so.0 (0x00007fb400a05000)
libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007fb4007c2000)
libfribidi.so.0 => /usr/lib64/libfribidi.so.0 (0x00007fb4005aa000)
libffi.so.6 => /usr/lib64/libffi.so.6 (0x00007fb4003a1000)
libpixman-1.so.0 => /usr/lib64/libpixman-1.so.0 (0x00007fb4000f9000)
libEGL.so.1 => /usr/lib64/opengl/nvidia/lib/libEGL.so.1 (0x00007fb3ffee5000)
libxcb-shm.so.0 => /usr/lib64/libxcb-shm.so.0 (0x00007fb3ffce1000)
libxcb-render.so.0 => /usr/lib64/libxcb-render.so.0 (0x00007fb3ffad3000)
libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007fb3ff8c9000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x00007fb3ff657000)
libblkid.so.1 => /lib64/libblkid.so.1 (0x00007fb3ff406000)
libharfbuzz.so.0 => /usr/lib64/libharfbuzz.so.0 (0x00007fb3ff157000)
libgraphite2.so.3 => /usr/lib64/libgraphite2.so.3 (0x00007fb3fef2a000)

crash archive output
----------------------------------------------------------------------
#TIME Thu Sep 6 18:29:17 2018 - Uptime 00:00:02 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve v15.0.1.003 (Linux/Clang)

/opt/resolve/bin/resolve() [0x40abbd9]
/opt/resolve/bin/resolve(_ZN7BtDebug14ReportSegfaultEiP7siginfoPv+0x6c) [0x40ab1dc]
/lib64/libpthread.so.0(+0x144e0) [0x7fefeea764e0]
/lib64/libc.so.6(gsignal+0x110) [0x7fefecabef70]
/lib64/libc.so.6(abort+0x17d) [0x7fefecac0b3d]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x939c) [0x7ff00739c39c]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x94c6) [0x7ff00739c4c6]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x22036) [0x7ff0073b5036]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x223a1) [0x7ff0073b53a1]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x228f7) [0x7ff0073b58f7]
/opt/resolve/bin/../libs/libc++abi.so.1(__gxx_personality_v0+0x6c) [0x7ff0073b5ddc]
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/libgcc_s.so.1(_Unwind_RaiseException+0x14b) [0x7fefece5b12b]
/opt/resolve/bin/../libs/libc++abi.so.1(__cxa_throw+0x66) [0x7ff0073b49c6]
/opt/resolve/bin/resolve() [0x949824]
/opt/resolve/bin/resolve() [0x949019]
/opt/resolve/bin/resolve() [0x940ada]
/opt/resolve/bin/resolve() [0x909e2c]
/opt/resolve/bin/resolve() [0x90753e]
/opt/resolve/bin/resolve() [0x906185]
/opt/resolve/bin/resolve() [0x905a68]
/opt/resolve/bin/resolve() [0x942560]
/opt/resolve/bin/resolve(_ZN7BtDebug14ReportSegfaultEiP7siginfoPv+0x4d7) [0x40ab647]
/lib64/libpthread.so.0(+0x144e0) [0x7fefeea764e0]
/lib64/libc.so.6(gsignal+0x110) [0x7fefecabef70]
/lib64/libc.so.6(abort+0x17d) [0x7fefecac0b3d]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x939c) [0x7ff00739c39c]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x94c6) [0x7ff00739c4c6]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x22036) [0x7ff0073b5036]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x223a1) [0x7ff0073b53a1]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x228f7) [0x7ff0073b58f7]
/opt/resolve/bin/../libs/libc++abi.so.1(__gxx_personality_v0+0x6c) [0x7ff0073b5ddc]
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/libgcc_s.so.1(_Unwind_RaiseException+0x14b) [0x7fefece5b12b]
/opt/resolve/bin/../libs/libc++abi.so.1(__cxa_throw+0x66) [0x7ff0073b49c6]
/opt/resolve/bin/resolve() [0x949824]
/opt/resolve/bin/resolve() [0x949019]
/opt/resolve/bin/resolve() [0x940ada]
/opt/resolve/bin/resolve() [0x909e2c]
/opt/resolve/bin/resolve() [0x90753e]
/opt/resolve/bin/resolve() [0x906185]
/opt/resolve/bin/resolve() [0x905a68]
/opt/resolve/bin/resolve() [0x942560]
/opt/resolve/bin/resolve(_ZN7BtDebug14ReportSegfaultEiP7siginfoPv+0x4d7) [0x40ab647]
/lib64/libpthread.so.0(+0x144e0) [0x7fefeea764e0]
/lib64/libc.so.6(gsignal+0x110) [0x7fefecabef70]
/lib64/libc.so.6(abort+0x17d) [0x7fefecac0b3d]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x939c) [0x7ff00739c39c]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x94c6) [0x7ff00739c4c6]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x22036) [0x7ff0073b5036]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x223a1) [0x7ff0073b53a1]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x228f7) [0x7ff0073b58f7]
Signal Number = 6


ResolveDebug Output
----------------
==========[CRASH DUMP]==========
Please send this to support:

#TIME Thu Sep 6 18:29:17 2018 - Uptime 00:00:02 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve v15.0.1.003 (Linux/Clang)

/opt/resolve/bin/resolve() [0x40abbd9]
/opt/resolve/bin/resolve(_ZN7BtDebug14ReportSegfaultEiP7siginfoPv+0x6c) [0x40ab1dc]
/lib64/libpthread.so.0(+0x144e0) [0x7fefeea764e0]
/lib64/libc.so.6(gsignal+0x110) [0x7fefecabef70]
/lib64/libc.so.6(abort+0x17d) [0x7fefecac0b3d]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x939c) [0x7ff00739c39c]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x94c6) [0x7ff00739c4c6]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x22036) [0x7ff0073b5036]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x223a1) [0x7ff0073b53a1]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x228f7) [0x7ff0073b58f7]
/opt/resolve/bin/../libs/libc++abi.so.1(__gxx_personality_v0+0x6c) [0x7ff0073b5ddc]
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/libgcc_s.so.1(_Unwind_RaiseException+0x14b) [0x7fefece5b12b]
/opt/resolve/bin/../libs/libc++abi.so.1(__cxa_throw+0x66) [0x7ff0073b49c6]
/opt/resolve/bin/resolve() [0x949824]
/opt/resolve/bin/resolve() [0x949019]
/opt/resolve/bin/resolve() [0x940ada]
/opt/resolve/bin/resolve() [0x909e2c]
/opt/resolve/bin/resolve() [0x90753e]
/opt/resolve/bin/resolve() [0x906185]
/opt/resolve/bin/resolve() [0x905a68]
/opt/resolve/bin/resolve() [0x942560]
/opt/resolve/bin/resolve(_ZN7BtDebug14ReportSegfaultEiP7siginfoPv+0x4d7) [0x40ab647]
/lib64/libpthread.so.0(+0x144e0) [0x7fefeea764e0]
/lib64/libc.so.6(gsignal+0x110) [0x7fefecabef70]
/lib64/libc.so.6(abort+0x17d) [0x7fefecac0b3d]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x939c) [0x7ff00739c39c]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x94c6) [0x7ff00739c4c6]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x22036) [0x7ff0073b5036]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x223a1) [0x7ff0073b53a1]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x228f7) [0x7ff0073b58f7]
/opt/resolve/bin/../libs/libc++abi.so.1(__gxx_personality_v0+0x6c) [0x7ff0073b5ddc]
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/libgcc_s.so.1(_Unwind_RaiseException+0x14b) [0x7fefece5b12b]
/opt/resolve/bin/../libs/libc++abi.so.1(__cxa_throw+0x66) [0x7ff0073b49c6]
/opt/resolve/bin/resolve() [0x949824]
/opt/resolve/bin/resolve() [0x949019]
/opt/resolve/bin/resolve() [0x940ada]
/opt/resolve/bin/resolve() [0x909e2c]
/opt/resolve/bin/resolve() [0x90753e]
/opt/resolve/bin/resolve() [0x906185]
/opt/resolve/bin/resolve() [0x905a68]
/opt/resolve/bin/resolve() [0x942560]
/opt/resolve/bin/resolve(_ZN7BtDebug14ReportSegfaultEiP7siginfoPv+0x4d7) [0x40ab647]
/lib64/libpthread.so.0(+0x144e0) [0x7fefeea764e0]
/lib64/libc.so.6(gsignal+0x110) [0x7fefecabef70]
/lib64/libc.so.6(abort+0x17d) [0x7fefecac0b3d]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x939c) [0x7ff00739c39c]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x94c6) [0x7ff00739c4c6]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x22036) [0x7ff0073b5036]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x223a1) [0x7ff0073b53a1]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x228f7) [0x7ff0073b58f7]
Signal Number = 6



================================
[0x7fefe547c580] | Main | INFO | 2018-09-06 18:29:17,646 | Updating display GPU information...
gentwo@local /opt/resolve $

Rolling output[0x7fefe547c580] | Main | INFO | 2018-09-06 18:29:17,582 | Updating display GPU information...
[0x7fefe547c580] | Main | INFO | 2018-09-06 18:29:17,586 | Updating display GPU information...
[0x7fefe547c580] | Main | INFO | 2018-09-06 18:29:17,589 | Updating display GPU information...
[0x7fefe547c580] | Main | INFO | 2018-09-06 18:29:17,593 | Updating display GPU information...
[0x7fefe547c580] | Main | INFO | 2018-09-06 18:29:17,597 | Updating display GPU information...
[0x7fefe547c580] | Main | INFO | 2018-09-06 18:29:17,601 | Updating display GPU information...
[0x7fefe547c580] | Main | INFO | 2018-09-06 18:29:17,605 | Updating display GPU information...
[0x7fefe547c580] | Main | INFO | 2018-09-06 18:29:17,608 | Updating display GPU information...
[0x7fefe547c580] | Main | INFO | 2018-09-06 18:29:17,612 | Updating display GPU information...
[0x7fefe547c580] | Main | INFO | 2018-09-06 18:29:17,616 | Updating display GPU information...
[0x7fefe547c580] | Main | INFO | 2018-09-06 18:29:17,620 | Updating display GPU information...
[0x7fefe547c580] | Main | INFO | 2018-09-06 18:29:17,623 | Updating display GPU information...
[0x7fefe547c580] | Main | INFO | 2018-09-06 18:29:17,627 | Updating display GPU information...
[0x7fefe547c580] | Main | INFO | 2018-09-06 18:29:17,631 | Updating display GPU information...
[0x7fefe547c580] | Main | INFO | 2018-09-06 18:29:17,634 | Updating display GPU information...
[0x7fefe547c580] | Main | INFO | 2018-09-06 18:29:17,638 | Updating display GPU information...
[0x7fefe547c580] | Main | INFO | 2018-09-06 18:29:17,642 | Updating display GPU information...
[0x7fefe547c580] | Main | INFO | 2018-09-06 18:29:17,646 | Updating display GPU information...

if you would just write one single line about your actual hardware configuration, it would be easier to guess the cause of your issue.

yes -- fixing the obvious flaws of the actual installer, would be really an important improvement, but the other claim -- i.e. flatpack deliveries -- is IMHO nearly impossible to realize right now.

If you were a dev at BMD, how would you approach the issue, based on what we know? Let's assume the file locations would be fixed, which, in itself, should be a lot easier to accomplish.

Fresh install of Fedora 28 and Resolve v15.0.1.003

Cannot load/import any media files. I've tried mp4 and avi.

Importing mp4, there is no notification or change in the ui but I see this in the logs

Code: Select all

 Codec (avc1) not Found in Repository

Any idea where Resolve is looking for the codecs? I think that may be the issue.

If you were a dev at BMD, how would you approach the issue, based on what we know? Let's assume the file locations would be fixed, which, in itself, should be a lot easier to accomplish.

i think, i would simply create native .deb and .rpm packages and host them in private repositories.

making native packages for this two families of linux distributions isn't rocket science -- to the contrary, it's a more or less trivial task considering resolves complexity. even very simple amateurish software projects successfully mastered this challenge.

native packages and delivery channels are not only the most mature solution for this kind of task, they also provide reliable dependency management services, which go far beyond simple repacking, which only supports a little bit of accidental overwriting protection and cleaner uninstallability. resolving package dependencies, e.g. handling proper nvidia-setup-requirements and ensure OpenCL presence, is IMHO a much better solution to prevent constantly recurring installation troubles than verbally answering in a forum or FAQ: "you have to install this or that in advance to make the application running".

but the most important improvement i would see in automatic tests of the generated packages on the few actual target platforms by CI/CD infrastructure -- a kind of QA procedure, which has become more or less standard for any serious software project nowadays.

most of the mentioned necessary improvements do not need extensive or overly complicated additional development efforts. it's really simple stuff. it also doesn't have to be realized in one huge step. in practice it's much more satisfaying, if improvements come in better manageable small but continuous increments, which really try to solve reported issues and discontent on the user side quickly and adequate. that's exactly, what i really miss in BMDs linux efforts. most of the still open issues (except the sound support) are now -- i.e. one and a half year after the launch of resolve for linux -- just the same as we reported them already within the first weeks after launch. nearly nothing has changed to the better. and that's really frustrating.

Most of the DaVinci Resolve installation issues would be solved by Flatpak. I use Kdenlive installed via Flatpak on Ubuntu 18.04. The installation process was very simple and for the first time I get regular Kdenlive updates. It would be great to have DaVinci Resolve available for Linux via Flatpak.

Thank you, thank you, thank you!
For the first time in my life I have a great NLE software on my portable with GNU/Linux!
I just made a fresh install of the Linux Mint 19 with the multimedia option activated. After I did the update, I changed the video driver to Nvidia and then did "sudo apt-get install nvidia-cuda-toolkit"
After that I installed DaVinci Resolve with sh command, inserted the dongle and IT WORKS.
You made my dreams come true .

i think, i would simply create native .deb and .rpm packages and host them in private repositories.

That sounds like a simple and doable suggestion. With the .rpm, BMD could keep their existing "pro config" with CentOS. The .deb would essentially replace Daniel's script and allow them tap into the expanding user base on Ubuntu, et al. The way you describe it sounds like a win-win, for BMD and Linux users.

what i really miss in BMDs linux efforts. most of the still open issues (except the sound support) are now -- i.e. one and a half year after the launch of resolve for linux -- just the same as we reported them already within the first weeks after launch. nearly nothing has changed to the better. and that's really frustrating.

Hear, hear. To be fair, BMD have addressed some bugs on the interim, like the notorious English (US) session, which have made the software more usable.

Still, I wonder if the problem has been, somewhat, that we've been asking the wrong questions, or passing on the wrong suggestions. This is due to obvious reasons. Anyone reading through this thread can see it's been a huge trial and error to get the software running on various Linux configs (many of which are quite sufficient to run it). Looking back, all those quirks have served as distractions.

With native packaging, we would've been on easy street since Day 1. That's still to come, as BMD have gone for the popular vote with System Audio and h.264 encoding. A case can be made, tho, that native packages would solve most (all) installation issues. Daniel's script is awesome and direly needed, but it's getting embarrassing to see BMD coast their way around the problem.

To the good people at BMD, since you're reading this, pull your finger out already. Resolve is a wonderful software and it's great to have on Linux. But that installation is still a bloody mess and your product and user base both deserve better. Thank you.

I got Debian 10 fresh install, used makeresolvedeb and still nothing.
This time strace shows:

futex(0x7fec6f938f38, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7fec6f938f38, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7fec707bd8b0, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7fec7357305c, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7fec73573068, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7ffee16ae294, FUTEX_UNLOCK_PI) = -1 EPERM (Operation not permitted)
futex(0x7fec8ccfbd98, FUTEX_WAKE_PRIVATE, 2147483647) = 0
mmap(NULL, 2101248, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fec6debc000
mmap(NULL, 4198400, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fec6dabb000
mmap(NULL, 1585152, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fec6d938000
mmap(NULL, 1585152, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fec6d7b5000
futex(0x7fec816e9598, FUTEX_WAKE_PRIVATE, 2147483647) = 0
--- SIGILL {si_signo=SIGILL, si_code=ILL_ILLOPN, si_addr=0x7fec89147198} ---
+++ killed by SIGILL +++

The only console output is:

Illegal instruction

In syslog i see this only line related:

Sep 11 14:50:32 resolver kernel: [ 7200.505140] traps: resolve[14833] trap invalid opcode ip:7f61b8a43198 sp:7ffedc500ae0 error:0 in fusionscript.so[7f61b8881000+389000]

ldd shows no missing libs, nvidia/cuda installed.
Any idea what to try? Replace all the hardware is the last resort

The only console output is:

Illegal instruction

In syslog i see this only line related:

Sep 11 14:50:32 resolver kernel: [ 7200.505140] traps: resolve[14833] trap invalid opcode ip:7f61b8a43198 sp:7ffedc500ae0 error:0 in fusionscript.so[7f61b8881000+389000]

what kind of CPU do you have in your machine?

i have seen similar error messages on a 10 year old CoreDuo processor recently, triggert by some scientific software. it's a very rare error. but that's also caused by the fact, that we usually do not try to utilize this kind of highly optimized and performance demanding software on very old hardware.

look for the suported "see*" flags in /proc/cpuinfo -- that's most likely the cause.

what kind of CPU do you have in your machine?

i have seen similar error messages on a 10 year old CoreDuo processor recently, triggert by some scientific software. it's a very rare error. but that's also caused by the fact, that we usually do not try to utilize this kind of highly optimized and performance demanding software on very old hardware.

look for the suported "see*" flags in /proc/cpuinfo -- that's most likely the cause.

I am actually suspecting something related to what you mentioned. But it's a relatively modern CPU: phenom X6.
Also on windows resolve v15.0.1 runs just fine for me(15.1 failed, see here). So if it's some CPU flag related, it should be recompiled. I can try with Intel CPU, could be useful to someone

update

Unable to find anything related to CPU features required in
configuration guide PDF
BUT! i found that in this topic and also this one SSE 4.1 was mentioned as necessary to run a modern fusion.
Windows binary are just less "optimized" then, compiled without SSE4 requirement and so works on older hardware.

Is there any option to bypass fusion on resolve boot up?

update2

That was it. On linux you just can't run resolve 15 on any CPU without SSE4 extension.
There is a tool to emulate it (it's Intel's, but runs fine on AMD also)
Intel Software Development Emulator, so i was able to avoid this "trap invalid opcode" just fine.
Performance is affected badly, maybe some switch is needed for SDE to work faster

Still this is not good. As i mentioned - windows version of resolve works without this trick.

So If you get an:
Illegal instruction
Message and /opt/resolve/logs/ResolveDebug.txt is not updated with details, you lack SSE4 (SSE4a is not the same thing). Also your syslog will contain:

Sep 11 21:56:32 resolver kernel: [ 5412.093796] traps: resolve[9152] trap invalid opcode ip:7ff51f912198 sp:7ffdcbf91330 error:0 in fusionscript.so[7ff51f750000+389000]

You can:
1 - wait for a patch
2 - try to run as me (Intel SDE, explained above)
3 - get at least "FX-Series" amd processor or any intel with SSE4 support

P/S will hope for an update on this from devs, clear bug for me.
Thanks Martin for pointing into the right direction!

Also noticed that on "Segmentation fault" error you may need to look at /opt/resolve/logs/ResolveDebug.txt last lines for:

Signal Number = 6

or a message:

[0x7fdf4c28db00] | Main | INFO | 2018-09-11 21:46:28,043 | Updating display GPU information...
OpenCL error -1001, GPUPropertiesUtilUnix.cpp:338.
terminating

You'll need to: apt purge mesa-opencl-icd or look into icd you have following this guide

This in particular helped me: apt install beignet clinfo

P/S will hope for an update on this from devs, clear bug for me.

SSE4 was introduced a decade ago (around 2008). So it's clearly a bug for you that Resolve utilises and requires SSE4? I'd say you should get a "modern platform" instead, as stated in the requirements:

System requirements
‚ Modern computer platform with at least a Quad core CPU and a powerful GPU

br Hari

But that installation is still a bloody mess and your product and user base both deserve better. Thank you.

"That installation" just worked perfectly, as I've tested a few days ago on Red Hat Enterprise Linux 7.5.

It's kind of ridiculous how a few guys in here describe the installer as "buggy" and full of "flaws". It gets the job done on the supported platforms.
Regarding native packaging for <insert random linux distribution here>, that's usually the job done by maintainers of that distro. Only a very very small percentage of upstream projects has native downstream packages for all the major distributions. A lot of stuff just comes as source tar.gz. With a binary only release like Resolve, things are not getting easier.
I'm not saying that the installer is perfect or would be better than e.g. RPM packages. And I fully agree that broader distribution support would be a good thing, but it's unfair and naive to describe the current installer as broken because it won't work on whatever distribution. It gives a working installation on the supported Linux variants. So some of you guys might consider better wording when asking BMD for additional features.

SSE4 was introduced a decade ago (around 2008). So it's clearly a bug for you that Resolve utilizes and requires SSE4? I'd say you should get a "modern platform" instead, as stated in the requirements:

I can agree only partially with you. My cpu is really not the bleeding edge tec, but it's a 1090t phenom 2 x6 (2 additional cores above of what's stated in reqs) introduced in 2010, and it runs resolve really just fine...on windows.
If a software runs fine on one platform and refuses to run on another, given identical hardware - i call it a bug.

"That installation" just worked perfectly, as I've tested a few days ago on Red Hat Enterprise Linux 7.5.
It's kind of ridiculous how a few guys in here describe the installer as "buggy" and full of "flaws". It gets the job done on the supported platforms.

no! -- i have to disagree!

if you do a fully automatic installation of resolve on a clean CentOS base image, as GitLab always does it, when it creates my docker images, you'll see, that the installer requires some little unix tools already installed on the system or the installation will silently break and leave a ugly mess on the system. the reason for this annoying behavior has to be seen in the fact, that the installation script doesn't check in advance, if all of the required little tools are actually available on the machine. it just tries to execute them by their names and doesn't handle any errors, if they do not exist. that's IMHO a really unacceptable flaw.

it's very likely, that you will not stumble over this shortcoming on a real world machine, where you have already installed a lot of other useful software for your daily work. that's exactly the reason, why you should test software automatically by CI/CD systems on really clean operating system images resp. containers to get more adequate quality control under perfectly reproduceable test conditions.

and although i wouldn't go as far as Boris, when it comes to hardware independence and cross platform compatibility desires, because this qualities are really hard to archive in real world, i still would see it as very useful, if resolve for linux would indeed work in a very slow but reliable manner on very simple hardware resp. those envrionments, which you usually utilize for this kind of automatic tests on cloud infrastructure. sure, there are workarounds available, to handle this kind of tests on some dedicated other machines, which provide the necessary nvidia cards etc. (e.g. gitlab-runner supports this kind of operations very well), but it would make live much easier, if resolve for linux would behave little bit more like the editions for the other platforms in this respect.

Plus this topic thread would be a fraction of the size it is now if there were some checks made in the installer before it just happily installs.

On the other hand, I'm happy that the script doesn't check that it's a CentOS/RHEL distro and quits, or whether there's a Titan GPU present, because then I'd really be out of luck!

Martin,

you might have a different view of prerequisites on your continuous integration system. The RHEL installation that I've done (and it was from scratch, as I was moving from Fedora to RHEL due to amdgpu-pro supportability requirements) was with "Graphical Environment" selected (bear with me, I don't remember the exact name in anaconda). That's for sure different form a "minimal" installation, but someone wanting to run resolve, will for sure need the window manager & co and hence select a desktop environment in the installer. Right after the RHEL installation, I did pull amdgpu-pro from the homepage, and then the Resolve installer. As said, it went through without any hassle.

Your point is partially valid, a smart installer wouldn't just assume some dependencies but make sure that they're there. Again, I'm not arguing that there is no room for improvement in the current installer, but describing it as "broken" is just not factual.

Regarding Boris' issue, technically I'd prefer if Resolve would fail gracefully. If it's a design decision to require SSE4 on Linux that's fine with me, but it shall print that before startup and not just crash with an SIG ILL. But still, there are probably only very few people wanting to run on such a limited CPU setup, hence not a lot to gain for BMD by working around SSE4.

br Hari

i have a question about fusion integration with dr in linux.

i'm successfully running dr v15.0.0B.037 on ubuntu studio. i just installed fusion and and it seems to open ok. when i open dr, however, the dr fusion menu contents are grayed. is that right? should the contents just show automatically? to i have to input a path somewhere? i remember having to make some links to get dr to work in ubuntu. might i need to do something similar to get fusion tied in with dr?

thanks for any advice,
g

You need to select a clip to have the MediaIn and MediaOut nodes been shown on the fusion page...

Either select the clip in the edit window or open the clip window in fusion tab to select it...

thanks. yes, i have tried selecting a clip in the edit page timeline but the menu remains grayed.

thanks again,
g

You have to have a clip in the timeline before you can use the Fusion tab in Resolve 15. It can be a Fusion Title, a generator, an image, or a video clip.

thanks. yes, i have tried selecting a clip in the edit page timeline but the menu remains grayed.

go to the fusion page!

edit: oops. looks like there's a fusion tab i hadn't noticed at the bottom of the screen. will try that when i get back to dr.

thanks for the replies. i'm not in front of that system right now but wanted to clarify, i should manually open the fusion program after selecting a clip? i was assuming there would be a more direct linkage between dr and the fusion program, like via the menus.

thanks again,
g

Any news on 15.1? I really want to test the BM raw! Could be an awesome codec for us linux users.

Sent from my SM-G955U using Tapatalk

Any news on 15.1?

no -- we are all busy with celebrating the most buggy release in resolves history.

haha awesome! what do you guys think about the BMraw and what it means for linux?

Hey mrooted, I think you got missed, but unless you shelled out for the Studio version, you probably can't import any media in h.264, or really any format that comes out of a consumer camera... I've pretty much resigned myself to using ffmpeg to transcode my GoPro and Lumix G7 footage to ProRes for editing because I need that $300 or so to go towards a graphics card that'll run Resolve better!

This is the syntax I use, but it's very slow and makes files about 10x the size of the original, however, it actually plays back nicely in Resolve.

Code: Select all

ffmpeg -i inputfile.MP4 -vcodec prores -acodec pcm_s16le -ar 48000 -ac 2 -f mov outputfile.mov

Fresh install of Fedora 28 and Resolve v15.0.1.003

Cannot load/import any media files. I've tried mp4 and avi.

Importing mp4, there is no notification or change in the ui but I see this in the logs

Code: Select all

 Codec (avc1) not Found in Repository

Any idea where Resolve is looking for the codecs? I think that may be the issue.

Any news on 15.1?

no -- we are all busy with celebrating the most buggy release in resolves history.

Haha! That was a good one Martin

I've been struggling trying to get braw decoding running but I'm getting nothing but crashing GPU's. I really like where it's going though!

Code: Select all

[0x7fd14c627700] | IO                   | ERROR | 2018-09-18 17:54:41,074 | Braw (SubmitGPUProcessJob) HRESULT = 0x80000008
[0x7fd14c627700] | IO                   | ERROR | 2018-09-18 17:54:41,087 | Braw (SubmitGPUProcessJob) HRESULT = 0x80000008
CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:223.
[0x7fd14c627700] | GPUManager           | ERROR | 2018-09-18 17:54:41,095 | Exception caught while running GPU algorithms: an illegal memory access was encountered.
Ignoring CUDA error 77: 'an illegal memory access was encountered', CudaBoardManager.cpp:415.
Ignoring CUDA error 77: 'an illegal memory access was encountered', CudaBoardManager.cpp:415.
[0x7fd14c627700] | GPUManager           | INFO  | 2018-09-18 17:54:41,095 | Flushing GPU memory...
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
Ignoring CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:457.
CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:30.
[0x7fd14c627700] | GPUManager           | WARN  | 2018-09-18 17:54:41,095 | Exception caught for allocate Linear 33.8 MiB. Clearing pool to retry...
CUDA error 77: 'an illegal memory access was encountered', SimpleCudaMemCacheMgr.cpp:30.
[0x7fd14c627700] | GPUManager           | ERROR | 2018-09-18 17:54:41,095 | Exception caught while running GPU algorithms: an illegal memory access was encountered.
Urgent message: The GPU failed to perform image processing because of an error.||Error Code: 77.
CUDA error 77: 'an illegal memory access was encountered', CudaBoardManager.cpp:214.
[0x7fd14c627700] | GPUManager           | ERROR | 2018-09-18 17:54:41,096 | Error occured while setting up job completion callbacks on board [0|0]<GeForce GTX 1080>: an illegal memory access was encountered

BTW, MakeResolveDeb for version 15.1 is released om my website http://www.danieltufvesson.com/makeresolvedeb. It just doesn't feel right posting here every time. This thread is getting pretty long as it is already.

Hello everyone, I have installed Resolve 15 on Arch and it works pretty much ok, but when I try to mask something in the Color tab and try to add a mask and resizing a masking "Window" (I'm referring to the rectangle, circle etc. shapes) the program just crashes. I get no significative output in the terminal window. Here's the output when I run the program

Code: Select all

ActCCMessage Already in Table: Code= 2282, Mode=  0, Level=  0, CmdKey= 8, Option= 0
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
15.0.1 (#003) Linux/Clang
Main thread starts: E4764B40
log4cxx: No appender could be found for logger (Undefined).
log4cxx: Please initialize the log4cxx system properly.
Discard all samples (playback) or generate zero samples (capture)
PulseAudio Sound Server
Default ALSA Output (currently PulseAudio Sound Server)
HDA Intel PCH, ALC298 AnalogDefault Audio Device
HDA Intel PCH, ALC298 AnalogFront speakers
HDA Intel PCH, ALC298 Analog2.1 Surround output to Front and Subwoofer speakers
HDA Intel PCH, ALC298 Analog4.0 Surround output to Front and Rear speakers
HDA Intel PCH, ALC298 Analog4.1 Surround output to Front, Rear and Subwoofer speakers
HDA Intel PCH, ALC298 Analog5.0 Surround output to Front, Center and Rear speakers
HDA Intel PCH, ALC298 Analog5.1 Surround output to Front, Center, Rear and Subwoofer speakers
HDA Intel PCH, ALC298 Analog7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
HDA Intel PCH, HDMI 0HDMI Audio Output
HDA Intel PCH, HDMI 1HDMI Audio Output
HDA Intel PCH, HDMI 2HDMI Audio Output
HDA Intel PCH, HDMI 3HDMI Audio Output
HDA Intel PCH, HDMI 4HDMI Audio Output
Discard all samples (playback) or generate zero samples (capture)
PulseAudio Sound Server
Default ALSA Output (currently PulseAudio Sound Server)
HDA Intel PCH, ALC298 AnalogDefault Audio Device
HDA Intel PCH, ALC298 AnalogFront speakers
HDA Intel PCH, ALC298 Analog2.1 Surround output to Front and Subwoofer speakers
HDA Intel PCH, ALC298 Analog4.0 Surround output to Front and Rear speakers
HDA Intel PCH, ALC298 Analog4.1 Surround output to Front, Rear and Subwoofer speakers
HDA Intel PCH, ALC298 Analog5.0 Surround output to Front, Center and Rear speakers
HDA Intel PCH, ALC298 Analog5.1 Surround output to Front, Center, Rear and Subwoofer speakers
HDA Intel PCH, ALC298 Analog7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
HDA Intel PCH, HDMI 0HDMI Audio Output
HDA Intel PCH, HDMI 1HDMI Audio Output
HDA Intel PCH, HDMI 2HDMI Audio Output
HDA Intel PCH, HDMI 3HDMI Audio Output
HDA Intel PCH, HDMI 4HDMI Audio Output
FusionScript Server [6533] Started
Host 'Fusion' [6032] Added


and the moment it crushes only these two lines add up to the output

Code: Select all

Host 'Fusion' Killed
FusionScript Server [6533] Terminated

I can move the masking Windows, but I can't rotate or resize them Any suggestions?

Hello everyone, I have installed Resolve 15 on Arch and it works pretty much ok, but when I try to mask something in the Color tab and try to add a mask and resizing a masking "Window" (I'm referring to the rectangle, circle etc. shapes) the program just crashes.

that's a reproducible flaw, which i also noticed on my machines.

I can move the masking Windows, but I can't rotate or resize them Any suggestions?

you can change the shape of the power windows via the nomeric entry fields without a crash. i therefore would guess, it's more related to the UI resp. mouse pointer events or overlay handling...

Hello everyone, I have installed Resolve 15 on Arch and it works pretty much ok, but when I try to mask something in the Color tab and try to add a mask and resizing a masking "Window" (I'm referring to the rectangle, circle etc. shapes) the program just crashes.

that's a reproducible flaw, which i also noticed on my machines.

I can move the masking Windows, but I can't rotate or resize them Any suggestions?

you can change the shape of the power windows via the nomeric entry fields without a crash. i therefore would guess, it's more related to the UI resp. mouse pointer events or overlay handling...

Thank you very much: your workaround worked. It is a bit tricky, but at least it did the job!

Just as a curious side question here...

Is this thread regarding installation issues on Linux or regarding the more buggy resolve Linux version? (o;

I would suggest opening a new thread for bugs which are not related to installation like I do...
That way BMD sees the many Linux bug threads

Just as a curious side question here...

Is this thread regarding installation issues on Linux or regarding the more buggy resolve Linux version? (o;

I would suggest opening a new thread for bugs which are not related to installation like I do...
That way BMD sees the many Linux bug threads

I'm sorry if I posted here, but this looked to me like the best place to ask such a question, even if it's not properly related to installation, because the subforum description says "Get answers to your questions about color grading, editing and finishing with DaVinci Resolve.". Usually forums prefer that people don't open too many threads if existing ones are fine for their questions. Maybe a subforum for specific Linux issues could be added or at least a differen thread for Linux issues not related to installation.

Hi there,

I'm trying to install Resolve 15.1 on OpenSurce Leap 42.3.
Hardware : CPU 4 x Intel Core i5-6500 CPU @ 3.20GHz, RAM 7.7 Gio, Graphics card AMD FirePro V3900

I followed the instruction of the post dedicated to Opensuse Leap and checked that no library is missing.

Resolve launched once and crashed when I had to choose the working folder. I selected a remote folder. Since that crash I haven't be able to restart it.

With the command line /opt/resolve/bin/resolve, I got the following :

Code: Select all

~> /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
15.1 (#025) Linux/Clang
Main thread starts: 29045B00
[0x7f0229045b00] | Undefined            | INFO  | 2018-09-22 08:33:41,285 | --------------------------------------------------------------------------------
[0x7f0229045b00] | Undefined            | INFO  | 2018-09-22 08:33:41,285 | Loaded log config from /opt/resolve/configs/log-conf.xml
[0x7f0229045b00] | Undefined            | INFO  | 2018-09-22 08:33:41,285 | --------------------------------------------------------------------------------
Erreur de segmentation (core dumped)

I checked the libraries :

Code: Select all

~> ldd /opt/resolve/bin/resolve
        linux-vdso.so.1 (0x00007ffedf3e5000)
        libc++.so.1 => /opt/resolve/bin/../libs/libc++.so.1 (0x00007f0c13762000)
        libc++abi.so.1 => /opt/resolve/bin/../libs/libc++abi.so.1 (0x00007f0c13533000)
        libcudart.so.9.1 => /opt/resolve/bin/../libs/libcudart.so.9.1 (0x00007f0c132c5000)
        libnvrtc.so.9.1 => /opt/resolve/bin/../libs/libnvrtc.so.9.1 (0x00007f0c11b98000)
        libQt5Concurrent.so.5 => /opt/resolve/bin/../libs/libQt5Concurrent.so.5 (0x00007f0c11b92000)
        libQt5Core.so.5 => /opt/resolve/bin/../libs/libQt5Core.so.5 (0x00007f0c115b2000)
        libQt5Gui.so.5 => /opt/resolve/bin/../libs/libQt5Gui.so.5 (0x00007f0c11047000)
        libQt5Multimedia.so.5 => /opt/resolve/bin/../libs/libQt5Multimedia.so.5 (0x00007f0c10f63000)
        libQt5Network.so.5 => /opt/resolve/bin/../libs/libQt5Network.so.5 (0x00007f0c10e5e000)
        libQt5OpenGL.so.5 => /opt/resolve/bin/../libs/libQt5OpenGL.so.5 (0x00007f0c10dfa000)
        libQt5Sql.so.5 => /opt/resolve/bin/../libs/libQt5Sql.so.5 (0x00007f0c10cb3000)
        libQt5Svg.so.5 => /opt/resolve/bin/../libs/libQt5Svg.so.5 (0x00007f0c10c5a000)
        libQt5Widgets.so.5 => /opt/resolve/bin/../libs/libQt5Widgets.so.5 (0x00007f0c105e0000)
        libQt5Xml.so.5 => /opt/resolve/bin/../libs/libQt5Xml.so.5 (0x00007f0c10597000)
        libQt5XmlPatterns.so.5 => /opt/resolve/bin/../libs/libQt5XmlPatterns.so.5 (0x00007f0c10105000)
        libGLU.so.1 => /usr/lib64/libGLU.so.1 (0x00007f0c0fe54000)
        libGL.so.1 => /usr/lib64/libGL.so.1 (0x00007f0c0fbea000)
        fusionscript.so => /opt/resolve/bin/../libs/Fusion/fusionscript.so (0x00007f0c0f5c7000)
        libluajit-5.1.so.2 => /opt/resolve/bin/../libs/libluajit-5.1.so.2 (0x00007f0c0f347000)
        libtbbmalloc.so.2 => /opt/resolve/bin/../libs/libtbbmalloc.so.2 (0x00007f0c0f108000)
        libtbbmalloc_proxy.so.2 => /opt/resolve/bin/../libs/libtbbmalloc_proxy.so.2 (0x00007f0c0ef03000)
        libXxf86vm.so.1 => /usr/lib64/libXxf86vm.so.1 (0x00007f0c0ecfc000)
        libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007f0c0ea5f000)
        libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007f0c0e84d000)
        libSM.so.6 => /usr/lib64/libSM.so.6 (0x00007f0c0e644000)
        libICE.so.6 => /usr/lib64/libICE.so.6 (0x00007f0c0e427000)
        libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f0c0e0e9000)
        libbz2.so.1 => /usr/lib64/libbz2.so.1 (0x00007f0c0ded9000)
        libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x00007f0c0db6e000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f0c0d871000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f0c0d66c000)
        librt.so.1 => /lib64/librt.so.1 (0x00007f0c0d464000)
        libavformat.so.57 => /opt/resolve/bin/../libs/libavformat.so.57 (0x00007f0c0d06a000)
        libavcodec.so.57 => /opt/resolve/bin/../libs/libavcodec.so.57 (0x00007f0c0bb01000)
        libavutil.so.55 => /opt/resolve/bin/../libs/libavutil.so.55 (0x00007f0c0b88e000)
        libMXF.so => /opt/resolve/bin/../libs/libMXF.so (0x00007f0c0b57e000)
        libSMDK-Linux-x64.so.4.7 => /opt/resolve/bin/../libs/libSMDK-Linux-x64.so.4.7 (0x00007f0c0b0d3000)
        libmp4decMT.so => /opt/resolve/bin/../libs/libmp4decMT.so (0x00007f0c0ada3000)
        libmp4encMT.so => /opt/resolve/bin/../libs/libmp4encMT.so (0x00007f0c0a837000)
        libsonyxavcenc.so => /opt/resolve/bin/../libs/libsonyxavcenc.so (0x00007f0c0a5c9000)
        liblog4cxx.so.10 => /opt/resolve/bin/../libs/liblog4cxx.so.10 (0x00007f0c0a0b2000)
        libapr-1.so.0 => /opt/resolve/bin/../libs/libapr-1.so.0 (0x00007f0c09e76000)
        libaprutil-1.so.0 => /opt/resolve/bin/../libs/libaprutil-1.so.0 (0x00007f0c09c48000)
        libopencv_calib3d.so.3.3 => /opt/resolve/bin/../libs/libopencv_calib3d.so.3.3 (0x00007f0c09888000)
        libopencv_core.so.3.3 => /opt/resolve/bin/../libs/libopencv_core.so.3.3 (0x00007f0c09384000)
        libopencv_features2d.so.3.3 => /opt/resolve/bin/../libs/libopencv_features2d.so.3.3 (0x00007f0c090d4000)
        libopencv_flann.so.3.3 => /opt/resolve/bin/../libs/libopencv_flann.so.3.3 (0x00007f0c08e68000)
        libopencv_highgui.so.3.3 => /opt/resolve/bin/../libs/libopencv_highgui.so.3.3 (0x00007f0c08c5f000)
        libopencv_imgcodecs.so.3.3 => /opt/resolve/bin/../libs/libopencv_imgcodecs.so.3.3 (0x00007f0c08a35000)
        libopencv_imgproc.so.3.3 => /opt/resolve/bin/../libs/libopencv_imgproc.so.3.3 (0x00007f0c082ac000)
        libopencv_ml.so.3.3 => /opt/resolve/bin/../libs/libopencv_ml.so.3.3 (0x00007f0c07ff8000)
        libopencv_objdetect.so.3.3 => /opt/resolve/bin/../libs/libopencv_objdetect.so.3.3 (0x00007f0c07daa000)
        libopencv_video.so.3.3 => /opt/resolve/bin/../libs/libopencv_video.so.3.3 (0x00007f0c07b5e000)
        libopencv_videoio.so.3.3 => /opt/resolve/bin/../libs/libopencv_videoio.so.3.3 (0x00007f0c07947000)
        libopencv_dnn.so.3.3 => /opt/resolve/bin/../libs/libopencv_dnn.so.3.3 (0x00007f0c0743d000)
        libcudnn.so.5 => /opt/resolve/bin/../libs/libcudnn.so.5 (0x00007f0c021ce000)
        libSonyRawDev.so.3 => /opt/resolve/bin/../libs/libSonyRawDev.so.3 (0x00007f0c01dc4000)
        libOpenCL.so.1 => /usr/lib64/libOpenCL.so.1 (0x00007f0c01ba7000)
        libgvc.so.6 => /opt/resolve/bin/../libs/libgvc.so.6 (0x00007f0c01906000)
        libcgraph.so.6 => /opt/resolve/bin/../libs/libcgraph.so.6 (0x00007f0c016f0000)
        libcdt.so.5 => /opt/resolve/bin/../libs/libcdt.so.5 (0x00007f0c014ea000)
        libxdot.so.4 => /opt/resolve/bin/../libs/libxdot.so.4 (0x00007f0c012e5000)
        libpathplan.so.4 => /opt/resolve/bin/../libs/libpathplan.so.4 (0x00007f0c010dd000)
        libDNxHR.so => /opt/resolve/bin/../libs/libDNxHR.so (0x00007f0c00942000)
        libimf.so => /opt/resolve/bin/../libs/libimf.so (0x00007f0c0047f000)
        libirc.so => /opt/resolve/bin/../libs/libirc.so (0x00007f0c00227000)
        libsvml.so => /opt/resolve/bin/../libs/libsvml.so (0x00007f0bff62b000)
        libintlc.so.5 => /opt/resolve/bin/../libs/libintlc.so.5 (0x00007f0bff3d5000)
        libArriRawSDK.so.5 => /opt/resolve/bin/../libs/libArriRawSDK.so.5 (0x00007f0bfd3d8000)
        libgvcodec.so => /opt/resolve/bin/../libs/libgvcodec.so (0x00007f0bfd1b0000)
        libCrmSdk.so.2.1 => /opt/resolve/bin/../libs/libCrmSdk.so.2.1 (0x00007f0bfaef0000)
        libid3-3.8.so.3 => /opt/resolve/bin/../libs/libid3-3.8.so.3 (0x00007f0bfacb3000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f0bfaa95000)
        libssl.so.1.0.0 => /opt/resolve/bin/../libs/libssl.so.1.0.0 (0x00007f0bfa81f000)
        libcrypto.so.1.0.0 => /opt/resolve/bin/../libs/libcrypto.so.1.0.0 (0x00007f0bfa3b6000)
        librsvg-2.so.2 => /usr/lib64/librsvg-2.so.2 (0x00007f0bfa180000)
        libCg.so => /opt/resolve/bin/../libs/libCg.so (0x00007f0bf9218000)
        libCgGL.so => /opt/resolve/bin/../libs/libCgGL.so (0x00007f0bf9097000)
        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f0bf8e7f000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f0bf8adc000)
        /lib64/ld-linux-x86-64.so.2 (0x000055d055667000)
        libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f0bf8753000)
        libexpat.so.1 => /usr/lib64/libexpat.so.1 (0x00007f0bf8528000)
        libxcb-dri3.so.0 => /usr/lib64/libxcb-dri3.so.0 (0x00007f0bf8324000)
        libxcb-present.so.0 => /usr/lib64/libxcb-present.so.0 (0x00007f0bf8121000)
        libxcb-sync.so.1 => /usr/lib64/libxcb-sync.so.1 (0x00007f0bf7f1b000)
        libxshmfence.so.1 => /usr/lib64/libxshmfence.so.1 (0x00007f0bf7d17000)
        libglapi.so.0 => /usr/lib64/libglapi.so.0 (0x00007f0bf7ae9000)
        libXdamage.so.1 => /usr/lib64/libXdamage.so.1 (0x00007f0bf78e6000)
        libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007f0bf76df000)
        libX11-xcb.so.1 => /usr/lib64/libX11-xcb.so.1 (0x00007f0bf74dd000)
        libxcb-glx.so.0 => /usr/lib64/libxcb-glx.so.0 (0x00007f0bf72c5000)
        libxcb-dri2.so.0 => /usr/lib64/libxcb-dri2.so.0 (0x00007f0bf70bf000)
        libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f0bf6e9f000)
        libdrm.so.2 => /usr/lib64/libdrm.so.2 (0x00007f0bf6c90000)
        libz.so.1 => /lib64/libz.so.1 (0x00007f0bf6a79000)
        libpng16.so.16 => /usr/lib64/libpng16.so.16 (0x00007f0bf683c000)
        libuuid.so.1 => /usr/lib64/libuuid.so.1 (0x00007f0bf6636000)
        liblzma.so.5 => /usr/lib64/liblzma.so.5 (0x00007f0bf640d000)
        libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f0bf61d1000)
        libcudart.so.7.5 => /opt/resolve/bin/../libs/libcudart.so.7.5 (0x00007f0bf5f72000)
        libgdk_pixbuf-2.0.so.0 => /usr/lib64/libgdk_pixbuf-2.0.so.0 (0x00007f0bf5d4e000)
        libgio-2.0.so.0 => /usr/lib64/libgio-2.0.so.0 (0x00007f0bf59c7000)
        libpangocairo-1.0.so.0 => /usr/lib64/libpangocairo-1.0.so.0 (0x00007f0bf57ba000)
        libpango-1.0.so.0 => /usr/lib64/libpango-1.0.so.0 (0x00007f0bf556e000)
        libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007f0bf531d000)
        libcairo.so.2 => /usr/lib64/libcairo.so.2 (0x00007f0bf4ffb000)
        libcroco-0.6.so.3 => /usr/lib64/libcroco-0.6.so.3 (0x00007f0bf4dbe000)
        libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f0bf4aae000)
        libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f0bf48a9000)
        libgmodule-2.0.so.0 => /usr/lib64/libgmodule-2.0.so.0 (0x00007f0bf46a5000)
        libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f0bf447e000)
        libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f0bf4267000)
        libpangoft2-1.0.so.0 => /usr/lib64/libpangoft2-1.0.so.0 (0x00007f0bf4051000)
        libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007f0bf3e12000)
        libthai.so.0 => /usr/lib64/libthai.so.0 (0x00007f0bf3c09000)
        libffi.so.4 => /usr/lib64/libffi.so.4 (0x00007f0bf3a00000)
        libpixman-1.so.0 => /usr/lib64/libpixman-1.so.0 (0x00007f0bf3758000)
        libEGL.so.1 => /usr/lib64/libEGL.so.1 (0x00007f0bf3528000)
        libxcb-shm.so.0 => /usr/lib64/libxcb-shm.so.0 (0x00007f0bf3325000)
        libxcb-render.so.0 => /usr/lib64/libxcb-render.so.0 (0x00007f0bf311a000)
        libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007f0bf2f10000)
        libpcre.so.1 => /usr/lib64/libpcre.so.1 (0x00007f0bf2ca1000)
        libharfbuzz.so.0 => /usr/lib64/libharfbuzz.so.0 (0x00007f0bf2a20000)
        libdatrie.so.1 => /usr/lib64/libdatrie.so.1 (0x00007f0bf281a000)
        libxcb-xfixes.so.0 => /usr/lib64/libxcb-xfixes.so.0 (0x00007f0bf2612000)
        libgbm.so.1 => /usr/lib64/libgbm.so.1 (0x00007f0bf2404000)
        libwayland-client.so.0 => /usr/lib64/libwayland-client.so.0 (0x00007f0bf21f6000)
        libwayland-server.so.0 => /usr/lib64/libwayland-server.so.0 (0x00007f0bf1fe3000)
        libgraphite2.so.3 => /usr/lib64/libgraphite2.so.3 (0x00007f0bf1dbb000)

And here is the message from ResolveDebug.txt

Code: Select all

==========[CRASH DUMP]==========
Please send this to support:

#TIME Sat Sep 22 08:33:42 2018 - Uptime 00:00:01 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve v15.1.0.025 (Linux/Clang)

/opt/resolve/bin/resolve() [0x40d7469]
/opt/resolve/bin/resolve() [0x40d6a6c]
/lib64/libpthread.so.0(+0x10b00) [0x7f0231d39b00]
/lib64/libc.so.6(gsignal+0x37) [0x7f022fda48d7]
/lib64/libc.so.6(abort+0x13a) [0x7f022fda5caa]
/opt/resolve/bin/resolve(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0xed) [0x59f2d6d]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x22036) [0x7f024a5f0036]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x223a1) [0x7f024a5f03a1]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x228f7) [0x7f024a5f08f7]
/opt/resolve/bin/../libs/libc++abi.so.1(__gxx_personality_v0+0x6c) [0x7f024a5f0ddc]
/lib64/libgcc_s.so.1(_Unwind_RaiseException+0x73) [0x7f0230123773]
/opt/resolve/bin/../libs/libc++abi.so.1(__cxa_throw+0x66) [0x7f024a5ef9c6]
/opt/resolve/bin/resolve() [0x14e2124]
/opt/resolve/bin/resolve() [0x14e1919]
/opt/resolve/bin/resolve() [0x14dc14a]
/opt/resolve/bin/resolve() [0x14ad0dc]
/opt/resolve/bin/resolve() [0x14aa7ee]
/opt/resolve/bin/resolve() [0x14a9435]
/opt/resolve/bin/resolve() [0x14a8d18]
/opt/resolve/bin/resolve() [0x14dd810]
/opt/resolve/bin/resolve() [0x40d6ed7]
/lib64/libpthread.so.0(+0x10b00) [0x7f0231d39b00]
/lib64/libc.so.6(gsignal+0x37) [0x7f022fda48d7]
/lib64/libc.so.6(abort+0x13a) [0x7f022fda5caa]
/opt/resolve/bin/resolve(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0xed) [0x59f2d6d]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x22036) [0x7f024a5f0036]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x223a1) [0x7f024a5f03a1]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x228f7) [0x7f024a5f08f7]
/opt/resolve/bin/../libs/libc++abi.so.1(__gxx_personality_v0+0x6c) [0x7f024a5f0ddc]
/lib64/libgcc_s.so.1(_Unwind_RaiseException+0x73) [0x7f0230123773]
/opt/resolve/bin/../libs/libc++abi.so.1(__cxa_throw+0x66) [0x7f024a5ef9c6]
/opt/resolve/bin/resolve() [0x14e2124]
/opt/resolve/bin/resolve() [0x14e1919]
/opt/resolve/bin/resolve() [0x14dc14a]
/opt/resolve/bin/resolve() [0x14ad0dc]
/opt/resolve/bin/resolve() [0x14aa7ee]
/opt/resolve/bin/resolve() [0x14a9435]
/opt/resolve/bin/resolve() [0x14a8d18]
/opt/resolve/bin/resolve() [0x14dd810]
/opt/resolve/bin/resolve() [0x40d6ed7]
/lib64/libpthread.so.0(+0x10b00) [0x7f0231d39b00]
/lib64/libc.so.6(gsignal+0x37) [0x7f022fda48d7]
/lib64/libc.so.6(abort+0x13a) [0x7f022fda5caa]
/opt/resolve/bin/resolve(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0xed) [0x59f2d6d]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x22036) [0x7f024a5f0036]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x223a1) [0x7f024a5f03a1]
/opt/resolve/bin/../libs/libc++abi.so.1(+0x228f7) [0x7f024a5f08f7]
/opt/resolve/bin/../libs/libc++abi.so.1(__gxx_personality_v0+0x6c) [0x7f024a5f0ddc]
/lib64/libgcc_s.so.1(_Unwind_RaiseException+0x73) [0x7f0230123773]
/opt/resolve/bin/../libs/libc++abi.so.1(__cxa_throw+0x66) [0x7f024a5ef9c6]
Signal Number = 6

================================

Any clues to help me ?

Any clues to help me ?

Signal Number = 6
Could be what happened to me, look into icd files you get on your setup:
/etc/OpenCL/vendors/*.icd (maybe on different location, since you're using SUSE)
And try to remove mesa-opencl-icd
Install clinfo to see what it shows to you

Any clues to help me ?

Signal Number = 6
Could be what happened to me, look into icd files you get on your setup:
/etc/OpenCL/vendors/*.icd (maybe on different location, since you're using SUSE)
And try to remove mesa-opencl-icd
Install clinfo to see what it shows to you

Um, indeed there seems to be a problem with OpenCL. I'll be diging into that.
Thanks for your answer !

Is it possible to install BMD's ISO of CentOS 7.3 in such a way to be able to boot via UEFI? So far, I've only been able to get it to work via "Secure Boot Disable and Legacy Boot Enable" on the HP Z8.

Is it possible to install BMD's ISO of CentOS 7.3 in such a way to be able to boot via UEFI? So far, I've only been able to get it to work via "Secure Boot Disable and Legacy Boot Enable" on the HP Z8.

i don't know, if it still impossible with the actual BMD ISOs, but this flaw was definitive present in older Images. an issue, which you'll not face in case of the original (hybrid) CentOS Images.

it's even a much more annoying limitation, if you have to utilize virtual machines, because the legacy boot mode will try initialize your graphics card in a manner, which isn't compatible with PCI passtrough techniques. in this case you simple have to use EFI boot.

Disabling secure boot makes sense (if they aren’t signing the NVIDIA driver themselves) but I don’t see why you would have to enable Legacy BIOS mode. What boot errors occur if you leave it disabled?

Cheers,
Mike

Disabling secure boot makes sense (if they aren’t signing the NVIDIA driver themselves) but I don’t see why you would have to enable Legacy BIOS mode. What boot errors occur if you leave it disabled?

you are simple not able to boot this ISO images on systems which only support or work satisfaying in EFI mode, because the necessary bootloader components are not available on the installation media.

Disabling secure boot makes sense (if they aren’t signing the NVIDIA driver themselves) but I don’t see why you would have to enable Legacy BIOS mode. What boot errors occur if you leave it disabled?

• Legacy Support Disable and Secure Boot Enable: can boot to Windows, but not CentOS
• Legacy Support Enable and Secure Boot Disable: can boot to both Windows and CentOS
• Legacy Support Disable and Secure Boot Disable: can boot to Windows, but not CentOS

Well that seems like a slightly less than ideal oversight... Has anyone reached out to support about this? I personally don’t use their ISO.

Cheers,
Mike

As here are the most Linux users (o;

Can some do me a favour and test this?

- Create compound clip and open it in Fusion...
- Add a background and merge it with MediaIn1 node (draw a line from background output to MediaIn1 output)

Crashes immediately for me under:

- Debian 9
- Ubuntu 18.04 LTS
- Centos 7.5


See also: viewtopic.php?f=21&t=79680

@davorin: same here (Ubuntu 16.04 LTS) with NVIDIA GTX1070, 396.44 driver

Since Resolve 15.1 the Fusion tab is totally useless, it crashes so often that its easier to tell on which operations it would not crash.... I think its time to look out for alternatives

I think its time to look out for alternatives

hmm... i even don't noticed this flaws in the compositor section, because i always preferred alternatives for this kind of tasks, just as i don't make much use of resolves audio section. in both cases there are much better alternatives available for linux user. and just because this additional capabilities are now included in resolve for free, it's no convincing argument to abandon those other much more satisfying specialized solutions. but this doesn't lessen resolves importance as the most powerful NLE-like solution on linux right now.

Resolve is nice for video editing on Linux, that's true.

The rest has to be done with other tools (I still use Fusion Studio a lot, and I love it).

Resolve still does not update the content dynamically (hey, we are in 2018 now..). When making an image sequence longer or a video gets longer, you have to delete it first in the media pool and then add it again to get the new length recognized in Resolve...

However, it was a cheap buy and we get what we payed for... for serious VFX you will never be able to use Resolve.

@davorin: same here (Ubuntu 16.04 LTS) with NVIDIA GTX1070, 396.44 driver

Since Resolve 15.1 the Fusion tab is totally useless, it crashes so often that its easier to tell on which operations it would not crash.... I think its time to look out for alternatives

Thanks for verifying...

Meanwhile I installed now macOS 10.13.6 on my ASRock H270-Pro motherboard with GTX1060 (o;

Hey, all.

I'm working on a video for our YT channel, Linus Tech Tips, where we look at editing on Linux (we've done a couple of videos recently on the topic of gaming on Linux and thought we'd do editing too).

Anyone here want to help me by answering some questions? I can't tell if Resolve is 'working' or not, judging by this thread...