Hello there, hopefully you had a nice day, and to care of whoever reading this,
Here's my issue.
After installing Solus back again on the 4.4 release, I was surprised to see the rocm package being available in the stable Solus repos, meaning I could potentially achieve one of the important only reasons I could use Solus as my preferred OS of choice. GPU Acceleration for Davinci Resolve Studio mainly. Absolutely obligatory for me for professional work on my main AMD unit.
However, after installing Davinci Resolve Studio as usual, it didn't manage to start due to an issue with libpango, apparently.
/opt/resolve/bin/resolve: symbol lookup error: /usr/lib/libpango-1.0.so.0: undefined symbol: g_string_free_and_steal
I've did try to install the 32 bits version of that dependency, as well as devel and compat version of it, without any changes.

So, I'm foremost asking for help to resolve this particular issue, but subsequently, asking about the status of Davinci Resolve support on Solus, does it work? Does the rocm package work as expected nowadays?

If the rocm package still has issues, I remember that the free mesa OpenCL implementation, managed to be stable enough to work fine with Davinci Resolve exigent GPU driver exigence, so perhaps this could also be used by myself, if it is package, or can be packaged on Solus.

  • In my case davinci resolve 17 luckily has never stopped working (but if it stops working it would be very serious: it's not an app I can give up) in fact at the moment I haven't been able to get it to go on distrobox, although I did not spend much time on it.

PoorPocketsMcNewHold
Both these symbols are in pango package and they are added when we updated pango to 1.50.14.

abi_used_symbols
399:libglib-2.0.so.0:g_string_free_and_steal

abi_used_symbols32
314:libglib-2.0.so.0:g_string_free_and_steal

Maybe you need to compile "Davinci Resolve Studio" again.

            PoorPocketsMcNewHold Sure, but if it's using system libs then ultimately it's the responsibility of the vendor to ensure that it works across multiple versions of those libs. So either there's a library you're missing somewhere, or the program is not compatible with our versions of those libraries (or how we compile them).

              In my case davinci resolve 17 luckily has never stopped working (but if it stops working it would be very serious: it's not an app I can give up) in fact at the moment I haven't been able to get it to go on distrobox, although I did not spend much time on it.

                FAb7D I never thought of testing it on Distrobox. I already played with it in the past. I'll reinstall Davinci Resolve to check if something is wrong, and consider trying it.


                  Yep. It works well. Haven't felt the need to go install a setup the AMDGPU proprietary OpenCL driver on Distrobox.
                  Just used mesa-libOpenCL (distrobox enter resolve -- sudo dnf install mesa-libOpenCL) on a Fedora 37 distrobox base.
                  I've used that small script (Well, more just a suite of commands) to setup it on Solus. I could potentially make a dedicated full tutorial on the forums for that, or even try to push request an entry to the Solus docs (Even if I doubt distrobox is something they entirely support/recommend using)