Skip Navigation
Linux @lemmy.ml governorkeagan @lemdro.id

[SOLVED] Davinci Resolve Plugin Issue on Nobara

I'm currently daily driving Pop!_OS and absolutely love it! I've even riced it a little. In the almost 2 months that I have been using Linux as my main OS I have seen a lot of talk about Nobara. I've got a spare SSD in my system so I did a quick install on there to see if it would be worth moving. My main priority is ensuring that DaVinci Resolve (and any plugins I use) work, the rest is less important.

I've gotten Resolve to work fine, but one of my plugins keeps giving me an error when I try activating the license.

/usr/OFX/Plugins/DehancerProCuda_x86_64_v7.ofx.bundle/Contents/apps/ProfileActivator: symbol lookup error: /lib64/libharfbuzz.so.0: undefined symbol: FT_Get_Color_Glyph_Layer

0x7f4eeec0f480 | OpenFX               | ERROR | 2023-12-16 12:40:21,756 | Process /usr/OFX/Plugins/DehancerProCuda_x86_64_v7.ofx.bundle/Contents/apps/ProfileActivator  "-c" "com.dehancer.film_pro.v7" "--licensename" "Dehancer Film OFX" "-t" "Dehancer Pro" "-h" "davinci_resolve" (pid=21715) failed

Urgent message: Open FX Error||Dehancer Pro 7.1.0-beta.11.build311 could not be run successfully. See DaVinci Resolve logs for details.

I don't have this issue on Pop!_OS and from my research it seems like the issue is related to a mismatched dependency (maybe?). I'd love to get another set of eyes on this to see if I can get the issue fixed.

EDIT: Forgot to mention, I’ve reached out to the developers of the plugin (Dehancer) to see if this is a known issue/bug.

SOLVED:

TL;DR - It was a FreeType issue and removing the FreeType library file from the plugin folder fixed the issue.

While reading through the logs to try and understand the issue, I came across this on the harfbuzz issue tracker. I had initially thought that this was a harfbuzz issue but after reading the comments a few times it seemed like it was actually an issue with FreeType and harfbuzz wasn't able to access it for some reason. After some more reading around and pondering, I decided to browse the plugin's folder, since the plugin was the thing causing me issues. Within the plugin folder structure, there is a section for libraries that it ships with. I couldn't find the libharfbuzz file like in /lib64 but there was libfreetype.so.6. I deleted that, thinking that if it is required it will either use the one provided by the system or give me a different error. After deleting it the plugin worked as expected and I was able to activate it without issue!

I had a look for this file in my Pop!_OS install and found it there. I'm not sure why on Nobara it caused an issue and needed to be deleted but not on Pop!_OS

4
4 comments

  • Since there are no replies yet I will take a stab that I hope will help get you closer and not send you off on a wild goose chase because of me being an idiot or something.

    You may also know all of the following, if so sorry.

    I run into Undefined symbol errors usually when some software is trying to call a function it expects to be in a library but the function isn't because I have the wrong version of the library.

    So yeah I think it may be a dependency issue.

    The next thing is to figure out which package holds libharfbuzz so you can determine what version of that package you have vs what version is required by Davinci Resolve.

    Something I learned about Nobara is that updating software has to either be done in the Nobara package manager or with a specific set of commands on the command line or you might break stuff (like I just did). It seems plausible that if you updated with a simple dnf update on the command line it may have caused issues.

    Also... Are you installing Resolve from a Flatpak or ...?