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

[forteller]

I started my computer, and I got a message about a crash, so I reported it. But even though it said the indicator-datetime-service crashed, the clock indicator still kept running. I noticed no crash.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: indicator-datetime 12.10.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Mon Sep 17 03:30:46 2012
ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f5c5fef8e79 <e_client_open_sync+9>: mov (%rdi),%rax
 PC (0x7f5c5fef8e79) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
 e_client_open_sync () from /usr/lib/libedataserver-1.2.so.17
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__STRINGv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: indicator-datetime-service crashed with SIGSEGV in e_client_open_sync()
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 #1050290, 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.