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

[khut]

kevin@x200:~$ lsb_release -rd
Description: Ubuntu Raring Ringtail (development branch)
Release: 13.04

kevin@x200:~$ apt-cache policy indicator-datetime
indicator-datetime:
  Installed: 12.10.3daily13.03.26-0ubuntu1
  Candidate: 12.10.3daily13.03.26-0ubuntu1
  Version table:
 *** 12.10.3daily13.03.26-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
        100 /var/lib/dpkg/status

Not sure what caused it or even what this package does.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: indicator-datetime 12.10.3daily13.03.26-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
Uname: Linux 3.8.0-15-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Fri Mar 29 17:59:12 2013
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
MarkForUpload: True
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=en_US.UTF-8
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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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.