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

Bug #979205 reported by Daniel O'Connor
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-mission-control-5 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Failed facebook jabber account authentication appeared to trigger this?

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 i686
ApportVersion: 2.0.1-0ubuntu1
Architecture: i386
CheckboxSubmission: d90366243e5f9fdf1e4af6d249269ab0
CheckboxSystem: fc73f07fcd9845bb95fa3ca6b8be7ef2
CrashCounter: 1
Date: Thu Apr 12 03:49:21 2012
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic root=UUID=63731535-29fc-415b-9b97-cf435280884f ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7000ac: mov 0x4(%esi),%eax
 PC (0x007000ac) ok
 source "0x4(%esi)" (0x5f646371) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: telepathy-mission-control-5
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 realloc () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: mission-control-5 crashed with SIGSEGV in realloc()
UpgradeStatus: Upgraded to precise on 2012-04-11 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Daniel O'Connor (daniel-oconnor) 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 #978046, 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.