On Fri, Oct 24, 2003 at 11:36:25PM +0930, David Purton wrote: > On Fri, Oct 24, 2003 at 10:31:46AM +0100, Anim Asante wrote: > > This has worked for me before when I ran into similar problems. > > There is a file in your home directory called .xsession_error or > > something like that. If your delete it, log off and back on again it > > may fix your problem. Like I indicated, it works for me. > > Sadly no, I neglected to say that I could not get things to work even > using a test account and doing an rm -rf .* in $HOME.
Just in case other people try this, 'rm -rf .*' is VERY DANGEROUS. '.*' expands to include '.' and '..', and if you happen to have privileges to write to the parent directory then you'll end up removing all directories *next* to your current directory as well! Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
