gnome-software crashed with SIGSEGV in g_variant_builder_add_value()

[Alex GOOD HEARTS Organisation]

Tried to install ufw snap twice - same result: crash. Have no idea why. What can be a fix? Or should I use a different simple firewall for my ubuntu 17.10? Thanks

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-software 3.26.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 12 18:22:19 2017
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2017-10-06 (6 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171004)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba N/A
 gnome-software-plugin-snap 3.26.1-0ubuntu1
ProcCmdline: /usr/bin/gnome-software --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7f35a6d61a10: mov 0x20(%rdi),%eax
 PC (0x7f35a6d61a10) ok
 source "0x20(%rdi)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-software
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_builder_add_value () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_new_va () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-software crashed with SIGSEGV in g_variant_builder_add_value()
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 #1722964, 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.