gnome-software crashed with SIGSEGV in g_type_check_instance() while trying to install the discord app from snapcraft.io

[Neil Oosthuizen]

Click on the link for installing discord app. Opens in Gnome-software. Clicked on install, Gnome-software closed and crash message came.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.27.92-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Sat Mar 10 12:10:17 2018
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2018-03-10 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba N/A
 gnome-software-plugin-snap 3.27.92-0ubuntu2
ProcCmdline: /usr/bin/gnome-software --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7fa1217a017d <g_type_check_instance+13>: mov (%rdi),%rax
 PC (0x7fa1217a017d) ok
 source "(%rdi)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-software
StacktraceTop:
 g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_handlers_disconnect_matched () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gnome-software crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Neil Oosthuizen (nlsthzn)]

I initially installed discord from the deb file, got a lot of font artifacting. Removed and then tried to install the snap package.

[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 #1752645, 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.