John Pettigrew wrote:

In a previous message, doc wrote:

...

When Failsafe brings up a window I enter kde and I get the same old "bad font, likely due to a permissions problem" (paraphrased).

I've had a similar problem that was due to fiddling with permissions on directories - a directory must have the execute bit set in order to be openable. Perhaps one of your directories (e.g. the ~/.kde3 directory) has lost this setting?

John

I looked in /home/abc/.kde3 and all looks well. Correct Owner and Group. I poked around a bunch of other folders and all looks OK there as well. Is there a file that is referenced during the logon process (after I enter the password) that I might check for errors? Soemthing is picking up something from somewhere and inserting bad data, causing this problem yet again! It is really frustrating to have to waste time repairing what has already been fixed. Thanks! doc

Anders Johansson wrote:

On Thursday 01 July 2004 15.55, doc wrote:

...

Yesterday I powered my notebook off at work, brought it home, and powered back up and the same problem has reoccurred forcing me to long in Failsafe instead of KDE. The login window flashes and returns me to login -- only Filsafe works.

When this happens, switch to a text console with ctrl-alt-f1, log in and have a look in $HOME/.xsession-errors. Hopefully that will have some clue about what's going on

$HOME/.xsession-errors comes up empty. /var/mail/edoc contains only the words "Error opening file" Tried to run kde from Bash and get "xset unable to open display" A private E-mail suggested I try renaming ~/.kde to something else and log in again. He thought that would recreate my config files. Worth a try I suppose! doc