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

[ariel sandoval]

gracias por todas las ayudas oportunas muy bien felicitaciones

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: telepathy-mission-control-5 1:5.14.1-1ubuntu5
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
Uname: Linux 3.11.0-8-generic x86_64
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 21 19:32:48 2013
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationDate: Installed on 2013-05-30 (114 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.0-8-generic root=UUID=fa0c3a7c-e5f4-47da-b196-99197deaefd1 ro nopat vesafb.invalid=1 plymouth:debug drm.debug=0xe
ProcEnviron:
 SHELL=/bin/false
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=es_CO:es
 LANG=es_CO.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f5f3f9dbad7 <g_slice_alloc+167>: mov (%rbx),%rax
 PC (0x7f5f3f9dbad7) ok
 source "(%rbx)" (0x00010000) 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
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
SystemImageInfo: Error: [Errno 2] No existe el archivo o el directorio: 'system-image-cli'
Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: Upgraded to saucy on 2013-06-03 (110 days ago)
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 #1154674, 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.