mission-control-5 crashed with SIGSEGV

Bug #443281 reported by Armin Borumand
This bug affects 28 people
Affects Status Importance Assigned to Milestone
telepathy-mission-control-5 (Ubuntu)

Bug Description

Binary package hint: telepathy-mission-control-5

When apply account... (random)

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Mon Oct 5 20:24:37 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/telepathy/mission-control-5
NonfreeKernelModules: wl
Package: telepathy-mission-control-5 5.3.1-1
ProcCmdline: /usr/lib/telepathy/mission-control-5
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
 Segfault happened at: 0x421c54: mov 0x8(%rdi),%r8
 PC (0x00421c54) ok
 source "0x8(%rdi)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%r8" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-mission-control-5
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: mission-control-5 crashed with SIGSEGV
Uname: Linux 2.6.31-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Armin Borumand (armin390) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:mc_param_type (param=0x0) at mcd-account.c:2009
get_parameter (account=0x1446280,
set_parameters_set_single (
set_parameters_iter_param (
set_parameters_iter_param (

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in telepathy-mission-control-5 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
cement_head (andorjkiss) wrote :

Just now, in Lucid, getting this crash coming up.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in telepathy-mission-control-5 (Ubuntu):
status: New → Confirmed
Revision history for this message
Phil Corbett (chubble-10) wrote :

This affects 12.04 beta2 as well.

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.