gnome-software crashed with SIGSEGV in g_param_spec_pool_lookup()

[Ivan Ulyanov]

I've updated to 17.10 alpha and I understand that something wouldn't work. Anyway, I'm glad to help you as I can. The version of gnome-software is 3.25.91-1ubuntu1.

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
NonfreeKernelModules: wl
ApportVersion: 2.20.6-0ubuntu7
Architecture: i386
Date: Mon Aug 28 11:07:28 2017
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2017-07-22 (36 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba N/A
 gnome-software-plugin-snap 3.25.91-1ubuntu1
ProcCmdline: gnome-software
ProcEnviron:
 LANG=ru_RU.UTF-8
 TERM=xterm-256color
 PATH=(custom, no user)
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb643d8e6 <__strchr_sse2_bsf+38>: movdqa (%edi),%xmm0
 PC (0xb643d8e6) 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 () at /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () at /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_object_new () at /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: Upgraded to artful on 2017-08-18 (9 days ago)
UserGroups:

[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.