After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 343656 - evolution 2.6.1 won't start after some time of inactivity.
evolution 2.6.1 won't start after some time of inactivity.
Status: RESOLVED DUPLICATE of bug 337597
Product: bonobo
Classification: Deprecated
Component: libbonobo
2.14.x
Other All
: Normal normal
: ---
Assigned To: Michael Meeks
bonobo qa
Depends on:
Blocks:
 
 
Reported: 2006-06-02 01:17 UTC by Iain Buchanan
Modified: 2006-06-02 09:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Iain Buchanan 2006-06-02 01:17:06 UTC
Please describe the problem:
Note: I'm not upgrading or installing anything, this is not an "old version lying around" problem :)

Evolution runs fine.  If I close it for a few minutes, then start again without logging off or doing anything interesting, evolution won't start.

Steps to reproduce:
1. Run evo
2. Exit evo
3. wait
4. Run evo


Actual results:
A dialog pops up showing:
Evolution can not start.

Your system configuration does not match your Evolution configuration.

Click help for details

(also, the help button directs me to a non-existant web page, but that's another issue :)

Expected results:
Evolution starts ok.

Does this happen every time?
depending on how long I wait, yes.

Other information:
After I get the dialog, I do a --force-shutdown (empty lines deleted):

$ evolution --force-shutdown
** (evolution:30102): WARNING **: Failed to send buffer
** (evolution:30102): WARNING **: Failed to send buffer
Bonobo activation failure: Unknown CORBA exception id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0'
** (evolution:30102): WARNING **: Failed to send buffer
Bonobo activation failure: Unknown CORBA exception id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0'
** (evolution:30102): WARNING **: Failed to send buffer
Bonobo activation failure: Unknown CORBA exception id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0'
** (evolution:30102): WARNING **: Failed to send buffer
Bonobo activation failure: Unknown CORBA exception id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0'
** (evolution:30102): WARNING **: Failed to send buffer
Bonobo activation failure: Unknown CORBA exception id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0'
** (evolution:30102): WARNING **: Failed to send buffer
Bonobo activation failure: Unknown CORBA exception id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0'
** (evolution:30102): WARNING **: Failed to send buffer
Bonobo activation failure: Unknown CORBA exception id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0'
** (evolution:30102): WARNING **: Failed to send buffer
Bonobo activation failure: Unknown CORBA exception id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0'
** (evolution:30102): WARNING **: Failed to send buffer
Bonobo activation failure: Unknown CORBA exception id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0' 


Evo won't start after --force-shutdown.

There is a bonobo-activation-server task running.  If I kill it manually, evolution starts normally.
Comment 1 Iain Buchanan 2006-06-02 01:24:11 UTC
FWIW:

$ ps aux | grep bonobo
iain      2589  0.0  1.0   8484  5184 ?        Ss   09:57   0:00 /usr/libexec/bonobo-activation-server --ac-activate --ior-output-fd=24
Comment 2 Nigel Metheringham 2006-06-02 08:28:03 UTC
Could this be related to
  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=188143

Comment 3 Michael Meeks 2006-06-02 09:01:06 UTC
this sounds like the well-known file descriptor leak on failed activation in older libbonobo's bonobo-activation-fork-server.c's.

Basically the mail notification thing fails to launch, and the client keeps batching thousands of back-to-back activation requests until file descriptors are exhausted in b-a-s and then it stops.

Of course - that means that nothing will activate not just evo - try adding a different/ new applet to the panel.

Either way - fixed in HEAD I believe.
Comment 4 Michael Meeks 2006-06-02 09:02:44 UTC

*** This bug has been marked as a duplicate of 337597 ***