DaVinci Resolve 15 on Ubuntu 18.04 buster/sid

I had beta 150b2 working on my debian system before I accepted the upgrade to ubuntu LTS 18.04.

After that, I am unable to start the resolve process. I'm getting what appear to be linking errors.

The attached log indicates that the issue is with starting the 'xcb' platform plugin, however, the launch output indicates that it is (more specifically) a linking problem, most likely with a wrong version of libCg and libCgGL, due to those files not containing versioned symbols. (And of course, Davinci being compiled against a different version of those libraries, possibly.)

I would really like to use DaVinci Resolve as my main studio tool. If we can get a build that will work on 18.04 LTS, I'll gladly buy the full version.

Here is the console output:

Code: Select all

./resolve
./resolve: /opt/resolve/bin/../libs/libCg.so: no version information available (required by ./resolve)
./resolve: /opt/resolve/bin/../libs/libCgGL.so: no version information available (required by ./resolve)
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.0b (#037) Linux/Clang
Main thread starts: E2F53A40
[0x7f38e2f53a40] | Undefined            | INFO  | 2018-05-10 12:42:43,846 | --------------------------------------------------------------------------------
[0x7f38e2f53a40] | Undefined            | INFO  | 2018-05-10 12:42:43,846 | Loaded log config from /opt/resolve/configs/log-conf.xml
[0x7f38e2f53a40] | Undefined            | INFO  | 2018-05-10 12:42:43,846 | --------------------------------------------------------------------------------
Aborted (core dumped)



Here is the ResolveDebug.log output: (attachments were rejected:)

Code: Select all

This application failed to start because it could not find or load the Qt platform plugin "xcb".

Available platform plugins are: linuxfb, minimal, offscreen, xcb.

Reinstalling the application may fix this problem.
[0x7f38e2f53a40] | Main                 | INFO  | 2018-05-10 12:42:43,848 | Caught termination signal SIGABRT, triggering termination routine
[0x7f38e2f53a40] | Main                 | ERROR | 2018-05-10 12:42:43,848 | Termination request failed


Hey Jonathan. I'm a heavy Debian user although I run resolve in a windows environment. That being said, might you be able to walk those libraries back somehow to the older versions? I've done that for other purposes in Debian and had success. I'm not sure how easier it would he due to dependencies.

THE libCG and libCgGL errors can be, in my experience, safely ignored. I may suggest either reinstalling Qt as a whole, the package containing xcb, or try reinstalling Resolve. Rolling back packages, a common practice on Windows, does not usually bode well on a Linux platform particularly after a major distro upgrade. If this was a minor update on his previous version, then that might be more seamless, but major upgrades will throw a fit if you do that, particularly if the distro itself is linked against it.

Cheers,
Mike

Agreed. I have done it (although not for those packages). It is difficult. I don't have experience with Resolve in a linix environment just extensive experience with Debian itself. I once rolled back from unstable to stable, although even that might be easier than just one package.

Code: Select all

This application failed to start because it could not find or load the Qt platform plugin "xcb".

Available platform plugins are: linuxfb, minimal, offscreen, xcb.

Reinstalling the application may fix this problem.
[0x7f38e2f53a40] | Main                 | INFO  | 2018-05-10 12:42:43,848 | Caught termination signal SIGABRT, triggering termination routine
[0x7f38e2f53a40] | Main                 | ERROR | 2018-05-10 12:42:43,848 | Termination request failed


i would guess, that your resolve binary doesn't use it's own Qt libraries in /opt/resolve/lib.
this may happen, if you change the location of the installation or one of the LD_* environment variables is set, etc.
resolve comes with quite old Qt libraries (5.4.1 -- from CentOS6 days), which are ABI incompatible to the QT system libraries of most recent linux distributions. it's therefore quite important, that resolve find it's own libraries...

btw. this outdated Qt versions make it also a little bit arduous, to use gammaray to modify the GUI yourself in a similar manner as discussed in another thread, because the used gammaray-probe also has to be ABI compliant...