gnome-software crashed with signal 5 in g_main_context_new()

[Brian]

Sorry, it is really hard to tell if this is a duplicate or not. The one I found that is almost exact match is marked expired, so I guess it is better to add info than to not under poor assumption.

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

$ apt-cache policy gnome-software
gnome-software:
  Installed: 3.28.0-0ubuntu7
  Candidate: 3.28.0-0ubuntu7
  Version table:
 *** 3.28.0-0ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.0-0ubuntu7
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: MATE
Date: Sat Apr 7 04:31:53 2018
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2018-03-05 (32 days ago)
InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba N/A
 gnome-software-plugin-snap 3.28.0-0ubuntu7
ProcCmdline: /usr/bin/gnome-software --gapplication-service
Signal: 5
SourcePackage: gnome-software
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
 snapd_client_find_section_sync () from /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_snap.so
Title: gnome-software crashed with signal 5 in g_main_context_new()
UpgradeStatus: Upgraded to bionic on 2018-03-13 (25 days ago)
UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape video

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