[Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

Without this, if a configuration is, say, available only on GLES2/3, but not on GLES1, and is rejected by the dri module's bindContext call, eglMakeCurrent fails with error "EGL_SUCCESS". In this patch, we set error to EGL_BAD_MATCH, which is what CTS/dEQP

[Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

Probably caused by commit de695014eb6c819b050a4f7f2f952c4466047292 Author: Nicolas Boichat Date: Fri Jul 15 16:24:20 2016 +0800 egl/dri2: dri2_make_current: Set EGL error if bindContext fails -- You received this bug notification because you are a member of

Re: [Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

On 13/09/2016 08:49, Gerry Boland wrote: > Could someone with a problematic system log into Unity7, and for a simple qml > file, run: > QT_XCB_GL_INTEGRATION=xcb_egl qmlscene ~/test.qml > and see does it fail? It works fine. -- You received this bug notification because you are a member of

[Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

Note it is only Unity8 which is mixing GL and GLES calls, clients are not doing that. Qt clients are only doing GL calls on desktop. Nothing obvious comes to mind here. It may be Qt's EGL configuration code is failing - code that QtUbuntu is using. Another consumer of that same code is the EGL

[Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

Maybe... Mesa only just started to care about mixing and matching GL with GLES in invalid ways. I know we have done it in the past and possibly still do. Maybe today is the day Mesa finally started checking the validity of our GL calls...? -- You received this bug notification because you are a

[Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

Enabling debugging I can't see anything EGL-related failing before the errors start in unity8-dash.log. Although rendering appears to fail: [2016-09-13:12:45:18.825] ubuntumirclient: Created surface with geometry: QRect( 0,24 510x712) title: "Scopes" role: 1 [2016-09-13:12:45:18.825]

[Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

CONFIRMED. Downgrading Mesa to 12.0.1 fixes the problem: https://launchpad.net/ubuntu/+source/mesa/12.0.1-3ubuntu2/+build/10506751 So the regression was triggered by: https://launchpad.net/ubuntu/+source/mesa/12.0.2-1ubuntu1 However that doesn't mean Mesa is buggy necessarily. Our Qt EGL setup

[Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

** Changed in: canonical-devices-system-image Milestone: None => 13 ** Changed in: canonical-devices-system-image Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu.

[Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

Another prime candidate that possibly triggered this bug: https://launchpad.net/ubuntu/+source/mesa/12.0.2-1ubuntu1 Released on 7 September (which would have been 8 Sept here). It could easily be that our Qt apps are (and always have been) requesting some EGL attributes that Mesa can not or

[Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

And the app never rendered because its call to eglMakeCurrent failed with error 3001 (EGL_NOT_INITIALIZED). -- 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/1620934 Title: Qt/QML apps

[Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

@larryprice the black Scopes and blank Settings are splash screens, basically means the app never rendered. -- 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/1620934 Title: Qt/QML apps

[Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

The System Settings log could actually contain some interesting information. It seems to imply that the launcher is out of memory. ** Attachment added: "System Settings log" https://bugs.launchpad.net/qtmir/+bug/1620934/+attachment/4739455/+files/application-legacy-ubuntu-system-settings-.log

[Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

In my case, the Dash shows up as just a black screen with the Dash icon and "Scopes" and never finishes loading. When opening up System Settings, it sits on a white screen with just the titlebar. When opening up the web browser, I got a crash and a weird update notifier log (attached) in addition

[Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

qtbase-opensource-src did get a new release on september 3rd. But xenial stable-phone-overlay and yakkety seem to be carrying the very same qt version, so scrap my theory from comment #30... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed

[Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

Maybe the culprit is different Qt versions between xenial and yakkety? -- 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/1620934 Title: Qt/QML apps don't render any more (logs say

[Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

This only happens in yakkety. The same qtmir, qtubuntu and unity8 runs fine in xenial. Lost a couple of hours on this issue yesterday and my "solution" was to reboot my test laptop into a xenial partition so I could unblock myself. -- You received this bug notification because you are a member

[Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

Yeah it could have happened a day or two ago. Probably been a couple of days since I tested Unity8 apps. -- 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/1620934 Title: Qt/QML apps don't

[Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

What we need is someone with a slightly out of date yakkety that doesn't have the bug. Then upgrade it, check the regression now occurs and work from that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu.

[Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

The only relevant piece there seems to be qtmir, but looking at its changelog [1] there's no related changes there... [1] https://launchpad.net/ubuntu/+source/qtmir/0.4.8+16.10.20160831-0ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is

[Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

Although it could also have happened a day or two ago in a different upgrade. I might not have noticed. -- 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/1620934 Title: Qt/QML apps don't

[Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

The regression appears to have happened for me in this upgrade: Start-Date: 2016-09-09 09:40:23 Commandline: apt full-upgrade Requested-By: dan (1000) Upgrade: ubuntu-settings:amd64 (16.10.2, 16.10.3), suru-icon-theme:amd64 (16.10+16.10.20160829.3-0ubuntu1, 16.10+16.10.20160908-0ubuntu1),

[Desktop-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

@dinamic, can you please look at /var/log/apt/history.log and try to estimate which upgrade broke it? -- 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/1620934 Title: Qt/QML apps don't