empathy-auth-client crashed with SIGSEGV in g_slice_alloc()

[userdce]

empathy-auth-client

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: empathy 3.1.3-1ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
Uname: Linux 3.0.0-5-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
CrashCounter: 1
Date: Thu Jul 21 11:01:14 2011
ExecutablePath: /usr/lib/empathy/empathy-auth-client
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110716)
ProcCmdline: /usr/lib/empathy/empathy-auth-client
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f6d67900105 <g_slice_alloc+293>: mov (%rbx),%rdx
 PC (0x7f6d67900105) ok
 source "(%rbx)" (0x1000000000) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_list_prepend () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: empathy-auth-client crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin mythtv netdev plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 magazine_chain_pop_head (mem_size=24) at /build/buildd/glib2.0-2.29.10/./glib/gslice.c:492
 thread_memory_magazine1_alloc (mem_size=24) at /build/buildd/glib2.0-2.29.10/./glib/gslice.c:795
 g_slice_alloc (mem_size=24) at /build/buildd/glib2.0-2.29.10/./glib/gslice.c:833
 g_list_prepend (list=0xb1e620, data=0xabddc0) at /build/buildd/glib2.0-2.29.10/./glib/glist.c:309
 g_object_newv (object_type=11461280, n_parameters=4, parameters=0xb27590) at /build/buildd/glib2.0-2.29.10/./gobject/gobject.c:1401

[Victor Vargas (kamus)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.

This will help us to find and resolve the problem.