gnome-system-monitor crashed with SIGSEGV in __GI___libc_free()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-system-monitor (Ubuntu) |
New
|
Medium
|
Unassigned |
Bug Description
gnome-system-
ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: gnome-system-
ProcVersionSign
Uname: Linux 4.9.0-15-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Feb 16 11:27:26 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2016-08-11 (188 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
ProcCmdline: gnome-system-
SegvAnalysis:
Segfault happened at: 0x7f035405a162 <__GI__
PC (0x7f035405a162) ok
source "-0x8(%rdi)" (0x55c4fffffff8) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-system-
StacktraceTop:
__GI___libc_free (mem=0x55c50000
get_process_
proctable_
update_
create_
Title: gnome-system-
UpgradeStatus: Upgraded to zesty on 2016-12-20 (57 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sbuild sudo vboxusers
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 #1665209, 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.