https://bugzilla.redhat.com/show_bug.cgi?id=1169979
Rob Foehl <rwf(a)loonybin.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rwf(a)loonybin.net
--- Comment #8 from Rob Foehl <rwf(a)loonybin.net> ---
(In reply to Adam Williamson (Red Hat) from comment #4)
I just tested a Workstation network install, as it seems plausible
that
regular installs could suffer from this too. It was fine. I suspect perhaps
the time taken to download packages helps, if we're figuring this is some
kinda timing issue with fc-cache. live image creation retrieves all the
packages first; network installation downloads packages one at a time during
the install process. So, perhaps a network install over a local network
might hit it.
I just ran into this issue with one of two desktops that were built up from
minimal network installs and an "add just the stuff I need" script: after
installing the @fonts group (among other things), one had Nimbus Mono L as the
only available monospace font, before manually running fc-cache -f. The other
system was fine, which seems to confirm your suspicion above.
Is there a fontconfig bug open anywhere for this? I've been using this same
basic process for (re)installs since FC3, and was blissfully unaware of the
fontconfig cache until now...
-Rob
--
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=6xvBfI8YUZ&a=cc_unsubscribe