-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
If you set it up using kcm it's kdm. The rule of thumb is: if it looks like crap it's xdm, if there's just one line and you enter alternately username and password then it's gdm, if you get a list of user icons it's kdm
It's kdm. So the mechanism for representing fonts to KDM and KDE is the problem, whatever that is.
No, unless I'm completely out to lunch Xft is the freetype extension to X. All through the 3.x series of X servers you needed xfs to get anti aliasing, unless my memory is going faster than I had hoped.
Right, xft is Freetype, and is the source of AA. Ever since I've used Suse I've had the xfs daemon off. If you turn it on, and set XF86Config to invoke the daemon, you'd be depending on that for font service rather than emumerating the font dirs in XF86Config, but no AA. I never figured out how to set fonts in Java and Adobe, so can't see if they're affected. I can read them, and they seem unaffected, but I can't prove that. Beginning to think that one of my fonts is tripping up KConfig's Font Installer. But the only one it's ever complained about is Cracks; I tell it to proceed anyway and it seems to finish fine. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj2ci8IACgkQnQ18+PFcZJsRywCfaJx9YHk2Ne18xdD1LxlJbTcp gioAn3Q3y3vHvG9qnF+/6DrArDdNFKSr =RxkJ -----END PGP SIGNATURE-----