Clock indicator-datetime stopped ticking after adding Google account in GOA

[Jérôme Poulin]

After about a month without a working clock on my laptop's Ubuntu session, I decided to delete all indicator/goa/online account related stuff in my .config and .cache directories since it wasn't working anyway.
I booted back in my session and the clock was back and ticking!
I added my GMail account in Online Accounts afterward it said applications couldn't access my account, I entered my password again and the clock stopped ticking and indicator-application crashed.
I immediately removed the online account, logged out then in and the clock was back.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: indicator-application 12.10.1daily13.01.25-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
Uname: Linux 3.10.0-6-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Thu Aug 1 19:39:33 2013
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-application-service
MarkForUpload: True
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-application-service
Signal: 5
SourcePackage: indicator-application
StacktraceTop:
 ?? ()
 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: indicator-application-service crashed with signal 5 in g_type_create_instance()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio dialout fuse libvirtd lp plugdev pulse-access src sudo users vboxusers video wireshark

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1205959, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.