gnome-software crashed with SIGSEGV in g_type_check_instance()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-software (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Not long after installing and launching gnome clocks snap
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4
ProcVersionSign
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 20 10:09:14 2018
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2017-09-29 (202 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
InstalledPlugins:
gnome-
gnome-
gnome-
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7facaac4a17d <g_type_
PC (0x7facaac4a17d) 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_
g_signal_
g_signal_emit () from /usr/lib/
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
Title: gnome-software crashed with SIGSEGV in g_type_
UpgradeStatus: Upgraded to bionic on 2018-04-14 (5 days ago)
UserGroups: adm cdrom dip 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 #1760397, 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.