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

[mollymasta]

Binary package hint: telepathy-mission-control-5

I got this error

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: telepathy-mission-control-5 5.3.2-2
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-generic x86_64
NonfreeKernelModules: usbhid hid sky2 usb_storage floppy pata_atiixp ahci
Architecture: amd64
Date: Sat Apr 3 11:47:57 2010
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
ProcCmdline: /usr/lib/telepathy/mission-control-5
ProcEnviron:
 SHELL=/bin/bash
 LANG=nl_BE.utf8
SegvAnalysis:
 Segfault happened at: 0x431d36: mov (%rdi),%ebx
 PC (0x00431d36) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%ebx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-mission-control-5
StacktraceTop:
 ?? ()
 ?? ()
 g_closure_invoke ()
 g_signal_connect_data ()
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
Title: mission-control-5 crashed with SIGSEGV in g_closure_invoke()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #540561, 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.