empathy crashed with SIGSEGV in g_slice_alloc()

[saksmlz]

Binary package hint: empathy

it сrashes when i try to close contacts window

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: empathy 2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelModules: nvidia wl
Architecture: i386
CrashCounter: 1
Date: Thu Sep 30 10:14:00 2010
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: empathy
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x6e62226 <g_slice_alloc+262>: mov (%edx),%ecx
 PC (0x06e62226) ok
 source "(%edx)" (0xffffffff) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 g_slice_alloc () from /lib/libglib-2.0.so.0
 g_slice_alloc0 () from /lib/libglib-2.0.so.0
 g_type_create_instance () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libtelepathy-glib.so.0
Title: empathy crashed with SIGSEGV in g_slice_alloc()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 g_slice_alloc () from /lib/libglib-2.0.so.0
 g_slice_alloc0 () from /lib/libglib-2.0.so.0
 g_type_create_instance () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 tp_proxy_constructor (type=142143928, n_params=9,

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file 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!

[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