mission-control-5 crashed with SIGABRT in __libc_message()

[Pranesh Prakash]

1. Precise Pangolin beta 2

2. telepathy-mission-control-5:
  Installed: 1:5.12.0-0ubuntu2
  Candidate: 1:5.12.0-0ubuntu2
  Version table:
 *** 1:5.12.0-0ubuntu2 0
        500 http://in.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

3 & 4. Unsure how it happened.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-mission-control-5 1:5.12.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
ApportVersion: 2.0-0ubuntu5
Architecture: amd64
CrashCounter: 1
Date: Wed Apr 11 17:29:08 2012
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic root=UUID=52f92201-d051-4e74-9ab6-726d93decc24 ro quiet splash vt.handoff=7
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=en_IN:en
 LANG=en_IN
Signal: 6
SourcePackage: telepathy-mission-control-5
Title: mission-control-5 crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 __libc_message (do_abort=2, fmt=0x7f744119e050 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
 malloc_printerr (action=3, str=0x7f744119b001 "free(): invalid pointer", ptr=<optimized out>) at malloc.c:5007
 debug_message_free (msg=0xf3a4c0) at debug-sender.c:147
 _tp_debug_sender_take (self=0xd76260, new_msg=0xe4dba0) at debug-sender.c:367
 tp_debug_sender_add_message (self=0xd76260, timestamp=<optimized out>, domain=<optimized out>, level=<optimized out>, string=<optimized out>) at debug-sender.c:414

[Launchpad Janitor (janitor)]

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

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