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

[Mihai Moldovan]

The error apears at log on

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: telepathy-mission-control-5 1:5.9.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic i686
NonfreeKernelModules: fglrx
ApportVersion: 1.22.1-0ubuntu2
Architecture: i386
Date: Fri Sep 9 19:50:42 2011
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic root=UUID=e9c6237b-6fc8-46bc-84bd-d6282f9f87b8 ro quiet splash vt.handoff=7
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: telepathy-mission-control-5
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: mission-control-5 crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: Upgraded to oneiric on 2011-09-09 (0 days ago)
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 #835672, 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.