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

[Adam Bruce]

Crashed when editing some printer settings

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: evolution-data-server 3.6.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27
Uname: Linux 3.2.0-30-generic x86_64
ApportVersion: 2.6.1-0ubuntu2
Architecture: amd64
Date: Wed Oct 10 01:30:53 2012
ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
ProcEnviron:
 SHELL=/bin/false
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.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_tpp_change_priority () from /lib/x86_64-linux-gnu/libpthread.so.0
Title: evolution-calendar-factory crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to quantal on 2012-09-09 (30 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 __assert_fail_base (fmt=<optimized out>, assertion=0x7fd04ff5be30 "new_prio == -1 || (new_prio >= __sched_fifo_min_prio && new_prio <= __sched_fifo_max_prio)", file=0x7fd04ff5be24 "tpp.c", line=<optimized out>, function=<optimized out>) at assert.c:94
 __GI___assert_fail (assertion=0x7fd04ff5be30 "new_prio == -1 || (new_prio >= __sched_fifo_min_prio && new_prio <= __sched_fifo_max_prio)", file=0x7fd04ff5be24 "tpp.c", line=63, function=0x7fd04ff5bf00 "__pthread_tpp_change_priority") at assert.c:103
 __pthread_tpp_change_priority (previous_prio=-1, new_prio=2564) at tpp.c:61
 __pthread_mutex_lock_full (mutex=0x7fd03400dc10) at pthread_mutex_lock.c:415
 cal_backend_contacts_remove_book_record (cbc=0x1ae80e0, source=0x7fd03001a810) at e-cal-backend-contacts.c:229

[Launchpad Janitor (janitor)]

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