Running in GNOME 3 with Shell on Quantal, telepathy-mission-control-5 package at 1:5.12.0-0ubuntu5. It fairly reliably crashes when I login to my system, and often when restarting empathy.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: telepathy-mission-control-5 1:5.12.0-0ubuntu5
ProcVersionSignature: Ubuntu 3.5.0-1.1-generic 3.5.0-rc3
Uname: Linux 3.5.0-1-generic x86_64
ApportVersion: 2.2.5-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sat Jun 23 13:30:35 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120606.2)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.5.0-1-generic root=UUID=8e3bb135-1892-48c8-a763-68e22c48593d ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: telepathy-mission-control-5
StacktraceTop:
raise () from /lib/x86_64-linux-gnu/libc.so.6
abort () from /lib/x86_64-linux-gnu/libc.so.6
?? () from /lib/x86_64-linux-gnu/libc.so.6
?? () from /lib/x86_64-linux-gnu/libc.so.6
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
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
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 #984556, 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.