Stop fontconfig from loading from host’s /etc/fonts/conf.d #13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: https://launchpad.net/bugs/2025651
At the moment the snaps in at least lunar and mantic load font configuration both from
gnome-42-2204
and from the host system’s/etc/fonts/conf.d
. This has proved to confuse fontconfig and result in unexpected issues. Stopping the snaps from loading from/etc/fonts/conf.d
seems to fix the issue.This PR reverts part of canonical/snapcraft@407dc755, which is sad IMO. But it’s a result of the reluctance to use font configuration from the host system as expressed in this comment, and for now the proposed change is the easiest way to stop fontconfig from being confused.