Hi,
Im writing as answer the fix to launch Davinci Resolve.
This is copied from the old forum, which is an important information for many users.
To find the result faster, its required to set as best answer.
The issue is, that resolve brings it’s own glib2, but not it’s own pango. It uses system-provided pango, which in turn assumes newer glib2 than resolve’s. The workaround is to move all glib2 libraries out of /opt/resolve/libs to somewhere else (/opt/resolve/libs/_disabled, for example). After that, resolve will pick system-provided glib2 and pango will be happy with that. The downside is, that Resolve wasn’t QA-ed with this glib2 version, so it may bug out somewhere else. On the other hand, at least it will start. Only need to move those files that belong to glib2: libgio, libglib, libgmodule*, libgobject*.**
Steps
Access to the location
cd /opt/resolve/libs
Create the folder _disabled in /opt/resolve/libs/ to move the glib2 libraries there:
sudo mkdir /opt/resolve/libs/_disabled
And then, move the glib2 inside the _disabled folder:
sudo mv libgio* libglib* libgmodule* libgobject* _disabled
Then launch Resolve as usual. It works. 
1 Like
You could too just preload the libraries like this:
LD_PRELOAD="/usr/lib64/libglib-2.0.so.0 /usr/lib64/libgio-2.0.so.0 /usr/lib64/libgmodule-2.0.so.0" /opt/resolve/bin/resolve
Or to copy the desktop file to your home…
cp /usr/share/applications/DaVinciResolve.desktop $HOME/.local/share/applications/
…then to edit and change de exec param:
nano $HOME/.local/share/applications/DaVinciResolve.desktop
[...]
Exec=env LD_PRELOAD="/usr/lib64/libglib-2.0.so.0 /usr/lib64/libgio-2.0.so.0 /usr/lib64/libgmodule-2.0.so.0" /opt/resolve/bin/resolve %u
[...]
2 Likes