Speaking of fontconfig bugs ... and using unstable versions
In case you have upgraded your fontconfig packages to those I provided in my blog entry about new fontconfig version, you may have run into KDE bug #116176 with the KDE3.5rc1 packages. Well, I warned you. That sometimes happens with unstable versions. I suggest you downgrade again or do your own build of newer fontconfig version or do whatever you want to do, but I'm not going to provide newer packages. It's still an unstable version after all.
Speaking of fontconfig bugs, with my current optimized KDE build I use for examining KDE startup performance, 1/3 (yes, that reads one third) of the startup time (with warm caches) is spent in fontconfig. And that's already this new unstable version of fontconfig with the better caches *sigh*. Fontconfig apparently still needs a lot of work.
Just in case you don't believe me, here is a gzipped file for sysprof. Download, gunzip, load into sysprof and see for yourself. Note that those 72.45 is actually 100%. And note that there's QFontDatabase::findFont() with 28.06 (==38.7%), which, if you expand the tree for it, is almost completely spent in fontconfig. Don't get me started on how KDE is so slow and bloated because we KDE developers don't care about performance.
Thanks to Dirk Mueller and
Thanks to Dirk Mueller and Stephen Kulow at SuSE, fontconfig is getting quite a bit quicker these days. Try the latest branch. FcCompareValueList, in particular, has had some work done to it.
Oh, and if 116176 was a fontconfig bug, then it's probably fixed now.