evolution-calendar-factory crashed with SIGABRT

[Per-Inge]

Got this bug directly after logout and login.
I am not using Evolution.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: evolution-data-server 3.6.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
Date: Sun Oct 7 19:34:34 2012
Disassembly: => 0x7f5c19ccf425: Cannot access memory at address 0x7f5c19ccf425
ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120714.1)
ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
ProcEnviron:
 SHELL=/bin/false
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: evolution-data-server
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: evolution-calendar-factory crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libjavascriptcoregtk-3.0-0 version 1.9.2-1ubuntu4 required, but 1.10.0-0ubuntu1 is available
outdated debug symbol package for libstdc++6: package version 4.7.2-2ubuntu1 dbgsym version 4.6.3-1ubuntu5
outdated debug symbol package for initscripts: package version 2.88dsf-13.10ubuntu13 dbgsym version 2.88dsf-13.10ubuntu11.1
libwebkitgtk-3.0-common version 1.9.2-1ubuntu4 required, but 1.10.0-0ubuntu1 is available
libwebkitgtk-3.0-0 version 1.9.2-1ubuntu4 required, but 1.10.0-0ubuntu1 is available
outdated debug symbol package for libtxc-dxtn-s2tc0: package version 0~git20110809-3 dbgsym version 0~git20110809-2.1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!