Author Topic: [SOLVED]Substance Designer 2019.1.0 does not work with CentOS 7.4  (Read 3249 times)

I've been trying to run the new Substance Designer 2019.1.0 on linux this morning and keep hitting a pesky problem:

symbol lookup error: /softwareLocal/substancedesigner/linux/2019.1.0/plugins/platforms/../../ undefined symbol: FT_Get_Font_Format

I was finally able to get it to work when switching to a workstation using CentOS 7.6 instead of the 7.4 I'm currently using.
Unfortunately my artists are all on CentOS 7.4 and we're not ready just yet to update them.

I believe it's due to the update of QT in the latest version of substance designer but I was wondering if it was something some of you folks may have encountered? Is this a known issue? An intended change?

Here's the ldd on the library that returns an error:
-$ ldd /softwareLocal/substancedesigner/linux/2019.1.0/plugins/platforms/../../ =>  (0x00007ffcd3957000) => /usr/lib64/nvidia/ (0x00007ff2ac3ef000) => /lib64/ (0x00007ff2ac1b1000) => /lib64/ (0x00007ff2abf0b000) => /lib64/ (0x00007ff2abcf5000) => /softwareLocal/substancedesigner/linux/2019.1.0/plugins/platforms/../.././ (0x00007ff2ab65c000) => /softwareLocal/substancedesigner/linux/2019.1.0/plugins/platforms/../.././ (0x00007ff2ab041000) => /lib64/ (0x00007ff2aae25000) => /lib64/ (0x00007ff2aac22000) => /lib64/ (0x00007ff2aa9fa000) => /lib64/ (0x00007ff2aa7ef000) => /lib64/ (0x00007ff2aa5dc000) => /lib64/ (0x00007ff2aa29e000) => /lib64/ (0x00007ff2a9f9c000) => /lib64/ (0x00007ff2a9d93000) => /lib64/ (0x00007ff2a9b53000) => /lib64/ (0x00007ff2a994f000) => /lib64/ (0x00007ff2a9646000) => /lib64/ (0x00007ff2a9430000) => /lib64/ (0x00007ff2a906d000) => /usr/lib64/nvidia/ (0x00007ff2a8e3c000) => /usr/lib64/nvidia/ (0x00007ff2a8b6e000) => /lib64/ (0x00007ff2a8944000)
   /lib64/ (0x00005612255b6000) => /lib64/ (0x00007ff2a873f000) => /usr/lib64/ (0x00007ff2a8523000)
Last Edit: June 06, 2019, 12:16:04 pm

Hey sorry about this: were you able to send a bug report?

I havent yet, was hoping maybe I'd get some tips but I will now! thanks!

no problem (we'll be able to get more info about what's going on ;-))

Hey there,

We are aware of the issue, it comes from the fact that our CentOS builders are up to date and that there is apparently no backward compatibility between point releases of CentOS. We are actively working on finding a solution to the problem!

Thanks for the quick reply, will be patiently waiting news from you folks!

Until we devise an appropriate solution, you can try the following workarounds:
 - update the freetype package. It should not trigger any other updates and the compatibility issue should be fixed afterwards
 - if you don't want to update any package, you can put the .so of the updated freetype library (v2.8) next to the Substance Designer executable. You can get it from the latest rpm here:

Not sure if this is related, but Designer 2019.1.1 fails to install with:

sudo rpm -Uvh Substance_Designer-2019.1.1-2320-linux-x64-standard-full.rpm
error: Failed dependencies:
        libxkbcommon >= 0.5 is needed by Substance_Designer-2019.1.1-1.el7.standard.full.x86_64
        libxkbcommon-x11 >= 0.5 is needed by Substance_Designer-2019.1.1-1.el7.standard.full.x86_64

2019.1.0 installs and works fine.

OpenSuse 15.0 (yes, I know, not Centos)

I notice that 2019.1.0 only links against


Peter B


First, try to install libxkbcommon and libxkbcommon-x11.
Then try install Designer.

If it doesn't work and since you were able to launch Designer 2019.1.0, try to install Designer 2019.1.1 using --nodeps.

Thanks !
QA Analyst

Hi Celine,

Thanks for the quick reply. It was late and I did not add nearly enough info to my post, apologies for that.

I do have libkxbcommon and -x11 installed.
I installed with --nodeps, and it installed. However when launching Designer immediately segfaults.

I was not able to check the version(s) installed of libkxbcommon however which might be a distro issue. Worst case I can try to extract those libs from Centos 7.6 and hack them into the Designer libs, but I worry about other dependencies then starting to creep in.


Peter B

Hi pbowmar,

One thing that changed between 2019.1.0 and 2019.1.1 is that we now bundle the freetype library alongside Substance Designer (see,29285.0.html). Maybe this is the cause of your issue, could you try removing it so that the freetype of your system gets used instead of the one we ship?


Luc Touraille

Nice one Luc, that makes it work nicely!

Merci beaucoup!


Peter B