gnome-software crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu GNOME |
New
|
Undecided
|
Unassigned | ||
gnome-software (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This happened very soon I did a 'dist-upgrade' using apt-get and upgraded the package mtools. Other than that I hadn't done anything, I didn't even launch gnome-software myself so I don't know why the error came about as I wasn't doing anything special which I don't normally do after turning on my machine.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gnome-software 3.20.1+
ProcVersionSign
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Sep 16 22:27:33 2016
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2016-05-15 (124 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fa7fd2b97ed <g_type_
PC (0x7fa7fd2b97ed) ok
source "(%rax)" (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_
g_object_ref () from /usr/lib/
gs_plugin_
?? () from /usr/lib/
?? () from /usr/lib/
Title: gnome-software crashed with SIGSEGV in g_type_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
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 #1551834, 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.