Edit /usr/bin/killev and put $debug=1 at the beginning. Run it (without evo running otherwise it'll kill it), then grab the first four lines (which are related to executive-summary), then launch evo, wait for it to block.
Here are the four kills for my system (it may depends of the system you're running because killev uses oaf to retrieve the components names...): killall -9 evolution-executive-summary killall -9 lt-evolution-executive-summary killall -9 evolution-execut killall -9 lt-evolution-exe Then paste them in a shell. Should destroy the bad component. Brice On Wed, 2002-01-30 at 11:31, Brian J. Murrell wrote: > On Wed, Jan 30, 2002 at 09:57:47AM +0100, Brice Figureau wrote: > > Hi, > > Hello, > > > I encounter the same trouble a few days ago. > > It seemed that it came from the evolution-executive-summary component. > > That would look right here too. > > > The only solution we found was to edit the '/usr/bin/killev' script, > > extract the executive-summary part, > > Which was which part. I experimented but could not isolate it. > > > launch evolution (which will block > > forever), then kill the executive summary, and then voila... > > >From the testing I did do this looks like it will work. I just need > to know how to isolate the exec-summary part. > > > Maybe evolution was stuck in trying to access a website somewhere to get > > its RSS/RDF file for the executive. > > That is what I was thinking. Bad design if so. > > > Hope this helps. > > It does, thanx. > > b. > > > -- > Brian J. Murrell > > >
