gnome-control-center crashed with SIGSEGV

[Steve Paynter]

Desktop icons had disappeared. Was scanning dock looking for "files" (on primary display) when error box popped up. Have 2nd display active via HDMI. Found desktop icons on 2nd even though selection was for prime to be 1st display. 1st=Acer Aspire 5742 2nd=LG Flatron W2242TQ

~$ lsb_release -rd
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
Last updated 10 April 2018 late afternoon.
~$ apt-cache policy pkgname
N: Unable to locate package pkgname

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.0-0ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 11 00:01:25 2018
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2018-01-25 (76 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180121)
ProcCmdline: gnome-control-center --overview
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x55d2ba514311: mov 0x90(%rbp),%rsi
 PC (0x55d2ba514311) ok
 source "0x90(%rbp)" (0x00000090) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ()
 ()
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV
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 #1754924, 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.