indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()

[Achim Behrens]

uptodate 13.04.
got this appreport window on login

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: indicator-datetime 12.10.3daily13.03.07-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
Uname: Linux 3.8.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu2
Architecture: amd64
Date: Sun Mar 24 11:11:24 2013
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
InstallationDate: Installed on 2011-10-29 (512 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MarkForUpload: True
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
SegvAnalysis:
 Segfault happened at: 0x406597: mov 0x8(%rax),%rcx
 PC (0x00406597) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__OBJECTv () 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_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()
UpgradeStatus: Upgraded to raring on 2013-02-24 (28 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: gnome-session[2246]: WARNING: Failed to start app: Unable to start application: Kindprozess »indicator-weather« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden)

[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 #1098812, 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.