unity8-dash crashed with SIGSEGV in QSGRenderContext::initialize()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity8 (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Crash happened generally occasionally
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity8 8.11+16.
ProcVersionSign
Uname: Linux 4.4.0-2-generic x86_64
NonfreeKernelMo
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
Date: Wed Feb 3 20:11:26 2016
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2016-02-01 (2 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
ProcCmdline: unity8-dash --desktop_
ProcEnviron:
LANGUAGE=it
PATH=(custom, no user)
XDG_RUNTIME_
LANG=it_IT.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fad56e5215d <__strstr_
PC (0x7fad56e5215d) ok
source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%xmm3" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity8
StacktraceTop:
QSGRenderConte
?? () from /usr/lib/
?? () from /usr/lib/
start_thread (arg=0x7fad1490
clone () at ../sysdeps/
Title: unity8-dash crashed with SIGSEGV in QSGRenderContex
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Changed in unity8 (Ubuntu): | |
importance: | Undecided → Medium |
Status changed to 'Confirmed' because the bug affects multiple users.