empathy crashed with SIGSEGV in g_type_check_instance_cast()

[Andreas Moog]

Binary package hint: empathy

Upon first starting empathy, I entered my Jabber account details, checked the box to add another account, clicked forward and got this crash.

ProblemType: Crash
Architecture: i386
Date: Wed Jan 13 14:03:42 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: nvidia
Package: empathy 2.29.4-1ubuntu1
ProcCmdline: empathy
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
SegvAnalysis:
 Segfault happened at: 0x8fee19 <g_type_check_instance_cast+41>: mov (%eax),%edi
 PC (0x008fee19) ok
 source "(%eax)" (0x0000001d) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 g_type_check_instance_cast ()
 ?? ()
 g_simple_async_result_complete ()
 ?? () from /usr/lib/libgio-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
Tags: lucid
Title: empathy crashed with SIGSEGV in g_type_check_instance_cast()
Uname: Linux 2.6.32-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 g_type_check_instance_cast ()
 account_manager_ready_cb (source_object=0x94a2118,
 g_simple_async_result_complete ()
 ?? () from /usr/lib/libgio-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0

[Omer Akram (om26er)]

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

[Vish (vish)]

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!