Ok, I suspect I have found the issue. Seems this hardware only supports
OpenGL 1.4 compatibility profile. Qt's EGL code is asking for at least
version 2.0, and so getting no valid context back.
Could you please install "mesa-utils" package and run "glxinfo". On the
hardware I have access to, I see these lines in the output:
Preferred profile: compat (0x2)
Max core profile version: 0.0
Max compat profile version: 1.4
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 2.0
I need to figure out why the X11 glx code is working, but the EGL code
is not. I also need to understand why at least OpenGL2.0 is desired by
Qt.
An option is to use GLES2 on this hardware, but as the GL/GLES switch is
made in Qt at compile time, that won't be straightforward either.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1549455
Title:
Unity8-dash on Intel Atom graphics crashes and restarts continuously
[qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) ==
EGL_TRUE"]
Status in Mir:
Invalid
Status in qtubuntu:
In Progress
Status in mesa package in Ubuntu:
Invalid
Status in mir package in Ubuntu:
Invalid
Status in qtdeclarative package in Ubuntu:
Confirmed
Status in qtmir package in Ubuntu:
Confirmed
Status in qtubuntu package in Ubuntu:
Triaged
Status in unity8 package in Ubuntu:
Confirmed
Bug description:
Qt clients are failing to create an egl context when running on Intel
Pineview systems under Mir.
eglCreateContext fails with a EGL_BAD_MATCH error code.
When it fails, Qt tries to delete & recreate the context, which then
crashes the client (bug 1580118)
=== Original bug description ===
This bug Makes the pc UNUSABLE
when I try to launch Unity 8 and Mir, after writing the password on the login
(in the image attached) the bar to enter the password disappears and my
computer screen stays stuck without them let me do anything. the connection
begins to separate and reattach alone and I can only move the cursor. it makes
the computer unusable and I am forced to restart forced to then enter into
Unity 7. represented in the screenshot is the lock status after entering the
password.
Version: unity8.12+16.04.201604.01.1
Version of Mir : 0.21
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1549455/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
