unity-control-center crashed with SIGSEGV in FcitxConfigFree()

[Buzzing Robot]

Clean and updated install of 13 March 15.04 daily. Adjusting settings in the control center. Had just clicked "All Settings" to back out of "Text Entry".

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: unity-control-center 15.04.0+15.04.20150313-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Mar 13 17:17:50 2015
ExecutablePath: /usr/bin/unity-control-center
InstallationDate: Installed on 2015-03-13 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150313)
ProcCmdline: unity-control-center
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f7269af5767 <FcitxConfigFree+39>: mov (%rax),%rax
 PC (0x7f7269af5767) ok
 source "(%rax)" (0x00000190) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-control-center
StacktraceTop:
 FcitxConfigFree () from /usr/lib/x86_64-linux-gnu/libfcitx-config.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libregion.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libregion.so
Title: unity-control-center crashed with SIGSEGV in FcitxConfigFree()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_unity-control-center: deja-dup 32.0-0ubuntu5

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