Empathy crashed with SIGSEGV in g_closure_invoke() when receiving a file through a jabber connection

[kernel_script]

Binary package hint: empathy

Empathy crashed with SIGSEGV in g_closure_invoke() when receiving a file through a jabber connection.

OS: Ubuntu Karmic Koala 9.10 RC, i386

My Ubuntu is freshly installed and updated.

ProblemType: Crash
Architecture: i386
Date: Fri Oct 23 15:31:54 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
NonfreeKernelModules: nvidia
Package: empathy 2.28.1-1ubuntu1
ProcCmdline: empathy
ProcEnviron:
 LANGUAGE=pt_BR.UTF-8
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Title: empathy crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
SegvAnalysis:
 Segfault happened at: 0x806e5a5: jmp *%edx
 PC (0x0806e5a5) ok
 source "*%edx" (0x08c8d5b0) ok
 SP (0xbfdcbc7c) ok
 Reason could not be automatically determined.
SegvReason: Reason could not be automatically determined.

[Apport retracing service (apport)]

StacktraceTop:empathy_event_activate (event_public=0x8c68800)
g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
?? () from /usr/lib/libgobject-2.0.so.0
g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
g_signal_emit () from /usr/lib/libgobject-2.0.so.0

[Sebastien Bacher (seb128)]

the crash is due to the libindicate changes

[Ken VanDine (ken-vandine)]

Thank you for your bug report, could you try if that's still an issue with current lucid updates?

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