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

Bug #977052 reported by Fran Diéguez
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-mission-control-5 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Raised this error after resume from suspend.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-mission-control-5 1:5.12.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
Date: Mon Apr 9 05:42:48 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120408)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic root=UUID=f755d13d-6540-4aff-bff6-78eb93b26ce0 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: telepathy-mission-control-5
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

Revision history for this message
Fran Diéguez (frandieguez) wrote :
visibility: private → public
description: updated
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #975100, 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.

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.