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

[David Baucum]

Crash occurred after loging into my account.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: indicator-datetime 12.10.3daily13.03.06-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
Uname: Linux 3.8.0-11-generic i686
ApportVersion: 2.9-0ubuntu2
Architecture: i386
Date: Fri Mar 8 19:29:25 2013
ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime-service
InstallationDate: Installed on 2012-10-25 (134 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MarkForUpload: True
ProcCmdline: /usr/lib/i386-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: 0x804d97f: mov 0x8(%eax),%eax
 PC (0x0804d97f) ok
 source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__OBJECTv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/i386-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-22 (14 days ago)
UserGroups: adm cdrom dip fuse 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 #1132174, 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.