Open xynydev opened 2 months ago
spaceguybob
commented
2 months ago This seems very hard to fix without actively breaking flatpak or compatibility with native programs of a custom directory method would be chosen, I'd think a simple oneshot systemD unit that does the needed steps on boot whenever the font module is used would be the most effective method of attack. If the goal is a seamless fix
xynydev
commented
2 months ago I found out that the google fonts directories have a space in their name: /usr/share/fonts/google-fonts/ Outfit, and for me, they are also empty.
spaceguybob
commented
2 months ago I found out that the google fonts directories have a space in their name:
/usr/share/fonts/google-fonts/ Outfit, and for me, they are also empty.
That's very odd, sounds almost like either a corrupt zip gets downloaded or the files get caught by the cleanup process and deleted 🤔
franute
commented
2 months ago Just wanted to add my experience. I've recently started using Blue-build and faced some issues with the fonts module and nerd fonts. But my problem was related to the name of the compressed file not being exactly what was shown in the web (for example there is Caskaydia Cove but the zip is Cascadia Code if that makes sense), but that failed the whole build, so it was a matter of reading the error and figuring out what was wrong. Other than that, the fonts module seems to be working correctly (at least with nerd fonts), they are downloaded and as soon as you boot into the new image they are available
xynydev
commented
2 months ago I found out that the google fonts directories have a space in their name:
/usr/share/fonts/google-fonts/ Outfit, and for me, they are also empty.
This issue was caused by me having an old branch of the module as the source:. Fonts are correctly downloaded with the latest version.
xynydev
commented
2 months ago Per my last comment, I figured out the source of my problems. After a reboot, the fonts were recognized and worked perfectly. I am thus still unable to reproduce this issue, and cannot effectively tackle it.
I would appreciate people who are experiencing issues to investigate on their own and report findings here.
mecattaf
commented
1 month ago In my recipe.yml I have the following config for this module:
- type: fonts
nerd-fonts:
- JetBrainsMono
- NerdFontsSymbolsOnlyJetBrainsMono is being installed on my system but not NerdFontsSymbolsOnly. When I do
fc-list | grep "my font"
I cannot find Symbols.
Has anybody managed to fix this on their system?
Multiple users have reported problems with the fonts module with the fonts not being recognized after install.
Attack plan:
systemdunit to do the fixes on boot automatically/usr/share/fonts/?Please report your experiences throughly before, also with installing fonts through methods other than the fonts module. What worked, what didn't, what fixed things, etc.