Hi, A very odd thing happened yesterday. I had a perfectly working KDE desktop (with anti-aliasing and fonts imported from windows) for both root and users. I then decided to update some packages (using cooker) to get "xcdroast" working as mentionned at: http://forum.mandrakesoft.com/article.php?sid=941&lang=en&mode=thread&order=0&thold=0 I went to a cooker web site and downloaded: mandrake_desk-8.0-10mdk mkisofs-1.13-7mdk.i586.rpm cdrecord-1.10-1mdk.i586.rpm cdrecord-cdda2wav-1.10-1mdk.i586.rpm and installed them manually doing: rpm -Uvh [package file name] I could not find: xcdroast-0.98-8mdk.i586.rpm and decided to do it later. Then I cannot remember exactly why but I logged out of KDE and logged back in again and the disaster struck... KDesktop, khotkeys, kicker, kwrited, klipper, kwin crashed (signal 11) I tried several times but no luck. I tried to launch KDE as root and no problem. After investigation, I found out that if I set the anti-aliasing flag to false in /home/myuser/.kde/share/config/kdeglobals then I can launch KDE again as myuser (note: the flag is still on for root and it works fine... go figure). I then created a new user and as soon as the anti-aliasing flag was turned on I could not launch KDE anymore... (1) What can trigger such nasty behaviour? Could that be the upgrade to mandrake_desk-8.0-10mdk from cooker? (2) For the time being I am running all my users with the anti-aliasing flag set to false, but if I go to the KDE Control Center/LooknFeel/ Fonts where I have: fixed width Lucida Console 8 iso8859-1 and I try to change the fixed width fond by clicking on choose then I can kiss my KDE session goodbye, it seems like xfs gets killed by doing that... because once back to the console, ps -ax | grep xfs does not show any xfs running and I have to do: service xfs start then going back to KDE works. (3) Can the imported fonts from Windows cause that? note: launching other WMs like Gnome, Enlightenment, etc.. works fine. Cheers, Fred
