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
Thank you!
I ran an update after installing Nobara from the welcome page thing. I also ran a
dnf updatelater.I’ll have a deeper dive tomorrow and try figure out what package has
libharfbuzz. Any tips on how to do this effectively?Resolve is an interesting case since they only officially support 3 distros. They have a
.runfile which installs the application. resolve on linuxVia Google search for libharfbuzz, It’s a “text shaping engine” – https://github.com/harfbuzz/harfbuzz
I then searched Fedora distro harfbuzz and got this – https://src.fedoraproject.org/rpms/harfbuzz
I would then go look for it in Nobara package manager and see if it needs updating or not and see what version it is running.
Another thing I would check is what version is standard in the supported distros. I’m guessing that list includes Fedora and Ubuntu and/or Debian. If the version they expect is different from what you have then we need a way to make the right version available. I’m not sure what is the best answer but I have a few ideas that I would try if it were me.
Man I tell you, apps that have one off install approaches like this are so annoying. I’ve run into this a few times. It just leaves me feeling dirty. Why can’t they just distribute an AppImage or rpm for Pete’s sake?
I just checked on Pop!_OS to see what version I’m running there because I know everything works fine.
harfbuzzisn’t even installed…When I’m finished work later today I’ll have a look on Nobara for the version installed cs expected etc.
EDIT: I solved the issue.I came across a similar issue on the GitHub repo for harfbuzz and while reading the log file again I had an ah-ha moment. More details in the post.