Bug 171270 - evolution crashes while using autocomplete
evolution crashes while using autocomplete
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Matthew Barnes
Depends On:
Blocks: FC4Update
  Show dependency treegraph
Reported: 2005-10-20 03:38 EDT by Need Real Name
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-12-16 18:29:29 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
bugbuddy stack trace (5.87 KB, text/plain)
2005-10-20 03:39 EDT, Need Real Name
no flags Details
Console output from /usr/libexec/evolution/2.2/evolution-exchange-storage (2.11 KB, text/plain)
2005-10-21 10:46 EDT, Need Real Name
no flags Details
requested stack trace (2.86 KB, text/plain)
2005-12-01 03:09 EST, Need Real Name
no flags Details

  None (edit)
Description Need Real Name 2005-10-20 03:38:43 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050923 Epiphany/1.6.5

Description of problem:
Evolution often crashes when I start typing a name into the To: line and autocomplete is turned on.

Attached will be the bugbuddy stack trace.

If you need any more info, I can get it quite quickly - it crashes several times a day.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Additional info:
Comment 1 Need Real Name 2005-10-20 03:39:05 EDT
Created attachment 120183 [details]
bugbuddy stack trace
Comment 2 Dave Malcolm 2005-10-20 13:49:19 EDT
Thanks for this bug report.

Looks like an assertion is failing in the evolution-exchange-storage process. 
If you manually start this in a terminal before starting evolution, with the


then it should report an error message there when it dies.  What's the output?
Comment 3 Need Real Name 2005-10-21 08:24:09 EDT
This is great! No crashes at all for over a day!

I got this at startup, but no crash yet..
(evolution-exchange-storage:25030): Bonobo-CRITICAL **:
bonobo_object_corba_objref: assertion `BONOBO_IS_OBJECT (object)' failed

(evolution-exchange-storage:25030): Bonobo-CRITICAL **:
bonobo_object_corba_objref: assertion `BONOBO_IS_OBJECT (object)' failed
Comment 4 Need Real Name 2005-10-21 10:46:25 EDT
Created attachment 120256 [details]
Console output from /usr/libexec/evolution/2.2/evolution-exchange-storage

I spoke too soon..
Comment 5 Need Real Name 2005-11-30 04:33:06 EST
Okay, I'm back to my seemingly-hourly routine of evolution crashing whenever I
type something in the To: field.

After a week of this, it's time I updated the bug.
Comment 6 Dave Malcolm 2005-11-30 11:35:33 EST
Thanks for the updated information.

Please can you 
(i) specify the result of:
rpm -q evolution evolution-connector evolution-data-server openldap

(ii) install the corresponding debuginfo packages for evolution-connector and
openldap.  For more information on this see:

Then try locating the evolution-exchange-storage process using
ps ax | grep evo

and then do a "gdb attach" to the process ID.

Then try to reproduce the crash.  When it happens, do a "t a a bt" inside gdb,
and attach the resulting backtrace to this bug.  

Comment 7 Need Real Name 2005-12-01 03:09:27 EST
Created attachment 121666 [details]
requested stack trace

$ rpm -q evolution evolution-connector evolution-data-server openldap

Stack trace attached.
Comment 8 Need Real Name 2005-12-15 05:34:28 EST
I don't think you still need information from me on this one?

I can tell you that the crashes are continuing though.
Comment 9 Need Real Name 2006-03-15 05:43:06 EST
Still crashing a few times a day.
Comment 11 Matthew Barnes 2006-07-31 12:25:04 EDT
Is this bug still present in the latest Rawhide release?

Comment 12 Matthew Barnes 2006-12-16 18:29:29 EST
Closing this bug due to lack of updates.  Feel free to re-open this if the
problem still exists in the latest Fedora Core 6 packages:


Note You need to log in before you can comment on or make changes to this bug.