empathy crashed with SIGSEGV in empathy_dispatcher_chat_with_contact()

[Matt Zimmerman]

Binary package hint: empathy

I noticed that my Google Talk account wasn't working, so I deleted it and re-created it (I noticed along the way that I had forgotten to add @gmail.com to my username). It started working, and I double-clicked one of my Google Talk contacts immediately to start a conversation. Empathy then crashed.

After reopening it, I was able to start a conversation with the same contact without a problem.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: empathy 2.30.0.1-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-20.30-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-20-generic i686
Architecture: i386
Date: Thu Apr 15 14:46:21 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Alpha i386 (20100315)
ProcCmdline: empathy
ProcEnviron:
 SHELL=/bin/zsh
 PATH=(custom, user)
 LANG=en_GB.utf8
SegvAnalysis:
 Segfault happened at: 0x80d1117: mov 0x8(%esi),%eax
 PC (0x080d1117) ok
 source "0x8(%esi)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: empathy crashed with SIGSEGV in g_closure_invoke()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 empathy_dispatcher_chat_with_contact (contact=0x92b80d0,
 contact_list_view_row_activated (view=0x920e108,
 _gtk_marshal_VOID__BOXED_OBJECT (closure=0x90ec878,
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0

[Brian Curtis (bcurtiswx)]

Thanks for your bug report and helping to make Ubuntu better. Please update empathy to the most recent version and please let us know if this is still an issue for you.

[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!