You are not logged in.
I'm working on switching over to an awesome/slim combination after having used gnome for quite some time. However, in various places around the desktop (both in wm applications and in non-wm applications, I get this weird, crappy gothic font that has nothing to do with the fonts I've configured. The problem was more or less corrected in gnome by using the tweak-tool, but in awesome
I've posted a screenshot of this font being displayed in chromium(look at the "print" statements, for example); it shows up in naughty notifications as well (despite having set some explicit fonts for in rc.lua and in the theme config.
From what I can tell, I get this font when some application tries to access a font I don't have installed; the output is what gets selected in its place. So I can, for example, force the font to appear by setting some application font to use a generic sans or monospace font.
So far, I've tried to set my preferred fonts in every possible place I can think of (config files for awesome, through gnome-tweak-tool (for gnome apps) and qtconfig for apps like kate, the chromium settings manager) and I've installed both ttf-google-fonts-git and ttf-win7-fonts, which should be giving me just about every font in widespread use out there. Qtconfig and tweak-tool takes care of most of what I use, but man, is that font ugly.
Beyond installing fonts via pacman/aur, system-wide font configuation is thus far a little over my head. Can anybody provide some clues as to what I still might be missing?
Offline
What do your gtk configs look like? I believe gnome-tweak-tool changes settings in gconf, which is as far as I know only loaded by gnome-session. You can edit the files yourself or use a tool like lxappearance to do it for you.
What font is set for the "print" text in the html page you show on that screenshot, and what is rendered? I'm not a chromium user but in Firefox it's possible to inspect an element to see the computed "rules".
Offline
Thanks for replying: these are both good ideas. I've never looked at the gtk settings.ini file; there wasn't much there but the only font listed was Cantarell.
The chromium is a bigger clue: the screenshot font is still the generic "monospace" font, and the other pages I tend to have trouble with are the generic sans and serif fonts. This makes sense, because forcing gnome and qt apps away from these generic entries solved the problem in a limited way. Awesome must have some references to these somewhere that override my theme and rc.lua fonts.
Is there a system wide way to force any application that wants to use "monospace" to actually use "droid sans mono" instead?
Offline
Problem is solved by uninstalling ttf-google-fonts-git. Not sure what was really causing the problem.
Offline