unity-control-center crashed with SIGSEGV in gtk_widget_get_scale_factor()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-control-center (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
crash after update to beta version
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-control-
ProcVersionSign
Uname: Linux 4.4.0-17-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 7 20:03:52 2016
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2014-07-01 (646 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: unity-control-
ProcEnviron:
PATH=(custom, no user)
SHELL=/bin/bash
LANG=fr_FR.UTF-8
LANGUAGE=fr_FR
XDG_RUNTIME_
SegvAnalysis:
Segfault happened at: 0x7f0eca05e277 <gtk_widget_
PC (0x7f0eca05e277) ok
source "0xc0(%rdx)" (0x000000c0) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-control-
StacktraceTop:
gtk_widget_
?? () from /usr/lib/
?? () from /usr/lib/
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
Title: unity-control-
UpgradeStatus: Upgraded to xenial on 2016-04-07 (0 days ago)
UserGroups: adm cdrom dialout 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 #1544819, 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.