I set "DejaVu Sans" as the default sans serif font in /etc/fonts, because it provides more characters than Vera. After upgrading to dejavu-2.21, all applications that use the "Sans Serif" font suddenly display some other font (could be dingbats, not sure). I am using KDE 3.5.7. Reproducible: Always Steps to Reproduce: 1. move dejavu fonts to the top of the list in /etc/fonts/conf.avail/40-generic.conf and 60-latin.conf 2. emerge =media-fonts/dejavu-2.21 3. launch applications that uses the Sans Serif font Actual Results: Applications use Dingbats Expected Results: Applications use DejaVu This happens only with dejavu-2.21, both dejavu-2.20 and 2.22 work fine. Applications that directly use DejaVu also work as expected.
Please, attach the output of `fc-match -s 'Sans Serif'` Also what do mean by "Applications that directly use DejaVu also work as expected."? What applications? Have you tried to clean local font cache ~/.fontconfig/*? Have you tried to restart firefox?
> Also what do mean by "Applications that directly use DejaVu also work as > expected."? What applications? Have you tried to clean local font cache > ~/.fontconfig/*? Have you tried to restart firefox? If I tell an application to use "Sans Serif" as font, it will use "DejaVu Sans" if =media-fonts/dejavu-2.20 is installed. With =media-fonts/dejavu-2.21 however, it will use another font (looks like Dingbats), even though DejaVu Sans is on top of the list in /etc/fonts. If I tell it to use "DejaVu Sans" as font, it will always use DejaVu Sans. I already tried logging out, rebooting, unmerging and re-emerging dejavu, and a new user account. I did some testing, and it seems that mostly kde apps are affected.
Created attachment 139008 [details] fc-match-sans-serif-dejavu-2.20 output of fc -match 'Sans Serif' when dejavu-2.20 is installed
Created attachment 139010 [details] fc-match-sans-serif-dejavu-2.21f output of fc -match 'Sans Serif' when dejavu-2.21 is installed
Fontconfig output shows that the best match in both cases is Dejavu Sans... Well, but I assumed that you were using firefox. But could you tell me what applications you are talking about? Could you provide screenshot with working and broken fonts? I do not see the problem still.
Created attachment 139027 [details] kcontrol-dejavu-2.20.png This is what the KDE Control Center looks like when dejavu-2.20 is installed
Created attachment 139029 [details] kcontrol-dejavu-2.21.png This is what the KDE Control Center looks like when dejavu-2.21 is installed. Note that kwin was started with dejavu-2.20 still installed, so it has the normal font still. If I restart it with kwin --replace, the title bar will change as well. I previously thought it looked like dingbats. But after seeing an actual dingbats font I now think it must be something else. Apologies if this was misleading.
This looks like some local configuration problem. Font selection dialog shows correct glyphs while you see that strange fonts in other places. Could you try to create another user with clean home directory, start kde with the new user and try to set fonts there?
(In reply to comment #8) > This looks like some local configuration problem. Font selection dialog shows > correct glyphs while you see that strange fonts in other places. No, the font selection dialog will show the incorrect font when selecting "Sans Serif", only "DejaVu Sans" is correctly shown. The problem seems to be related to the condensed font issue in bug 202255. Anyways, I am using dejavu-2.22.20071220.2156 now without any problems. I guess this bug can be closed now (or when that version goes stable).
Similar to bug 202255 comment 2, removing /usr/share/fonts/dejavu/DejaVuCondensedSans* fixes the issue as well. So the font that was displayed for "Sans Serif" was actually DejaVu Condensed Sans after all.
The bug 202255 is completely different from the issue you've reported here and it does not happen in dejavu-2.21. And the output of fc-match shows that fontconfig returns correct font names/files in both cases, strange that font selection dialog displays different font... But well, although 2.21 are stable now, I did not have other reports about problems with them so dejavu-2.22.20071220.2156 will go stable as the time comes. Marking this bug as FIXED as it is fixed in the tree in dejavu-2.22.20071220.2156.
