unity8-dash crashed with SIGSEGV in QOpenGLContext::shareGroup()

[Danial Behzadi]

No app starts. It just flashes a window containing app's icon, but it would be closed immediately.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity8 8.11+16.04.20160212-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
Uname: Linux 4.4.0-4-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Wed Feb 17 04:26:38 2016
ExecutablePath: /usr/bin/unity8-dash
InstallationDate: Installed on 2015-04-24 (298 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: unity8-dash --desktop_file_hint=/usr/share/applications/unity8-dash.desktop
SegvAnalysis:
 Segfault happened at: 0x7f3e63fb3200 <_ZNK14QOpenGLContext10shareGroupEv>: mov 0x8(%rdi),%rax
 PC (0x7f3e63fb3200) ok
 source "0x8(%rdi)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity8
StacktraceTop:
 QOpenGLContext::shareGroup() const () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
Title: unity8-dash crashed with SIGSEGV in QOpenGLContext::shareGroup()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip disk libvirtd lpadmin plugdev sambashare sudo vboxusers

[Apport retracing service (apport)]

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 #1541057, 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.