empathy crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

[Michael Lazarev]

Binary package hint: empathy

Looks like something as bug 441848, but happened today.
As you can see, I used updated packages.
What I tried to do is simultaneously opening four chats: two on jabber, and two on IRC.
When I opened the last chat on IRC, it didn't manage to open a new tab, started showing me notification bubbles, and then crashed.

ProblemType: Crash
Architecture: i386
Date: Fri Oct 30 20:27:25 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/empathy
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
Package: empathy 2.28.1.1-0ubuntu1
ProcCmdline: empathy
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x806e67d: mov 0xc(%eax),%esi
 PC (0x0806e67d) 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__VOID ()
 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
Title: empathy crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Brian Curtis (bcurtiswx)]

Thanks for your bug report and helping to make Ubuntu better. Could you please obtain a backtrace by using the information in https://wiki.ubuntu.com/Backtrace.

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