Moving included libs out of the way didn’t work. Still get the same segfault with essentially the same error message. I’ll try a snapshot and see what happens.
EDIT: Nope. The Unofficial tarball crashes in exactly the same way.
Then it’s probably the AMD driver. I see that it includes it’s own GL library and other stuff.
I don’t have access to any cards that uses amdgpu-pro (I think, what’s the oldest cards I can use?) so I can’t test this directly (or find a workaround).
I’ll move the plugin folder aside and try that. But I honestly think it’s the AMD Pro drivers. They don’t play well with games either. But it does run OpenCL 2.0, which makes it perfect for Blender and Resolve.
First of all, start by fixing your fontconfig location:
export FONTCONFIG_PATH=/etc/fonts
If that does not help, try flatpak version to see if works, some other people also experienced this and reported that flatpak version was working fine:
Yeah, sandboxing won’t fix the GL conflict with the AMD driver.
At the moment your only solution would be to build Natron yourself (against the dev packages provided by AMD). I will however look into this when I get a amdgpu-pro compatible card (the closest I could find was an 290x, but the card is broken or something, no video output) and see if some workarounds can be made.
I’m willing to try that. It’s been a while, but I’ve built stuff from source before. Ubuntu Desktop doesn’t ship with a real dev environment. So I’ll have to sort that out. But if it will help the Natron community get an answer here, and me too, this might be worth it. Pretty much anyone with a recent AMD card running Linux or Resolve has the Pro drivers installed. I can’t be the only one who’s seen this.
OK. So it turned out that Davinci Resolve had a serious Fusion bug with the AMDGPU-Pro drivers too. I installed ROCm with the standard driver and (though it’s a little slower) the Fusion bug was resolved. As a side benefit, the flatpak Natron also works. So, I’m not sure if anyone really cares about AMDGPU-Pro.
Great that you got Natron working. The biggest problem with the AMDGPU stack is the forced use of libraries that will/might conflict with “universal” binaries from other applications. At least they (AMD) provided headers so you can compile against them if you have issues, but it won’t fix existing binaries from Resolve, Natron etc.
This problem might be resolved in the future when Natron is built against a newer version of CentOS/RHEL that provides a newer OpenGL(Mesa) stack.
OpenGL is not the issue. The OpenGL API hasn’t changed for 20 years. It is probably that their version of the OpenGL library depends on something that conflicts with Natron.