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

[winux]

I've been disconnected from the control center without notification.
Incidently I was on "Universal access" and wanted to move to the next item

ubuntu@ubuntu:~$ lsb_release -rd
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04

ubuntu@ubuntu:~$ apt-cache policy pkgname
N: Unable to locate package pkgname

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu1
Architecture: amd64
CasperVersion: 1.391
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 28 20:03:54 2018
ExecutablePath: /usr/bin/gnome-control-center
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
ProcCmdline: gnome-control-center wifi
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x5614a93e76f5: cmpb $0x0,(%rbx)
 PC (0x5614a93e76f5) ok
 source "$0x0" ok
 destination "(%rbx)" (0x40000002) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () 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
Title: gnome-control-center crashed with SIGSEGV in g_closure_invoke()
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 #1723249, 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.