unity-control-center crashed with SIGSEGV in gtk_widget_size_allocate_with_baseline()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-control-center (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Got the error after clicking "Displays".
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: unity-control-
Uname: Linux 4.6.0-040600-
NonfreeKernelMo
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Tue May 24 01:08:38 2016
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2016-05-17 (6 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcCmdline: unity-control-
ProcEnviron:
PATH=(custom, user)
SHELL=/bin/bash
LANG=en_US.UTF-8
LANGUAGE=en_US
XDG_RUNTIME_
SegvAnalysis:
Segfault happened at: 0x7f90a6c21b27 <gtk_widget_
PC (0x7f90a6c21b27) ok
source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-control-
StacktraceTop:
gtk_widget_
?? () from /usr/lib/
gtk_widget_
?? () from /usr/lib/
g_closure_invoke () from /usr/lib/
Title: unity-control-
UpgradeStatus: No upgrade log present (probably fresh install)
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 #1547063, 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.