mission-control-5 crashed with SIGSEGV in g_slice_alloc()

[Geier]

I'm not using telepathy, but this error report just came out of the blue.

Sorry I can't give any more detail about the error.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: telepathy-mission-control-5 1:5.14.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
Uname: Linux 3.8.0-11-generic x86_64
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
Date: Thu Mar 14 15:26:35 2013
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationDate: Installed on 2013-03-08 (5 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130308)
KernLog:

MarkForUpload: True
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic root=UUID=c028b5f0-4b8a-4b17-9340-fdc9cd48a278 ro quiet splash
ProcEnviron:
 SHELL=/bin/false
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=de_DE:en
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f5e138c0f6f <g_slice_alloc+223>: mov (%rbx),%rax
 PC (0x7f5e138c0f6f) ok
 source "(%rbx)" (0x74617000656d616e) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: telepathy-mission-control-5
StacktraceTop:
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slist_prepend () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_object_class_install_property () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
 g_type_class_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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