evolution-calendar-factory crashed with SIGABRT in __assert_fail_base()

[Tobiasz Jarczyk]

Happened after restart after some changes in the system and reinstalling some packages.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: evolution-data-server 3.6.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
Date: Fri Oct 5 01:24:24 2012
ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
ProcEnviron:
 SHELL=/bin/false
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=pl:en
 LANG=pl_PL.UTF-8
Signal: 6
SourcePackage: evolution-data-server
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
 __pthread_mutex_lock_full () from /lib/x86_64-linux-gnu/libpthread.so.0
Title: evolution-calendar-factory crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to quantal on 2012-06-28 (98 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 __assert_fail_base (fmt=<optimized out>, assertion=0x7fc4fece79d0 "robust || (oldval & 0x40000000) == 0", file=0x7fc4fece7f3e "pthread_mutex_lock.c", line=<optimized out>, function=<optimized out>) at assert.c:94
 __GI___assert_fail (assertion=0x7fc4fece79d0 "robust || (oldval & 0x40000000) == 0", file=0x7fc4fece7f3e "pthread_mutex_lock.c", line=321, function=0x7fc4fece7a40 "__pthread_mutex_lock_full") at assert.c:103
 __pthread_mutex_lock_full (mutex=0x24f64a0) at pthread_mutex_lock.c:321
 cal_backend_contacts_remove_book_record (cbc=0x27760e0, source=0x7fc4e001b010) at e-cal-backend-contacts.c:229
 g_closure_invoke (closure=0x2780b80, return_value=0x0, n_param_values=2, param_values=0x7fff19df6430, invocation_hint=0x7fff19df63d0) at /build/buildd/glib2.0-2.34.0/./gobject/gclosure.c:777

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.