empathy-accounts crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

[Gary M]

Binary package hint: empathy

While CPU was busy, ran "Chat Accounts" from the "me menu". The Accounts windows was slow to be populated, and I closed it. This error was then shown.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: empathy 2.33.1-0ubuntu3
Uname: Linux 2.6.38-020638rc5-generic i686
Architecture: i386
Date: Thu Feb 17 03:07:53 2011
ExecutablePath: /usr/bin/empathy-accounts
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202.1)
ProcCmdline: empathy-accounts
ProcEnviron:
 SHELL=/bin/bash
 LC_MESSAGES=en_NZ.utf8
 LANGUAGE=en_NZ:en
 LANG=en_NZ.UTF-8
SegvAnalysis:
 Segfault happened at: 0x80856ea: mov (%esi),%eax
 PC (0x080856ea) ok
 source "(%esi)" (0x0000dc63) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0
 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-accounts crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (nautilus:1263): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (gnome-power-manager:1270): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private->update_and_descendants_freeze_count > 0' failed

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

[Ian Ross (iankross)]

empathy trying to hookup to hotmail (MSN) account

[Pedro Villavicencio (pedro)]

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