Hi,
        I find myself in gnome sawfish about 99% of the time these days.  But twice 
now including today (just now in fact) it has screwed up. (seems to be when I 
'halt' out of gnome without closing all the open applications).  
        Luckily I made a directory called gnome-backup in my home directory a while 
back and chucked a copy of every directory in my home directory that started 
with .gnome-'whatever', and .gconf, .gconfd, and .gnome_private  in it.  I 
just had to copy all the files in this directory back in to my home directory 
and hey presto my desktop is restored.  I have actually backed up kde like 
this also and had to use it when kde has let me down in the past!

BTW my restored gnome desktop can be viewed at:
http://homepages.ihug.co.nz/~nicke/linux/desktop/screenshot.jpg 
 
Nick E

On Friday 26 April 2002 3:25 pm, Julian Carver wrote:
> Michael,
>
> I had something very similar just recently when I tried to upgrade to
> kde3.  I use gnome, but wanted to have a look at what kde3 was like. I'm
> using Mandrake 8.1
>
> Unwisely I did a nodeps install because I couldn't be bothered dealing
> with the depedencies.  I just installed everything from the kde3 ftp
> directory.  I have now learned my lesson about nodeps...
>
> Firstly kde3 wouldn't start properly, and secondly it munted gnome.
> Gnome would start, but was very slow in starting, and sawfish wouldn't
> start at all.
>
> I managed to resolve this by getting rid of all the kde3 and associated
> new rpms, moving my .gnome and .sawfish user directories, and logging in
> again.  This fixed everything up.  Not very scientific, but it worked.
>
> Not sure if this helps, but maybe a similar cause?
>
> Julian
>
> > I run Redhat 7.2.  Whenever I login (run level 3) and startx, gnome
> > appears to load up but I end up with a blank blue screen without any
> > icons etc - absolutely nothing.  I can crash back into level 3 without
> > a problem using the keyboard.
> >
> > I really need to know what's failing, I got an error message the very
> > first time it happened but like the pro I am I ignored it and now I
> > don't get it anymore.  Where do I find the log that the errors are
> > sent to?
> >
> > This fault ocurred out of the blue - there was no reason, like cold
> > reboot, to blame.  Basically I want to resurrect the machine without
> > having to reinstall Redhat all over again.
> >
> > Regards,
> > Michael.

Reply via email to