Assertion failure: "(eglContext_ = eglCreateContext( eglDisplay_, screen->eglConfig(), share ? share->eglContext() : EGL_NO_CONTEXT, attribs.constData())) != EGL_NO_CONTEXT"

[Jean-Baptiste Lallement]

I tried a unity8 session on an EeePC 1015PE (N450 / Intel Pineview / i386) and this crash occurs on login.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity8 7.85+14.04.20140404.is.7.85+14.04.20140403.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic i686
ApportVersion: 2.14.1-0ubuntu1
Architecture: i386
Date: Wed Apr 9 11:36:41 2014
ExecutablePath: /usr/bin/unity8
InstallationDate: Installed on 2012-10-08 (547 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta i386 (20121008)
ProcCmdline: unity8
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: unity8
StacktraceTop:
 QMessageLogger::fatal(char const*, ...) const () from /usr/lib/i386-linux-gnu/libQt5Core.so.5
 qt_assert(char const*, char const*, int) () from /usr/lib/i386-linux-gnu/libQt5Core.so.5
 ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqubuntumirserver.so
 ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqubuntumirserver.so
 QOpenGLContext::create() () from /usr/lib/i386-linux-gnu/libQt5Gui.so.5
Title: unity8 crashed with SIGABRT in QMessageLogger::fatal()
UpgradeStatus: Upgraded to trusty on 2013-10-31 (159 days ago)
UserGroups: adm autopilot lpadmin sambashare sudo

[Jean-Baptiste Lallement (jibel)]

Log from ~/.cache/upstart/unity8-mir.log

[Apport retracing service (apport)]

StacktraceTop:
 qt_message_fatal (context=..., message=...) at global/qlogging.cpp:979
 QMessageLogger::fatal (this=0xabdfeb8c, msg=0xb69f9b3c "ASSERT: \"%s\" in file %s, line %d") at global/qlogging.cpp:384
 qt_assert (assertion=0xabfa0c2c "(eglContext_ = eglCreateContext( eglDisplay_, screen->eglConfig(), share ? share->eglContext() : EGL_NO_CONTEXT, attribs.constData())) != EGL_NO_CONTEXT", file=0xabfa0ba0 "../../../../src/platforms/base/context.cc", line=63) at global/qglobal.cpp:2096
 QUbuntuBaseContext::QUbuntuBaseContext (this=0xa24c29b0, screen=0xaa498a60, share=0x0) at ../../../../src/platforms/base/context.cc:61
 QUbuntuBaseIntegration::createPlatformOpenGLContext (this=0xaa47b4e8, context=0xa3421d68) at ../../../../src/platforms/base/integration.cc:93

[Jean-Baptiste Lallement (jibel)]

setting to critical because the desktop session doesn't even start.

[Michał Sawicz (saviq)]

I'm inclined to say that this is a hardware-too-old issue... :/

[Michał Sawicz (saviq)]

Can you try the "Running Mir natively" part from http://unity.ubuntu.com/mir/using_mir_on_pc.html ?

[Jean-Baptiste Lallement (jibel)]

I followed instructions from http://unity.ubuntu.com/mir/using_mir_on_pc.html, I get a black screen with a pointer and nothing on the screen when I start a mir client. However, even if nothing is drawn on the screen, the client is running because when I switch to VT1, there are FPS displayed on VT2.
When the client starts, there is also a warning on VT2:
"libEGL warning: unsupported platform (null)"

I'm fine if the hardware is too 'old' or unsupported and close this report as won't fix, but in this case there should be a warning dialog or a fallback as in the early days of Unity.

[Daniel Gimpelevich (daniel-gimpelevich)]

Similar thing happening with an EeePC 900A which I have retrofitted with a touchscreen under Trusty. Please fix.

[Daniel Gimpelevich (daniel-gimpelevich)]

()
libEGL warning: unsupported platform (null)
WARNING: QApplication was not created in the main() thread.
libEGL warning: unsupported platform (null)
unity::action::ActionManager::ActionManager(QObject*):
 Could not determine application identifier. HUD will not work properly.
 Provide your application identifier in $APP_ID environment variable.
file:///usr/lib/i386-linux-gnu/qt5/qml/Ubuntu/Components/Tabs.qml:335: TypeError: Cannot call method 'indexOf' of undefined
UbuntuKeyboardInfo - socket error: "QLocalSocket::connectToServer: Invalid name"
QQmlExpression: Expression file:///usr/share/unity8/Hud/Hud.qml:431:36 depends on non-NOTIFYable properties:
    HudClient::results
QQmlExpression: Expression file:///usr/share/unity8/Hud/Hud.qml:342:32 depends on non-NOTIFYable properties:
    HudClient::toolBarModel
file:///usr/share/unity8/Shell.qml:628:5: QML Binding: Binding loop detected for property "target"

(process:1935): GLib-GIO-CRITICAL **: g_bus_watch_name: assertion 'g_dbus_is_name (name)' failed
file:///usr/share/unity8/Hud/HudParametrizedActionsPage.qml:138:5: QML Item: Binding loop detected for property "width"
file:///usr/share/unity8/Stages/PhoneStage.qml:51: TypeError: Cannot read property 'screenshot' of null

(process:1935): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
file:///usr/lib/i386-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:198:5: QML StyledItem: Binding loop detected for property "style"
file:///usr/share/unity8/Launcher/LauncherDelegate.qml:62:20: QML QQuickImage: Failed to get image from provider: image://theme/skype.png
file:///usr/share/unity8/Launcher/LauncherDelegate.qml:62:20: QML QQuickImage: Failed to get image from provider: image://theme/skype.png
file:///usr/share/unity8/Launcher/LauncherDelegate.qml:62:20: QML QQuickImage: Failed to get image from provider: image://theme/skype.png
file:///usr/share/unity8/Launcher/LauncherDelegate.qml:62:20: QML QQuickImage: Failed to get image from provider: image://theme/system-file-manager
file:///usr/share/unity8/Launcher/LauncherDelegate.qml:62:20: QML QQuickImage: Failed to get image from provider: image://theme/system-file-manager
file:///usr/share/unity8/Launcher/LauncherDelegate.qml:62:20: QML QQuickImage: Failed to get image from provider: image://theme/system-file-manager
file:///usr/share/unity8/Launcher/LauncherDelegate.qml:62:20: QML QQuickImage: Failed to get image from provider: image://theme/preferences-system
file:///usr/share/unity8/Launcher/LauncherDelegate.qml:62:20: QML QQuickImage: Failed to get image from provider: image://theme/preferences-system
file:///usr/share/unity8/Launcher/LauncherDelegate.qml:62:20: QML QQuickImage: Failed to get image from provider: image://theme/preferences-system
file:///usr/share/unity8/Launcher/LauncherDelegate.qml:62:20: QML QQuickImage: Failed to get image from provider: image://theme/utilities-terminal
file:///usr/share/unity8/Launcher/LauncherDelegate.qml:62:20: QML QQuickImage: Failed to get image from provider: image://theme/utilities-terminal
file:///usr/share/unity8/Launcher/LauncherDelegate.qml:62:20: QML QQuickImage: Failed to get image from provider: image://theme...

[Daniel Gimpelevich (daniel-gimpelevich)]

Please support older Intel hardware.

[Andreas Pokorny (andreas-pokorny)]

I tried on a N270 with 950GMA - older than N450 - the gpu is separate but the feature level is similar so it also uses the i915 driver. ,Mir demo shell works well. All software based clients work. eglplasma crashes inside the dri i915 driver code with a segmentation fault within glDrawArrays when it sets up the renderbuffer.. inside intel_mipmap_tree.c:871. egltriangle and eglflash fail to change the buffer - i.e. you see the buffer of a previous client with the same window size.

[Andreas Pokorny (andreas-pokorny)]

The i915 driver seems to use a separate path for buffer allocation, which is not patched for allocating buffers for fd. So mesa on mir platform will not work.

[Daniel van Vugt (vanvugt)]

Please refer to bug 1275398 about Mir/Mesa supporting older intel hardware. I've been trying to test lots of older chips.

As for the crash (assertion failure) reported here, that's different. Although the root cause is probably the same. So I'm going to make this bug just about the assertion failure.

See also similar bug 1275684 but check bug 1275398 is fixed too.