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

[Marta Vuelma]

This issue occur after a upgrade from 12.10 to 13.04 via software updater.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: empathy 3.6.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6
Uname: Linux 3.8.0-5-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Sat Feb 9 02:20:36 2013
ExecutablePath: /usr/lib/empathy/empathy-auth-client
InstallationDate: Installed on 2012-10-21 (111 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: /usr/lib/empathy/empathy-auth-client
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fc9f6d0339a <g_hash_table_iter_init+10>: mov 0x44(%rsi),%eax
 PC (0x7fc9f6d0339a) ok
 source "0x44(%rsi)" (0x100000044) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 g_hash_table_iter_init () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ag_auth_data_get_parameters () from /usr/lib/x86_64-linux-gnu/libaccounts-glib.so.0
 ag_auth_data_insert_parameters () from /usr/lib/x86_64-linux-gnu/libaccounts-glib.so.0
 ?? () from /usr/lib/empathy/libempathy-3.6.3.so
 ?? () from /usr/lib/empathy/libempathy-3.6.3.so
Title: empathy-auth-client crashed with SIGSEGV in g_hash_table_iter_init()
UpgradeStatus: Upgraded to raring on 2013-02-09 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1105240, 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.