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? ** Changed in: indicator-datetime (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294580 Title: indicator-datetime-service panel clock freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1294580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs