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

Bug #572737 reported by Cristian Aravena Romero on 2010-05-01
42
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Telepathy Mission Control 5
Confirmed
Medium
telepathy-mission-control-5 (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: telepathy-mission-control-5

I use empathy and open apport

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: telepathy-mission-control-5 5.3.2-3
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Fri Apr 30 21:41:49 2010
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
ProcCmdline: /usr/lib/telepathy/mission-control-5
ProcEnviron:
 SHELL=/bin/bash
 LANG=es_CL.utf8
SegvAnalysis:
 Segfault happened at: 0x80795f2: mov (%ebx),%esi
 PC (0x080795f2) ok
 source "(%ebx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-mission-control-5
StacktraceTop:
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: mission-control-5 crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Binary package hint: telepathy-mission-control-5

I use empathy and oppen apport

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: telepathy-mission-control-5 5.3.2-3
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Fri Apr 30 21:41:49 2010
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
ProcCmdline: /usr/lib/telepathy/mission-control-5
ProcEnviron:
 SHELL=/bin/bash
 LANG=es_CL.utf8
SegvAnalysis:
 Segfault happened at: 0x80795f2: mov (%ebx),%esi
 PC (0x080795f2) ok
 source "(%ebx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-mission-control-5
StacktraceTop:
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: mission-control-5 crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

StacktraceTop:
 _mcd_build_error_string (error=0x0) at mcd-misc.c:70
 mcd_dispatch_operation_channel_aborted_cb (
 IA__g_cclosure_marshal_VOID__VOID (closure=0x9cc8ef8,
 IA__g_closure_invoke (closure=0x9cc8ef8, return_value=0x0,
 signal_emit_unlocked_R (node=<value optimized out>,

Changed in telepathy-mission-control-5 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Omer Akram (om26er) wrote :

Thanks for sending this upstream

Changed in telepathy-mission-control-5 (Ubuntu):
status: New → Triaged
description: updated
Andrea Amoroso (heiko81) wrote :

the same error in Maverick..

Gabriel Mazetto (brodock) wrote :

Happening on maverick... i can confirm too

Changed in mission-control-5:
importance: Unknown → Medium
status: Unknown → Confirmed
Changed in mission-control-5:
importance: Medium → Unknown
Changed in mission-control-5:
importance: Unknown → Medium

Is this reproducible? If so, how?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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