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

[Finnish]

I try to import evolution backup file from ubuntu 12.04

Evolution always crashes while Restoring Evolution Data and goes back to "Welcome to Evolution"

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: evolution-data-server 3.5.91-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 11 13:48:09 2012
ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120910)
ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fe042651f60 <g_rec_mutex_lock>: mov (%rdi),%rax
 PC (0x7fe042651f60) ok
 source "(%rdi)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
 g_rec_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/evolution-data-server/calendar-backends/libecalbackendcontacts.so
 g_closure_invoke () 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
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 #1041723, 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.