empathy crashed with SIGSEGV in gtk_tree_model_get_valist()

[Franz]

Installing wine

ProblemType: Crash
Architecture: amd64
Date: Thu Oct 15 23:17:30 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/empathy
NonfreeKernelModules: fglrx
Package: empathy 2.28.0.1-1ubuntu6
ProcCmdline: empathy
ProcEnviron:
 LANG=hr_HR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.47-generic
SegvAnalysis:
 Segfault happened at: 0x7f179caec495 <gtk_tree_model_get_valist+245>: mov 0x30(%rax),%rdx
 PC (0x7f179caec495) ok
 source "0x30(%rax)" (0x00000030) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 gtk_tree_model_get_valist ()
 gtk_tree_model_get ()
 ?? () from /usr/lib/libempathy-gtk.so.28
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: empathy crashed with SIGSEGV in gtk_tree_model_get_valist()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:IA__gtk_tree_model_get_valist (
IA__gtk_tree_model_get (tree_model=0x7fffa534ee20,
account_widget_irc_button_remove_clicked_cb (
g_closure_invoke ()
?? () from /usr/lib/libgobject-2.0.so.0

[Brian Curtis (bcurtiswx)]

Thanks for your bug report and helping to make Ubuntu better. All traces look OK, marked as public. Would you please update empathy to 2.28.1ubuntu1 to see if this is still a 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!

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