gnome-software crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

Bug #1725845 reported by Paul Smith
This bug report is a duplicate of:  Bug #1752645: Crash installing from snap:// URL. Edit Remove
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-software (Ubuntu)
Confirmed
Critical
Robert Ancell
Bionic
Confirmed
Critical
Robert Ancell

Bug Description

Test Case:
1. Open https://snapcraft.io/store in a webbrowser
2. Search for discord and select the entry
3. Click on Install

Expected result
It installs discord.

Actual Result
This crash

== Original description ==

Searched for "evolution" then asked to install it (fresh install of Ubuntu 17.10, running Gnome session, not Unity, on Wayland). Gnome-software crashed.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-software 3.26.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Oct 21 17:50:23 2017
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2017-10-21 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba N/A
 gnome-software-plugin-snap 3.26.1-0ubuntu2
ProcCmdline: /usr/bin/gnome-software --gapplication-service
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fbdb2b78cd7 <g_type_check_instance_is_fundamentally_a+7>: mov (%rdi),%rdx
 PC (0x7fbdb2b78cd7) ok
 source "(%rdi)" (0x1900000000) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-software
StacktraceTop:
 g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-software crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Paul Smith (psmith-gnu) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_is_fundamentally_a (type_instance=type_instance@entry=0x1900000000, fundamental_type=fundamental_type@entry=80) at ../../../../gobject/gtype.c:4023
 g_object_unref (_object=0x1900000000) at ../../../../gobject/gobject.c:3227
 soup_socket_properties_unref (props=0x7fbd842e6b00) at soup-socket-properties.c:60
 soup_connection_finalize (object=0x557de05f2250) at soup-connection.c:72
 g_object_unref (_object=0x557de05f2250) at ../../../../gobject/gobject.c:3330

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-software (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-software (Ubuntu):
status: New → Confirmed
Revision history for this message
Eli Boaz (eli-boaz) wrote :

This happened after i clicked on a link from snapcraft.io to install discord.

Changed in gnome-software (Ubuntu):
importance: Medium → Critical
Changed in gnome-software (Ubuntu Bionic):
assignee: nobody → Robert Ancell (robert-ancell)
description: updated
description: updated
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.