evolution-calendar-factory assert failure: *** Error in `/usr/lib/evolution/evolution-calendar-factory': corrupted double-linked list: 0xb1d039a8 ***

[Sripad S. Kowshik]

Happened on reboot.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: evolution-data-server 3.8.3-0ubuntu5
ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2
Uname: Linux 3.10.0-5-generic i686
ApportVersion: 2.11-0ubuntu1
Architecture: i386
AssertionMessage: *** Error in `/usr/lib/evolution/evolution-calendar-factory': corrupted double-linked list: 0xb1d039a8 ***
CrashCounter: 1
Date: Fri Jul 26 08:31:22 2013
ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
ExecutableTimestamp: 1373481719
InstallationDate: Installed on 2013-03-23 (124 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130322)
MarkForUpload: True
ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
ProcCwd: /home/sripad
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
Signal: 6
SourcePackage: evolution-data-server
StacktraceTop:
 __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0xb7382530 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:199
 malloc_printerr (action=<optimized out>, str=<optimized out>, ptr=0xb1d039a8) at malloc.c:4902
 _int_free (av=0xb1d00010, p=0xb1d03920, have_lock=0) at malloc.c:3912
 g_free () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/evolution-data-server/calendar-backends/libecalbackendcaldav.so
Title: evolution-calendar-factory assert failure: *** Error in `/usr/lib/evolution/evolution-calendar-factory': corrupted double-linked list: 0xb1d039a8 ***
UpgradeStatus: Upgraded to saucy on 2013-06-19 (36 days ago)
UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo vboxusers

[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 #1203244, 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.