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

[easezhi lee]

os:ubuntu kylin
this occured right after I upgrade 15.10 to 16.04

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1 [modified: usr/share/unity-control-center/searchingthedashlegalnotice.html usr/share/unity-control-center/ui/UbuntuLogo.png]
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Wed Mar 23 11:45:01 2016
ExecutablePath: /usr/bin/unity-control-center
InstallationDate: Installed on 2015-12-10 (104 days ago)
InstallationMedia: Ubuntu-Kylin 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: unity-control-center --overview
ProcEnviron:
 PATH=(custom, user)
 SHELL=/bin/bash
 LANG=zh_CN.UTF-8
 LANGUAGE=zh_CN:
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f53bcc4c4f7 <FcitxConfigFree+39>: mov (%rax),%rax
 PC (0x7f53bcc4c4f7) ok
 source "(%rax)" (0x6574736e69207374) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown 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: Upgraded to xenial on 2016-03-23 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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.