evolution-calendar-factory assert failure: evolution-calendar-factory: pthread_mutex_lock.c:312: __pthread_mutex_lock_full: Assertion `(-(e)) != 3 || !robust' failed.

Bug #1062229 reported by eris23
94
This bug affects 21 people
Affects Status Importance Assigned to Milestone
evolution-data-server (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

on log in

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: evolution-data-server 3.6.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-17.26-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
AssertionMessage: evolution-calendar-factory: pthread_mutex_lock.c:312: __pthread_mutex_lock_full: Assertion `(-(e)) != 3 || !robust' failed.
Date: Fri Oct 5 03:53:48 2012
ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120312)
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:
 __assert_fail_base (fmt=<optimized out>, assertion=0x7f2fa3b10938 "(-(e)) != 3 || !robust", file=0x7f2fa3b10f3e "pthread_mutex_lock.c", line=<optimized out>, function=<optimized out>) at assert.c:94
 __GI___assert_fail (assertion=0x7f2fa3b10938 "(-(e)) != 3 || !robust", file=0x7f2fa3b10f3e "pthread_mutex_lock.c", line=312, function=0x7f2fa3b10a40 <__PRETTY_FUNCTION__.9925> "__pthread_mutex_lock_full") at assert.c:103
 __pthread_mutex_lock_full (mutex=0x7f2f88012830) at pthread_mutex_lock.c:312
 ?? () 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
Title: evolution-calendar-factory assert failure: evolution-calendar-factory: pthread_mutex_lock.c:312: __pthread_mutex_lock_full: Assertion `(-(e)) != 3 || !robust' failed.
UpgradeStatus: Upgraded to quantal on 2012-10-03 (2 days ago)
UserGroups:

Revision history for this message
eris23 (jdkatz23) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __assert_fail_base (fmt=<optimized out>, assertion=0x7f2fa3b10938 "(-(e)) != 3 || !robust", file=0x7f2fa3b10f3e "pthread_mutex_lock.c", line=<optimized out>, function=<optimized out>) at assert.c:94
 __GI___assert_fail (assertion=0x7f2fa3b10938 "(-(e)) != 3 || !robust", file=0x7f2fa3b10f3e "pthread_mutex_lock.c", line=312, function=0x7f2fa3b10a40 "__pthread_mutex_lock_full") at assert.c:103
 __pthread_mutex_lock_full (mutex=0x7f2f88012830) at pthread_mutex_lock.c:312
 cal_backend_contacts_remove_book_record (cbc=0x27160e0, source=0x7f2f8401a810) at e-cal-backend-contacts.c:229
 g_closure_invoke (closure=0x2720ac0, return_value=0x0, n_param_values=2, param_values=0x7fff91552950, invocation_hint=0x7fff915528f0) at /build/buildd/glib2.0-2.34.0/./gobject/gclosure.c:777

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in evolution-data-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Paul Larson (pwlars)
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in evolution-data-server (Ubuntu):
status: New → Confirmed
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1062229

tags: added: iso-testing
piotr zimoch (ebytyes)
Changed in evolution-data-server (Ubuntu):
status: Confirmed → New
status: New → Incomplete
status: Incomplete → Opinion
status: Opinion → Invalid
status: Invalid → Confirmed
status: Confirmed → In Progress
status: In Progress → Fix Committed
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.