gnome-software crashed with SIGSEGV in g_type_check_instance()

Bug #1752650 reported by Антон Дерлюк
This bug report is a duplicate of:  Bug #1752645: Crash installing from snap:// URL. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-software (Ubuntu)
New
Undecided
Unassigned

Bug Description

-

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.27.90-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
Uname: Linux 4.15.0-11-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Wed Feb 28 23:18:23 2018
ExecutablePath: /usr/bin/gnome-software
ExecutableTimestamp: 1519079819
InstallationDate: Installed on 2017-06-18 (255 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170618)
InstalledPlugins:
 gnome-software-plugin-flatpak 3.27.90-1ubuntu1
 gnome-software-plugin-limba N/A
 gnome-software-plugin-snap 3.27.90-1ubuntu1
ProcCmdline: /usr/bin/gnome-software --gapplication-service
ProcCwd: /home/anton
SegvAnalysis:
 Segfault happened at: 0x7fe66804f17d <g_type_check_instance+13>: mov (%rdi),%rax
 PC (0x7fe66804f17d) ok
 source "(%rdi)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-software
StacktraceTop:
 g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_handlers_disconnect_matched () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gnome-software crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Антон Дерлюк (gespenst-vs) 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 #1752645, 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-amd64-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.