gnome-software crashed with SIGSEGV in tcache_get()

[S Jones]

  was installing xscreensaver

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-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 5 11:45:48 2018
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2018-04-05 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
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
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc5edafd207 <__GI___libc_malloc+407>: mov (%rdx),%rdi
 PC (0x7fc5edafd207) ok
 source "(%rdx)" (0x6e6f662f6374652f) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-software
StacktraceTop:
 tcache_get (tc_idx=2) at malloc.c:2943
 __GI___libc_malloc (bytes=48) at malloc.c:3050
 () at /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
 FcStrSetAdd () at /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
 FcConfigParseAndLoad () at /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
Title: gnome-software crashed with SIGSEGV in tcache_get()
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 #1758844, 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.