[Bug 921706] ghostscript: /invalidfont in /findfont, --nostringval-- Helvetica

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=921706



--- Comment #44 from Jerry James <loganjerry at gmail.com> ---
After several more mock builds, I can tell you that adding any one of the
following (not all of them at once!) to %prep sometimes results in a good build
and sometimes doesn't.  In other words, none of these has any effect.  We still
sometimes have /usr/share/fonts/default/Type1 in the cache, and sometimes
don't.  

- fc-cache /usr/share/fonts/default/Type1
- fc-cache /usr/share/fonts/default
- fc-cache -f /usr/share/fonts/default/Type1
- fc-cache -fr /usr/share/fonts/default/Type1
- fc-cache -f /usr/share/fonts/default
- fc-cache -fr /usr/share/fonts/default
- fc-cache -fr
- fc-cache

Since fc-cache is being run by a nonprivileged user, the new cache data is
being written to /builddir/.cache/fontconfig.  And, after most of the commands
above, that contains the correct directory:

strings
/var/lib/mock/fedora-rawhide-x86_64/root/builddir/.cache/fontconfig/0251a5afa6ac727a1e32b7d4d4aa7cf0-le64.cache-4
47zS
/usr/share/fonts/default
/usr/share/fonts/default/Type1
/usr/share/fonts/default/ghostscript

But then ghostscript fails anyway, as though it can't see
/usr/share/fonts/default/Type1.  So fc-cache sometimes fails to add
/usr/share/fonts/default/Type1 to the system cache after urw-fonts has been
installed, and the fontconfig system sometimes ignores the presence of
/usr/share/fonts/default/Type1 in user caches when it isn't present in the
system cache.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=RKYkqpeqBq&a=cc_unsubscribe