Re: Problems with Garnome 0.18.3

[Jens Askengren <jensus linux nu>]

ons 2002-11-06 klockan 15.56 skrev Anthony R. Mattke:

> I pulled a top up and saw that
> gnome_segv2 had several processes going and were all rather active.. 
> 
>  PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
> 1098 foo       25   0  5844 5844  4768 S    25.9  2.2   0:00 gnome_segv2
> 1100 foo       25   0  5844 5844  4768 S    25.9  2.2   0:00 gnome_segv2
> 1099 foo       25   0  5844 5844  4768 S    23.1  2.2   0:00 gnome_segv2
> 1101 foo       25   0  3784 3784  3024 R    12.0  1.4   0:00 gnome_segv2
> 1096 foo       25   0  5844 5844  4768 S    11.1  2.2   0:00 gnome_segv2
> 
> Anyone have any idea of whats going on ? I've attached the Garnome
> sessions file.. just inccase i'm an idiot.

I have seen this before..
There is probably a segmentation fault in the initialization of a
library, triggering gnome_segv2 to start. gnome_segv2 uses the same
library, and also crashes, causing another gnome_segv2 to be spawned...
etc etc.

In my case it was because of a Xft bug, but it might be something
compleately different that triggers the behaviour on your machine.

To stop the gnome_segv2 spamming, replace the last line in your session
file with this one:

exec /usr/local/garnome/bin/gnome-session --disable-crash-dialog

If you know how to run gdb, the next step is to create a stacktrace, and
submit a bug repport. Balsa has a nice page describing how to do this:
http://balsa.gnome.org/bugs.html


	-Jens