empathy crashed with SIGSEGV in g_type_check_instance_cast()

[hexagram]

Binary package hint: empathy

going offline make crash empathy

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: empathy 2.33.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
Uname: Linux 2.6.38-1-generic i686
Architecture: i386
Date: Fri Feb 4 11:18:34 2011
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100310)
ProcCmdline: empathy
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 LC_MESSAGES=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x38269c <g_type_check_instance_cast+44>: mov (%ecx),%esi
 PC (0x0038269c) ok
 source "(%ecx)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libdbusmenu-gtk.so.3
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_datalist_id_set_data_full () from /lib/libglib-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: empathy crashed with SIGSEGV in g_type_check_instance_cast()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 g_type_check_instance_cast (type_instance=0x94e8d38,
 dbusmenu_cache_freed (data=0x94e8d38, obj=0x95f2140)
 weak_refs_notify (data=0x92f5a00)
 g_datalist_id_set_data_full (datalist=0x95f2148, key_id=55,
 ?? ()

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

[Lauri Siltala (latelol)]

Hi,
From what I gather, to give you that information I need to be able to reproduce the crash. But as I said in the original report, I have no idea whatsoever how to reproduce it (it has only occurred once) so I don't think I can help you with that.

[Lauri Siltala (latelol)]

Please disregard my former comment, I was looking at the wrong bug and wasn't supposed to comment on this one :)

[Omer Akram (om26er)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.