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

Bug #1018053 reported by Angel Guzman Maeso
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-mission-control-5 (Ubuntu)
New
Medium
Unassigned

Bug Description

Maybe dupe of #585952 reporting just in case (the trace could be more useful).

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 i686
ApportVersion: 2.2.5-0ubuntu1
Architecture: i386
Date: Tue Jun 26 20:16:08 2012
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationMedia:

ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.5.0-1-generic root=UUID=793921c9-c002-4400-9dd5-e0879b4061fb ro quiet splash vt.handoff=7
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
SegvAnalysis:
 Segfault happened at: 0x808220d: mov 0xc(%edx),%ecx
 PC (0x0808220d) ok
 source "0xc(%edx)" (0xaaaaaab6) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: telepathy-mission-control-5
Title: mission-control-5 crashed with SIGSEGV in g_cclosure_marshal_VOID__INT()
UpgradeStatus: Upgraded to quantal on 2012-06-05 (21 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape vboxusers video

Revision history for this message
Angel Guzman Maeso (shakaran) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceTop.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in telepathy-mission-control-5 (Ubuntu):
importance: Undecided → Medium
summary: - mission-control-5 crashed with SIGSEGV in g_cclosure_marshal_VOID__INT()
+ mission-control-5 crashed with SIGSEGV in copy_status()
tags: removed: need-i386-retrace
tags: removed: apparmor
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.