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

Bug #979419 reported by Shaun Burch
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-mission-control-5 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Description: Ubuntu precise (development branch)
Release: 12.04

telepathy-mission-control-5:
  Installed: 1:5.12.0-0ubuntu2
  Candidate: 1:5.12.0-0ubuntu2
  Version table:
 *** 1:5.12.0-0ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-mission-control-5 1:5.12.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
ApportVersion: 2.0.1-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Wed Apr 11 17:33:54 2012
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic-pae root=UUID=fa878bda-065f-4314-bf31-0ea94df097f2 ro i915.powersave=0 acpi_backlight=vendor vga=792 quiet splash vt.handoff=7
Signal: 6
SourcePackage: telepathy-mission-control-5
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: mission-control-5 crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-04-05 (5 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
Shaun Burch (shazbot) wrote :
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 #974687, 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.

visibility: private → public
visibility: private → public
tags: removed: need-i386-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.