Ubuntu
empathy package

empathy crashed with SIGSEGV in g_closure_invoke()

Bug #747699 reported by Miguelángel León on 2011-04-01

This bug report is a duplicate of: Bug #748535: empathy crashed with SIGSEGV in event_manager_add. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	empathy (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: empathy

it just crashed without any obvious trigger

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: empathy 2.34.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
Date: Fri Apr 1 14:48:24 2011
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
ProcCmdline: empathy
ProcEnviron:
SHELL=/bin/bash
LANGUAGE=es_VE:es:en
LANG=es_VE.UTF-8
SegvAnalysis:
Segfault happened at: 0x43ef2d: mov 0x28(%r12),%rax
PC (0x0043ef2d) ok
source "0x28(%r12)" (0x00000028) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
?? ()
?? ()
g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: empathy crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to natty on 2011-03-21 (10 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Miguelángel León (migueleonm) wrote on 2011-04-01:

XsessionErrors.txt Edit (16.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-04-04: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #748608, 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.