Hi Emanuele,
you attached a branch of mine to this bug - it makes our GL/EGL managing code
more robust. I had hoped it would fix this issue, but unfortunately it doesn't.
That's why I didn't attach that branch to this bug.
Annoyingly I don't have the hardware to hand either, so I'm flying
slightly blind. I make a change, then ask someone else to test it. I'll
have access to the hardware in about 2 weeks time, hopefully I'll have a
breakthrough then.
In the mean time, I've assembled some diagnostic applications that might
help me out.
If you're feeling adventurous, grab and compile
lp:~gerboland/+junk/qteglchooser/
Run it with
./qteglchooser -o
and
./qteglchooser -o -i
and pastebin me the output.
It's a tool I made to try explain how Qt is deciding which EGL
configuration to use. Qt can end up jumping through many hoops figuring
out a good EGL config, but also I might be using it slightly wrong
(hence the -i switch).
I would also appreciate if you could please grab, compile, run and
pastebin me the output of lp:~gerboland/+junk/eglinfo
That just prints the EGL configurations available, plus other EGL stuff.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir 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/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
