Re: Help! E/Gnome system crash

[Aaron Prohaska <verdesoft verdesoft net>]

I should have done included this information with my first email, but
here it is a little late.

What I am running:

RedHat 5.2
Mach_64 Xserver
Gnome 1.0
Enlightenment 0.15
Kernel 2.2.2-ac5

Some other things I am wondering about is where if any does the log
file/s for gnome sit? I would liket to be able to look at output of
what's going on when Gnome crashes (if its gnome). If there is no log
file for gnome is there some way to make one? When I am in
gnome/enlightenment and it freezes I can get out by hitting
Ctrl+Alt+Backspace to kill the Xserver and when I do this and am back on
the commmand line there is a lot of error messages that I would like to
copy. How can I do this?

Thanks,

Aaron

"Jesse D . Sightler" wrote:
> 
> On Sat, 10 Apr 1999 18:14:22 Aaron Prohaska wrote:
> 
> > So with that done I typed startx and waited to see what happened. Well
> > to my surprise it worked. I was very happy to have it running. I went
> > right away to playing around with settings and changing the colors and
> > themes which I liked very much. I noticed two things that were happening
> > while doing this. Moving windows around was slow and when I went to the
> > dialogs option in the control-center the hard drive starting being
> > wildly accessed. This lasted for about 2-4 minutes and then stopped.
> > After that happened everything in E/Gnome became very slow and
> > impossible to deal with. I logged out at that point and restarted it.
> > Once restarted it behaved fine foe a while. So again I proceeded to
> > start playing with settings again. Only this time everything completely
> > locked up! I don't remember exactly what I was doing at the time since
> > it was late last night, but it killed the whole system.
> 
> I've seen this several times with the latest Gnome CVS dist here.  So far,
> it looks like it doesn't happen here when running without "esd".  You might
> try doing a "killall esd" after logging into Gnome to see if that makes things
> more stable.
> 
> It looks like a kernel bug of some sort, so maybe an upgrade to the latest kernel
> would be a good idea as well (I'm still at 2.2.1).
> 
> ---------------
> Jesse D. Sightler
> http://www3.pair.com/jsight/
> 
> "An honest answer can get you into a lot of trouble."
>          - Anonymous

-- 
_________________________________________________

mailto:verdesoft@verdesoft.net
VerdeSoft Internet Services
http://www.verdesoft.net/