<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - fontconfig git makes gimp not see fonts." href="https://bugs.freedesktop.org/show_bug.cgi?id=102141#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - fontconfig git makes gimp not see fonts." href="https://bugs.freedesktop.org/show_bug.cgi?id=102141">bug 102141</a> from <a class="email" href="mailto:mforney@mforney.org" title="Michael Forney <mforney@mforney.org>"> Michael Forney</a> <pre>I don't quite understand your fix in dc56ff80. In 2.12.4, a failure in FcConfigFile or FcOpen both lead to bail with error == FcTrue, causing the warning message to print and FcFalse to be returned. In 2.12.5, a failure in either of those causes FcConfigParseAndLoad to just return FcTrue. My system doesn't have a fontconfig config file, and just uses the fallback configuration. However, as of 2.12.5, FcConfigParseAndLoad returns FcTrue when the config doesn't exist causing FcInitLoadOwnConfig to not load the fallback config. Reverting dc56ff80 solves the issue for me. I don't understand what issue it was meant to fix, but it does not seem to "Keep the same behavior to the return value of FcConfigParseAndLoad" as the commit message suggests.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>