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

[مالك ب]

This bug occurred during the installation of Telegram desktop from ubuntu software. The Telegram Desktop install was successful.
The following applications were in use:
Firefox, Libreoffice calc, gnome editor, konsole, system monitor.
lsb_release -rd:
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04

apt-cache policy
ملفات الحزم:
 100 /var/lib/dpkg/status
     release a=now
 500 http://archive.canonical.com/ubuntu bionic/partner i386 Packages
     release v=18.04,o=Canonical,a=bionic,n=bionic,l=Partner archive,c=partner,b=i386
     origin archive.canonical.com
 500 http://archive.canonical.com/ubuntu bionic/partner amd64 Packages
     release v=18.04,o=Canonical,a=bionic,n=bionic,l=Partner archive,c=partner,b=amd64
     origin archive.canonical.com
 500 http://dz.archive.ubuntu.com/ubuntu bionic/multiverse i386 Packages
     release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=multiverse,b=i386
     origin dz.archive.ubuntu.com
 500 http://dz.archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages
     release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=multiverse,b=amd64
     origin dz.archive.ubuntu.com
 500 http://dz.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
     release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=universe,b=i386
     origin dz.archive.ubuntu.com
 500 http://dz.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
     release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=universe,b=amd64
     origin dz.archive.ubuntu.com
 500 http://dz.archive.ubuntu.com/ubuntu bionic/restricted i386 Packages
     release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=restricted,b=i386
     origin dz.archive.ubuntu.com
 500 http://dz.archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages
     release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=restricted,b=amd64
     origin dz.archive.ubuntu.com
 500 http://dz.archive.ubuntu.com/ubuntu bionic/main i386 Packages
     release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=main,b=i386
     origin dz.archive.ubuntu.com
 500 http://dz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
     release v=18.04,o=Ubuntu,a=bionic,n=bionic,l=Ubuntu,c=main,b=amd64
     origin dz.archive.ubuntu.com
الحزم المُدبّسة:

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.27.92-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 18 17:46:33 2018
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2018-03-18 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317)
ProcCmdline: gnome-control-center background
ProcEnviron:
 LANGUAGE=ar_DZ:ar
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ar_DZ.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x5630a72075f1: mov 0x90(%rbp),%rsi
 PC (0x5630a72075f1) 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:
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
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.