gnome-control-center crashed with SIGABRT in __kernel_vsyscall()

[Victor Vargas]

Steps to reproduce this issue:

1) Open online-accounts in control center
2) Try to add a google account, fill the fields and then click on "Grant this application"
3) After a couple of seconds control-center will crash.

However, if you come back to online accounts you will see your account already configured.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.1.4-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
Uname: Linux 3.0.0-7-generic i686
Architecture: i386
Date: Mon Aug 1 12:19:25 2011
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110727)
ProcCmdline: gnome-control-center
Signal: 6
SourcePackage: gnome-control-center
StacktraceTop:
 __kernel_vsyscall ()
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 g_assertion_message (domain=0x20801bf2 "GoaBackend", file=0x20802a25 "goaoauthprovider.c", line=1015, func=0x20802ffc "goa_oauth_provider_add_account", message=<value optimized out>) at /build/buildd/glib2.0-2.29.14/./glib/gtestutils.c:1425
 g_assertion_message_expr (domain=0x20801bf2 "GoaBackend", file=0x20802a25 "goaoauthprovider.c", line=1015, func=0x20802ffc "goa_oauth_provider_add_account", expr=0x20802ac8 "ret == NULL") at /build/buildd/glib2.0-2.29.14/./glib/gtestutils.c:1436
Title: gnome-control-center crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: No upgrade log present (probably fresh install)
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 #810684, 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.