empathy crashed with SIGSEGV in g_closure_invoke()

[Ian Corne]

Binary package hint: empathy

Crashed after I signed in with another client and tried to close a windows of a conversation (msn)

It did not try to relogin.

Reporting new bug because I'm fully up to date and the other bugs have status fix released.

Ian

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Feb 21 21:01:44 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/empathy
NonfreeKernelModules: nvidia
Package: empathy 2.29.90-0ubuntu2
ProcCmdline: empathy
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
SegvAnalysis:
 Segfault happened at: 0x80dea3a: mov 0xc(%eax),%eax
 PC (0x080dea3a) ok
 source "0xc(%eax)" (0x0000000c) 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
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: empathy crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.32-13-generic i686
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare scanner tape vboxusers video

[Apport retracing service (apport)]

StacktraceTop:
 empathy_tp_chat_acknowledge_messages (chat=0x0, messages=0x0)
 empathy_chat_messages_read (self=0x9177040)
 chat_window_page_removed_cb (notebook=0x917c830,
 _gtk_marshal_VOID__OBJECT_UINT (closure=0x917e4f0,
 g_closure_invoke () 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!