empathy crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM()

[Spyros Kavvadias]

Binary package hint: empathy

Hello,

Empathy crashed when tried to use video call with MSN contact.

Regards

ProblemType: Crash
Architecture: i386
Date: Thu Jan 21 01:37:39 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
Package: empathy 2.29.5.1-1ubuntu2
ProcCmdline: empathy
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-11.15-generic-pae
SegvAnalysis:
 Segfault happened at: 0x807b4dd: mov 0xc(%eax),%esi
 PC (0x0807b4dd) ok
 source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__PARAM ()
 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 g_cclosure_marshal_VOID__PARAM()
Uname: Linux 2.6.32-11-generic-pae i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 event_manager_media_channel_got_contact (approval=0x86eec78)
 event_manager_media_channel_contact_changed_cb (
 g_cclosure_marshal_VOID__PARAM ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0

[Omer Akram (om26er)]

thanks for the bug report. is this still an issue?

[Vish (vish)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. If this is still an issue, 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 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!