Comment 21 for bug 1311213

Thanks for the update. Interestingly, the evolution-calendar-factory is idle, it doesn't do anything at the moment of the backtrace capture. The evolution backtrace, on the other hand, shows that there was received a notification about added components to a view (that's when the calendar finds an event which satisfies view's criteria), where the calendar wanted to marks days with events in the left-bottom calendar. This got stuck on the timezone request, the evolution asked for a timezone definition the calendar factory. The interesting part here is that the timezone ID seems to be garbled, it shows value " 1".

I just tested this and I can reproduce this too.