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

[Krzysztof Lisowski]

I'd modified personal setting and closed the window when it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-control-center 15.04.0+16.04.20160216-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
Uname: Linux 4.4.0-9-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Mar 3 21:11:54 2016
ExecutablePath: /usr/bin/unity-control-center
InstallationDate: Installed on 2016-03-03 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160303)
ProcCmdline: unity-control-center --overview
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/bash
 LANG=pl_PL.UTF-8
 LANGUAGE=pl
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7fb04b7a4d99 <g_type_check_instance+25>: mov (%rax),%rdi
 PC (0x7fb04b7a4d99) ok
 source "(%rax)" (0x2c0000005000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity-control-center
StacktraceTop:
 g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: unity-control-center crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: No upgrade log present (probably fresh install)
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 #1375073, 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.