gnome-control-center crashed with SIGSEGV in goa_oauth_provider_get_callback_uri()

[mastaiza]

гавно

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.1.92-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Fri Sep 23 00:58:44 2011
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
ProcCmdline: gnome-control-center online-accounts
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
SegvAnalysis:
 Segfault happened at: 0x1e81f78d <goa_oauth_provider_get_callback_uri+45>: cmp %eax,(%edi)
 PC (0x1e81f78d) ok
 source "%eax" ok
 destination "(%edi)" (0x4a39c381) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 goa_oauth_provider_get_callback_uri () from /usr/lib/libgoa-backend-1.0.so.0
 ?? () from /usr/lib/libgoa-backend-1.0.so.0
 webkit_marshal_BOOLEAN__OBJECT_OBJECT_OBJECT_OBJECT () from /usr/lib/libwebkitgtk-3.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in goa_oauth_provider_get_callback_uri()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
usr_lib_gnome-control-center:
 deja-dup 19.92-0ubuntu1
 gnome-bluetooth 3.1.4-0ubuntu2
 indicator-datetime 0.2.95-0ubuntu1

[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 #844205, 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.