Comment 6 for bug 90258

I'll try it later, but I'm not really sure how to use gdb on a process that is not really crashing - it simply stays active, in theory (if it would not keep open bonobo-activation-server what does harm to some applets (gswitchit etc) it could be re-used after re-login.

The former strace-output seems not to be the best for finding out what is going wrong, starting e-d-s from terminal with strace directly I got some error messages, which seem to be a bit more helpful.

---
Especially the following lines seem to be interesting:
09:21:33.882038 write(2, "\n(evolution-data-server:7683): G"..., 112
(evolution-data-server:7683): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed
) = 112
09:21:33.882138 write(2, "\n(evolution-data-server:7683): l"..., 148
(evolution-data-server:7683): libedata-cal-CRITICAL **: e_cal_backend_internal_get_default_timezone: assertion `E_IS_CAL_BACKEND (backend)' failed
) = 148
09:21:33.882250 write(2, "\n(evolution-data-server:7683): G"..., 113
(evolution-data-server:7683): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
) = 113
---

Please note: After setting up evolution on a clean account, everything went well untill I set up birthday-calendar events. Same seems to be true when tasks or other events are added.