For me, the fix was to delete a recently-created task in Evolution.
DETAILS
I encountered this error a few hours ago, after I added a task in Evolution (something I rarely do). I set three reminders for the task. Within 10 minutes, the datetime indicator applet froze at 16:40. The Date tab in the Date/Time settng applet was also greyed-out, so I was unable to turn it back on. I re-booted three times, hoping it was an update issue, but all I saw was the datetime indicator crash repeatedly and then vanish within seconds of my logging in.
I searched /var/log/syslog for "crash" and found it was the datetime-indicator service that had crashed. I was able to confirm this with the following command:
systemctl status indicator-datetime --user
I tried restarting it, but I got a message that the service had crashed too many times.
Since I was fairly certain that this was related to the Evolution Task that I just created, I deleted it, restarted the service, and the datetime indicator came back.
SUMMARY
For me, the fix was to delete a recently-created task in Evolution.
DETAILS
I encountered this error a few hours ago, after I added a task in Evolution (something I rarely do). I set three reminders for the task. Within 10 minutes, the datetime indicator applet froze at 16:40. The Date tab in the Date/Time settng applet was also greyed-out, so I was unable to turn it back on. I re-booted three times, hoping it was an update issue, but all I saw was the datetime indicator crash repeatedly and then vanish within seconds of my logging in.
I searched /var/log/syslog for "crash" and found it was the datetime-indicator service that had crashed. I was able to confirm this with the following command:
systemctl status indicator-datetime --user
I tried restarting it, but I got a message that the service had crashed too many times.
Since I was fairly certain that this was related to the Evolution Task that I just created, I deleted it, restarted the service, and the datetime indicator came back.
Hopefully, this will help someone else.