empathy crashed with SIGSEGV in empathy_tp_chat_provide_password_async()

[James Cape]

Binary package hint: empathy

Crashed while attempting to login to an password-protected xmpp conference.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: empathy 2.31.92-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.32-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
CrashCounter: 1
Date: Sat Sep 18 18:47:08 2010
ExecutablePath: /usr/bin/empathy
ProcCmdline: empathy
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x80f1fdd <empathy_tp_chat_provide_password_async+29>: mov 0xc(%esi),%edi
 PC (0x080f1fdd) ok
 source "0xc(%esi)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 empathy_tp_chat_provide_password_async ()
 ?? ()
 g_cclosure_marshal_VOID(int0_t) () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: empathy crashed with SIGSEGV in empathy_tp_chat_provide_password_async()
UserGroups: adm admin cdrom dialout list lpadmin plugdev sambashare users video

[Apport retracing service (apport)]

StacktraceTop:
 empathy_tp_chat_provide_password_async (self=0x0,
 password_infobar_response_cb (info_bar=0x9249228,
 g_cclosure_marshal_VOID () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0

[Omer Akram (om26er)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem

[Omer Akram (om26er)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

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