-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default fonts are being overridden upon installation #29
Comments
This may well be related to #13, but as the bug log shows, it is not the fonts themselves that hijack the preferred places for the "monospace" etc. aliases. It is a fontconfig issue, and the way fontconfig is configured is all up to your distribution. If you are on Arch, could you please post the output of the While packaging the fonts for Debian, I found that sorting the fontconfig rules with a priority higher than 61, i.e. with a smaller numerical prefix, lead to similar issues that you describe. Also, I found the urw-urw-fallback-specifics.conf rule to be offensive and removed it from the package. |
This doc is relevant: |
Thanks for the quick reply. I reinstalled the dependency chain which installs gsfonts.
|
Hm, doesn't look too wrong to me. |
My system: Arch Linux 5.8.3-arch-1-1
Package manager: yay (pacman)
I think through a chain of dependencies, this was installed on my system.
(I installed font-manager, which installed vala, which installed graphviz, which installed gsfonts, which lists this repo as the upstream URL)
When I installed font-manager, my default system fonts (such as the monospace font used in my terminal and dmenu) were overridden from Noto to Nimbus. I checked that using
fc-match monospace
fc-match sans-serif
fc-match serif
which all returned a Nimbus variant.
I found out that gsfonts was the package that installed Nimbus on my system.
(After I uninstalled gsfonts, my fonts thankfully went back to normal; checking with
fc-match
returns Noto variants again.)Is this expected behavior? If it is, I find it quite intrusive. It took me a while to track down the problem on my system.
Could this be related to #13 ?
The text was updated successfully, but these errors were encountered: