gnome-control-center.real crashed with SIGSEGV in gtk_stack_set_visible_child_name()

[Theo]

This bug occurred when I pressed the key on my keyboard that is bound to open gnome settings. The computer's fan turned on very loudly and gnome settings did not open.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: gnome-control-center 1:3.14.0-1ubuntu1~utopic1 [origin: LP-PPA-gnome3-team-gnome3-staging]
Uname: Linux 3.19.0-031900rc6-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Mar 22 09:33:08 2015
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center.real
InstallationDate: Installed on 2015-03-17 (5 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcCmdline: /usr/bin/gnome-control-center.real --overview
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fbf2f013fb7 <gtk_stack_set_visible_child_name+7>: mov 0x24(%rdi,%rax,1),%edx
 PC (0x7fbf2f013fb7) ok
 source "0x24(%rdi,%rax,1)" (0xfffffffffffffea4) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 gtk_stack_set_visible_child_name () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? ()
 ?? ()
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: gnome-control-center.real crashed with SIGSEGV in gtk_stack_set_visible_child_name()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_gnome-control-center: deja-dup 32.0-0ubuntu2~utopic1

[Ubuntu GNOME (ug-bot)]

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 #1433090, 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.