Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[fontconfig] gimp could not find any fonts #6661

Closed
kerwinxu opened this issue Jul 8, 2020 · 6 comments
Closed

[fontconfig] gimp could not find any fonts #6661

kerwinxu opened this issue Jul 8, 2020 · 6 comments

Comments

@kerwinxu
Copy link

kerwinxu commented Jul 8, 2020

mingw-w64-x86_64-fontconfig-2.13.92-1 has problem . gimp could not find any fonts .

@lazka lazka changed the title mingw-w64-x86_64-fontconfig-2.13.92-1 [fontconfig] gimp could not find any fonts Aug 5, 2020
@Jehan
Copy link

Jehan commented Aug 16, 2020

Hi!

This was fixed upstream at Fontconfig which had a regression on FcConfigParseAndLoad*():
https://gitlab.freedesktop.org/fontconfig/fontconfig/-/commit/fcada522913e5e07efa6367eff87ace9f06d24c8

So either Msys2 should downgrade (also apparently the stable release is 2.13.1; why does Msys2 release an unstable version?), or should cherry-pick this fix.
Thanks for all the hard work! 🙂

@Biswa96
Copy link
Member

Biswa96 commented Aug 16, 2020

why does Msys2 release an unstable version?

Msys2 is inherited from ArchLinux, so being unstable is in it's gene 😎 Also fontconfig has 2.13.92 tag.

There are two options:

  1. Import the patch file here and rebuild the package. It builds without any compiler error (at least).
  2. Use the fontconfig git repository with a specific commit. But need someone familiar with the project.

Which one is better option here?

@Jehan
Copy link

Jehan commented Aug 16, 2020

Msys2 is inherited from ArchLinux, so being unstable is in it's gene sunglasses Also fontconfig has 2.13.92 tag.

Ok.

Which one is better option here?

Personally I would just go the patch way, because just adding more experimental commits in may bring you more work-in-progress bugs. I mean, unless you get lucky or you've got time on your hand, this is most likely not recommended.

But in the end, the choice is yours, not mine. 🙂

@lazka
Copy link
Member

lazka commented Aug 16, 2020

@Jehan thanks for the hint re the regression/patch!

Not sure why fontconfig was updated... my guess would be because Arch did first.

lazka added a commit to lazka/MINGW-packages that referenced this issue Aug 16, 2020
@lazka
Copy link
Member

lazka commented Aug 25, 2020

new package including the fix is out

@lazka lazka closed this as completed Aug 25, 2020
@lazka
Copy link
Member

lazka commented Nov 4, 2020

Inkscape noted in #7230 that things are still broken. Does anyone know more?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants