gnome-software crashed with SIGSEGV in g_param_spec_pool_lookup()

[John Belton]

Attempting to open the SOFTWARE package it crashed without opening and generated an error report. Other packages seem OK.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-software 3.25.91-1ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic i686
ApportVersion: 2.20.6-0ubuntu7
Architecture: i386
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 26 11:48:36 2017
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2017-08-08 (17 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170807)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba N/A
 gnome-software-plugin-snap 3.25.91-1ubuntu1
ProcCmdline: /usr/bin/gnome-software --gapplication-service
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb64f08e6 <__strchr_sse2_bsf+38>: movdqa (%edi),%xmm0
 PC (0xb64f08e6) ok
 source "(%edi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-software
StacktraceTop:
 g_param_spec_pool_lookup () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? ()
 gs_shell_change_mode ()
Title: gnome-software crashed with SIGSEGV in g_param_spec_pool_lookup()
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 #1708998, 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.