evolution-calendar-factory crashed with SIGSEGV in g_rec_mutex_lock()

[MaxistXXL]

I cannot create an account, neither restoring from my backup, nor creating a new one. Evolution just continues to show me the initial configurations manager.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: evolution-data-server 3.5.92-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
Uname: Linux 3.5.0-14-generic i686
ApportVersion: 2.5.2-0ubuntu1
Architecture: i386
Date: Tue Sep 18 16:33:52 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120917)
ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb750d0b3 <g_rec_mutex_lock+19>: mov (%eax),%edx
 PC (0xb750d0b3) ok
 source "(%eax)" (0xaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
 g_rec_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/evolution-data-server/calendar-backends/libecalbackendcontacts.so
 g_cclosure_marshal_VOID__OBJECT () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: evolution-calendar-factory crashed with SIGSEGV in g_rec_mutex_lock()
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 #1045819, 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.