unity-control-center crashed with SIGSEGV in g_type_check_instance()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-control-center (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Tried disabling file diagnostics and it crashed.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-control-
ProcVersionSign
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Apr 13 15:34:26 2016
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2016-02-23 (49 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
ProcCmdline: unity-control-
SegvAnalysis:
Segfault happened at: 0x7f7c2385cd99 <g_type_
PC (0x7f7c2385cd99) ok
source "(%rax)" (0x200000005800) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity-control-
StacktraceTop:
g_type_
g_signal_
g_signal_emit () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: unity-control-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
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 #1375073, 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.