gnome-software crashed with SIGSEGV in g_param_spec_pool_lookup()

Bug #1709737 reported by Ralph Gilbert
This bug report is a duplicate of:  Bug #1708998: gnome-software fails to run on i386. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-software (Ubuntu)
New
Undecided
Unassigned

Bug Description

At power up I also see a FAILED to start/init for Apparmor

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-software 3.25.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
Uname: Linux 4.11.0-13-generic i686
ApportVersion: 2.20.6-0ubuntu4
Architecture: i386
CrashCounter: 1
CurrentDesktop: Unity:Unity7
Date: Wed Aug 9 17:12:21 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2016-08-17 (357 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba N/A
 gnome-software-plugin-snap 3.25.4-1ubuntu3
ProcCmdline: /usr/bin/gnome-software --gapplication-service
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb65058e6 <__strchr_sse2_bsf+38>: movdqa (%edi),%xmm0
 PC (0xb65058e6) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

Revision history for this message
Ralph Gilbert (rhg3) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

information type: Private → Public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.