Fontconfig finds a font during scanning, but does not enter it into the cache
On a CentOS 7 installation I have a number of font files in /usr/share/fonts. Some of them have been correctly recognised by fontconfig and show up in fc-list, but others quite simply refuse to be added to the cache.
I set the flags CACHEV and SCANV (seperately) for FC_DEBUG and ran fc-cache -fv. Fonts that work correctly show up in the output when either of those flags are set, but fonts which aren't working show up only with SCANV. However, I can't make out a difference between the SCANV output for working vs broken fonts which might explain the issue.
The fonts in question have also already been correctly installed on another CentOS installation (which is not quite identical to this one but similar enough) and work just fine there. I ran cmp and diff over the "broken" files in /usr/share/fonts and a copy of the working ones from the other system and they claim to be identical.
Permissions are consistently set to -rw-r--r-- and files are owned by the current user.
What could be the cause of this behaviour? How can I go about debugging this further?
centos fontconfig
edited Dec 17 at 10:23
Rui F Ribeiro
38.9k1479129
asked Dec 17 at 10:07
Jan Hettenkofer
61
add a comment |
On a CentOS 7 installation I have a number of font files in /usr/share/fonts. Some of them have been correctly recognised by fontconfig and show up in fc-list, but others quite simply refuse to be added to the cache.
I set the flags CACHEV and SCANV (seperately) for FC_DEBUG and ran fc-cache -fv. Fonts that work correctly show up in the output when either of those flags are set, but fonts which aren't working show up only with SCANV. However, I can't make out a difference between the SCANV output for working vs broken fonts which might explain the issue.
The fonts in question have also already been correctly installed on another CentOS installation (which is not quite identical to this one but similar enough) and work just fine there. I ran cmp and diff over the "broken" files in /usr/share/fonts and a copy of the working ones from the other system and they claim to be identical.
Permissions are consistently set to -rw-r--r-- and files are owned by the current user.
What could be the cause of this behaviour? How can I go about debugging this further?
centos fontconfig
edited Dec 17 at 10:23
Rui F Ribeiro
38.9k1479129
asked Dec 17 at 10:07
Jan Hettenkofer
61
add a comment |
On a CentOS 7 installation I have a number of font files in /usr/share/fonts. Some of them have been correctly recognised by fontconfig and show up in fc-list, but others quite simply refuse to be added to the cache.
I set the flags CACHEV and SCANV (seperately) for FC_DEBUG and ran fc-cache -fv. Fonts that work correctly show up in the output when either of those flags are set, but fonts which aren't working show up only with SCANV. However, I can't make out a difference between the SCANV output for working vs broken fonts which might explain the issue.
The fonts in question have also already been correctly installed on another CentOS installation (which is not quite identical to this one but similar enough) and work just fine there. I ran cmp and diff over the "broken" files in /usr/share/fonts and a copy of the working ones from the other system and they claim to be identical.
Permissions are consistently set to -rw-r--r-- and files are owned by the current user.
What could be the cause of this behaviour? How can I go about debugging this further?
centos fontconfig
edited Dec 17 at 10:23
Rui F Ribeiro
38.9k1479129
asked Dec 17 at 10:07
Jan Hettenkofer
61
On a CentOS 7 installation I have a number of font files in /usr/share/fonts. Some of them have been correctly recognised by fontconfig and show up in fc-list, but others quite simply refuse to be added to the cache.
I set the flags CACHEV and SCANV (seperately) for FC_DEBUG and ran fc-cache -fv. Fonts that work correctly show up in the output when either of those flags are set, but fonts which aren't working show up only with SCANV. However, I can't make out a difference between the SCANV output for working vs broken fonts which might explain the issue.
The fonts in question have also already been correctly installed on another CentOS installation (which is not quite identical to this one but similar enough) and work just fine there. I ran cmp and diff over the "broken" files in /usr/share/fonts and a copy of the working ones from the other system and they claim to be identical.
Permissions are consistently set to -rw-r--r-- and files are owned by the current user.
What could be the cause of this behaviour? How can I go about debugging this further?
centos fontconfig
centos fontconfig
edited Dec 17 at 10:23
Rui F Ribeiro
38.9k1479129
asked Dec 17 at 10:07
Jan Hettenkofer
61
edited Dec 17 at 10:23
Rui F Ribeiro
38.9k1479129
asked Dec 17 at 10:07
Jan Hettenkofer
61
edited Dec 17 at 10:23
Rui F Ribeiro
38.9k1479129
edited Dec 17 at 10:23
Rui F Ribeiro
38.9k1479129
edited Dec 17 at 10:23
Rui F Ribeiro
38.9k1479129
38.9k1479129
asked Dec 17 at 10:07
Jan Hettenkofer
61
asked Dec 17 at 10:07
Jan Hettenkofer
61
asked Dec 17 at 10:07
Jan Hettenkofer
61
61
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I could get the fonts in question to show up in fc-list by running fc-cache -rv. Apparently the switch -f doesn't force regeneration from scratch whereas -r deletes existing caches and starts over.
The critical hint was found here: Why is font not listed by fc-list after running fc-cache on font
answered Dec 17 at 10:35
Jan Hettenkofer
61
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489436%2ffontconfig-finds-a-font-during-scanning-but-does-not-enter-it-into-the-cache%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I could get the fonts in question to show up in fc-list by running fc-cache -rv. Apparently the switch -f doesn't force regeneration from scratch whereas -r deletes existing caches and starts over.
The critical hint was found here: Why is font not listed by fc-list after running fc-cache on font
answered Dec 17 at 10:35
Jan Hettenkofer
61
add a comment |
I could get the fonts in question to show up in fc-list by running fc-cache -rv. Apparently the switch -f doesn't force regeneration from scratch whereas -r deletes existing caches and starts over.
The critical hint was found here: Why is font not listed by fc-list after running fc-cache on font
answered Dec 17 at 10:35
Jan Hettenkofer
61
add a comment |
I could get the fonts in question to show up in fc-list by running fc-cache -rv. Apparently the switch -f doesn't force regeneration from scratch whereas -r deletes existing caches and starts over.
The critical hint was found here: Why is font not listed by fc-list after running fc-cache on font
answered Dec 17 at 10:35
Jan Hettenkofer
61
I could get the fonts in question to show up in fc-list by running fc-cache -rv. Apparently the switch -f doesn't force regeneration from scratch whereas -r deletes existing caches and starts over.
The critical hint was found here: Why is font not listed by fc-list after running fc-cache on font
answered Dec 17 at 10:35
Jan Hettenkofer
61
answered Dec 17 at 10:35
Jan Hettenkofer
61
answered Dec 17 at 10:35
Jan Hettenkofer
61
answered Dec 17 at 10:35
Jan Hettenkofer
61
61
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489436%2ffontconfig-finds-a-font-during-scanning-but-does-not-enter-it-into-the-cache%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
