It appears to be related to my EWS account in evolution. When I remove that, all works fine. When I added that account again (all default settings, except for checking mail every 10 minutes in stead of 60 and disabeling the 'apply filters'), the clock stopped after a short while (but several seconds later than previously). At that time I saw that /usr/lib/evolution/evolution-calendar-factory was consuming quite some cpu power.
When I remove the account again and kill the remaining /usr/lib/evolution/evolution-* processes, the clock starts ticking again (after waiting some time). I've configured the ews account again. Now it seems that the clock stops ticking when the cpu usdage of evolution-calendar-factory dropped. Looks like that there's somthing wrong in evolution-calendar-factory that causes the clock to stop. Killing just evolution-calendar-factory gets the clock running again. I don't think I've an abnormal number of appointments in my calander. BWT. I'd rather see the clock going on when errors occur... -- 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
