Comment 10 for bug 1294580

Judging from that backtrace it's blocking in e_dbus_calendar_call_get_timezone_sync(), which is being called from e_cal_client_get_timezone_sync(), which in turn is being called from generate_instances() after being called asynchronously from indicator-datetime via a call to e_cal_client_generate_instances().

indicator-datetime is already invoking this as an asynchronous function, so you could argue that this is a lesser bug in EDS -- it shouldn't block. Even then, though, I don't understand why its call of e_cal_client_get_timezone_sync() would take a couple of *seconds*.

Kees, do you have any interesting configuration settings in Evolution / EDS that might account for such a lag? Do you have a lot of calendar sources, remotely-connected/mounted sources, an unusual number of appointments, etc etc?