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
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'
On Tue, Jan 29, 2002 at 05:39:03PM -0600, Tech At Mathco Dot Com wrote:
if running evolution from the console, any error messages?
From the console? Does evolution have a console mode? I thought it
was gui (X11/Gnome) only.
$ DISPLAY= evolution
Gtk-WARNING **: cannot open display:
Maybe
No. What was meant was that you should open a terminal and:
$ evolution
instead of starting it from a menu or a desktop icon. That way any
messages it prints out while executing will be visible in that terminal
window.
On Tue, 2002-01-29 at 21:48, Brian J. Murrell wrote:
On Tue, Jan 29,
