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

[Cristian Aravena Romero]

Open empathy and crash.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: empathy 3.1.4-1ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
Uname: Linux 3.0.0-7-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sun Jul 31 09:45:05 2011
ExecutablePath: /usr/lib/empathy/empathy-auth-client
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1)
ProcCmdline: /usr/lib/empathy/empathy-auth-client
ProcEnviron:
 SHELL=/bin/bash
 LANG=es_CL.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f95e60a6ee4 <g_main_context_query+116>: cmp %ebp,0x18(%rax)
 PC (0x7f95e60a6ee4) ok
 source "%ebp" ok
 destination "0x18(%rax)" (0x00000019) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 g_main_context_query (context=0xba0e10, max_priority=2147483647, timeout=0x7fffdecd08fc, fds=<value optimized out>, n_fds=5) at /build/buildd/glib2.0-2.29.14/./glib/gmain.c:2893
 g_main_context_iterate (context=0xba0e10, block=1, dispatch=1, self=<value optimized out>) at /build/buildd/glib2.0-2.29.14/./glib/gmain.c:3143
 g_main_loop_run (loop=0xc3fc50) at /build/buildd/glib2.0-2.29.14/./glib/gmain.c:3369
 gtk_main () at /build/buildd/gtk+3.0-3.1.10/./gtk/gtkmain.c:1367
 main (argc=1, argv=0x7fffdecd0a98) at empathy-auth-client.c:307
Title: empathy-auth-client crashed with SIGSEGV in g_main_context_query()
UpgradeStatus: Upgraded to oneiric on 2011-07-30 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #797962, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.