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 should not provide. That could be a Mesa bug or a Qt bug that's been around for much longer and Mesa only just became pedantic enough to say no. Remember EGL clients from the 'mir-demos' package still render OK so this is something specific to Q* clients. -- 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 "QEGLPlatformContext: eglMakeCurrent failed: 3001") Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in QtMir: Confirmed Status in qtubuntu: Confirmed Status in mesa package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Bug description: nothing works, all apps, dash are just black windows - Ubuntu 16.10 + proposed (x86, and using Nvidia 8600GT with nouveau drivers) and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 3001" To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620934/+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
