empathy crashed with SIGSEGV

[YannUbuntu]

Binary package hint: empathy

Crash when testing Muji : Muji was blocked on "Pending receiver" state, and I tried to quit Muji.
There Empathy crashed.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: empathy 2.30.1.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
CheckboxSubmission: 7bf4676ac92338d1d362954586c33b04
CheckboxSystem: bd9978d0ff03d4f55482fc24a6cdac35
CrashCounter: 1
Date: Sun Jun 27 23:29:44 2010
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100328)
ProcCmdline: /usr/bin/empathy -h
ProcEnviron:
 SHELL=/bin/bash
 LANG=fr_FR.utf8
SegvAnalysis:
 Segfault happened at: 0x8072944: mov 0x8(%esi),%eax
 PC (0x08072944) ok
 source "0x8(%esi)" (0x4a8d2a7c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: empathy
Stacktrace:
 #0 0x08072944 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbf988c4c
StacktraceTop: ?? ()
Title: empathy crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare src

[Apport retracing service (apport)]

Stacktrace:
 #0 0x08072944 in event_remove (event=0xbd70980)
     at empathy-event-manager.c:174
  priv = (EmpathyEventManagerPriv *) 0x4a8d2a74
  __PRETTY_FUNCTION__ = "event_remove"
 Cannot access memory at address 0xbf988c4c
StacktraceTop: event_remove (event=0xbd70980)
ThreadStacktrace:

[Brian Curtis (bcurtiswx)]

Thanks for your bug report and helping to make Ubuntu better. There are newer version of empathy available. Could you please update empathy and see if this is still an issue?

[Omer Akram (om26er)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!