empathy crashed with SIGSEGV

[jage]

Binary package hint: empathy

Rebooting after updates, ran sudo dpkg-reconfigure console-setup got error before exiting.

ProblemType: Crash
Architecture: i386
Date: Thu Feb 11 22:17:20 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100127)
Package: empathy 2.29.90-0ubuntu2
ProcCmdline: empathy
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
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
Stacktrace:
 #0 0x080dea3a in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfc9e8cc
StacktraceTop: ?? ()
Title: empathy crashed with SIGSEGV
Uname: Linux 2.6.32-13-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1468): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (bluetooth-applet:1469): Gtk-CRITICAL **: gtk_action_set_sensitive: assertion `GTK_IS_ACTION (action)' failed
 (gnome-terminal:1772): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed

[Apport retracing service (apport)]

Stacktrace:
 #0 empathy_tp_chat_acknowledge_messages (chat=Cannot access memory at address 0xbfc9e8d0
 ) at empathy-tp-chat.c:1676
  msgs = (GSList *) Cannot access memory at address 0xbfc9e88c
StacktraceTop: empathy_tp_chat_acknowledge_messages (chat=Cannot access memory at address 0xbfc9e8d0

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