On Mon, 10 Jul 2006 11:10:41 +0200 Jan Willem Stumpel wrote: > The vital clue came from googling with keywords 'luxi mono kde': > http://lists.kde.org/?l=kde&m=110617132115635&w=2 > > This says that the Postscript (Type1) versions of the Luxi fonts > are the culprits. And indeed, I had such versions in > /usr/share/fonts/type1/t1-xfree86-nonfree. Turns out they are from > a package t1-xfree86-nonfree which I had installed ages ago. > > I then did dpkg --purge t1-xfree86-nonfree. This is not enough to > show Luxi mono in the KDE menu. For this, Luxi Mono Bold and Luxi > Mono Bold Oblique have to be cleaned up, because they each have > one character of width 682 and four characters of width 1338 > (instead of 1229). One way to do this is to use fontforge on the > .ttf's, save as .sfd, edit the .sfd, and generate new ttf's. Now > Luxi Mono will be in the KDE font menu. As Christian said, you > have to restart KDE for it to work. Re-installing > t1-xfree86-nonfree makes the problem return. > > Please try this. I did a few other things with the fonts (removed > some characters with names like 'glyph<number>', and which seem to > have no content, at the end) but I do not know if this was necessary. > > So now the problem is why t1-xfree86-nonfree causes this. The > above link says that the basic cause is a bug in fontconfig. But I > have no idea what fontconfig actually does.
Thanks alot! I'll have a look at fixing those errors, based on your investigation. - Jonas -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm
pgptCaEmHtpAo.pgp
Description: PGP signature