Bug 286260 - Incorrect fonts displayed in the font kcm
Summary: Incorrect fonts displayed in the font kcm
Status: RESOLVED FIXED
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kdeui (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-10 12:05 UTC by Christophe Marin
Modified: 2017-01-17 18:30 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
font kcm (49.17 KB, image/png)
2011-11-10 12:05 UTC, Christophe Marin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christophe Marin 2011-11-10 12:05:01 UTC
Created attachment 65475 [details]
font kcm

Using master,

For an unknown reason, the font kcm displays incorrect fonts for a few entries. 

See the attached screenshot. The unreadable entries come from a font called 
"!Y2KBUG"

However, this is not the font I chose (and not the one used). From kdeglobals:

XftAntialias=true
XftHintStyle=hintfull
XftSubPixel=rgb
desktopFont=Droid Sans [unknown],9,-1,5,50,0,0,0,0,0
fixed=Droid Sans Mono [unknown],9,-1,5,50,0,0,0,0,0
font=Droid Sans,9,-1,5,50,0,0,0,0,0
menuFont=Droid Sans [unknown],9,-1,5,50,0,0,0,0,0
shadeSortColumn=true
smallestReadableFont=Droid Sans [unknown],9,-1,5,50,0,0,0,0,0
taskbarFont=mikachan-PB,10,-1,5,50,0,0,0,0,0
toolBarFont=Droid Sans,8,-1,5,50,0,0,0,0,0

I tried changing the values back to Droid but when reopening the font kcm, the issue is back.

(screenshot attached)
Comment 1 Christoph Feck 2011-11-10 12:58:25 UTC
Note that your config file says "Droid Sans" and "Droid Sans [unknown]", which might be the problem. What Qt do you use? Those entries are saved by Qt.
Comment 2 Christophe Marin 2011-11-10 13:32:19 UTC
That's Qt 4.7.4 and now that you mention it, in qtconfig/fonts, the !Y2KBUG is the first listed in the Font substitution drop down menu (the current substitution list is empty however)
Comment 3 Christophe Marin 2011-11-10 13:38:52 UTC
note that "Droid Sans" and "Droid Sans [unknown]" are two different fonts. In the font selector, the first one is called "Droid Sans [misc]" hence the difference
Comment 4 Christophe Marin 2011-11-10 13:43:23 UTC
I just retried:
- Changing all the droid fonts back to Droid Sans [unknown]
# grep Font ~/.kde/share/config/kdeglobals
desktopFont=Droid Sans [unknown],9,-1,5,50,0,0,0,0,0
menuFont=Droid Sans [unknown],9,-1,5,50,0,0,0,0,0
smallestReadableFont=Droid Sans [unknown],9,-1,5,50,0,0,0,0,0
taskbarFont=mikachan-PB,10,-1,5,50,0,0,0,0,0
toolBarFont=Droid Sans [unknown],8,-1,5,50,0,0,0,0,0
activeFont=mikachan-PB,10,-1,5,50,0,0,0,0,0

and when re-running kcmshell4 fonts, they're all listed as !Y2KBUG again
Comment 5 Jekyll Wu 2012-12-04 04:54:14 UTC
The fonts kcm uses KFontRequester (more precisely, a simple subclass of KFontRequester)  for choosing and listing fonts.  Move it to kdelibs/kdeui. But I guess this can only be fixed by Qt.
Comment 6 Alexander Volkov 2017-01-17 16:07:43 UTC
Fixed by https://cgit.kde.org/kwidgetsaddons.git/commit/?id=243626c27f3f27db3ec6c94f5de1e6751b56fa18 (kwidgetaddons 5.31)