[Dash] unity8-dash crashed with ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"

Bug #1436203 reported by Alberto Mardegan
32
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Mir
Invalid
Undecided
Unassigned
mir (Ubuntu)
Invalid
Undecided
Unassigned
unity8 (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Testing unity8 on a Lenovo IdeaPad s10-3t. The welcome wizard completed successfully. Unity8 loads, the indicators are visible and working.
However, nothing else works: the scope shell doesn't load, only the splash screen is shown with the progress indicator spinning, and you can see that periodically it's restarted. Upstart logs for unity8-shell show an infinite loop of these:

==============
Loading module: 'libubuntu_application_api_desktop_mirclient.so.2.9.0'
[1427269742.137055] Loader: Loading modules from: /usr/lib/i386-linux-gnu/mir/client-platform/
[1427269742.137918] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/client-platform/dummy.so
[1427269742.139587] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/client-platform/mesa.so.2
[1427269742.140657] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/client-platform/mesa.so
QSocketNotifier: Can only be used with threads started with QThread
QSocketNotifier: Can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QIBusPlatformInputContext: invalid bus.
file:///usr/share/unity8/Dash/Dash.qml:245: ReferenceError: scopeStyle is not defined
UbuntuWindow - regular geometry
file:///usr/share/unity8/Dash/Dash.qml:245: ReferenceError: scopeStyle is not defined
ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE" in file ../../../src/ubuntumirclient/glcontext.cpp, line 70
Loading module: 'libubuntu_application_api_desktop_mirclient.so.2.9.0'
[1427269746.575630] Loader: Loading modules from: /usr/lib/i386-linux-gnu/mir/client-platform/
[1427269746.576432] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/client-platform/dummy.so
...
==============

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: unity8 8.02+15.04.20150318-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic i686
ApportVersion: 2.16.2-0ubuntu4
Architecture: i386
Date: Tue Mar 24 17:31:02 2015
ExecutablePath: /usr/bin/unity8-dash
InstallationDate: Installed on 2012-10-07 (898 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
ProcCmdline: unity8-dash --desktop_file_hint=/usr/share/applications/unity8-dash.desktop
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: unity8
StacktraceTop:
 QMessageLogger::fatal(char const*, ...) const () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
 qt_assert(char const*, char const*, int) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
 ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
 ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
 QOpenGLContext::destroy() () from /usr/lib/i386-linux-gnu/sse2/libQt5Gui.so.5
Title: unity8-dash crashed with SIGABRT in QMessageLogger::fatal()
UpgradeStatus: Upgraded to vivid on 2015-01-31 (52 days ago)
UserGroups: adm lpadmin nopasswdlogin sambashare sudo

Revision history for this message
Alberto Mardegan (mardy) wrote :
information type: Private → Public
summary: - [Dash] unity8-dash crashed with SIGABRT in QMessageLogger::fatail()
+ [Dash] unity8-dash crashed with SIGABRT in QMessageLogger::fatal()
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1415
 QMessageLogger::fatal (this=0xbfaedd48, msg=0xb6535b14 "ASSERT: \"%s\" in file %s, line %d") at global/qlogging.cpp:636
 qt_assert (assertion=0xb3b5e698 "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE", file=0xb3b5e66c "../../../src/ubuntumirclient/glcontext.cpp", line=70) at global/qglobal.cpp:2868
 UbuntuOpenGLContext::~UbuntuOpenGLContext (this=0x9ea5fb8, __in_chrg=<optimized out>) at ../../../src/ubuntumirclient/glcontext.cpp:70
 UbuntuOpenGLContext::~UbuntuOpenGLContext (this=0x9ea5fb8, __in_chrg=<optimized out>) at ../../../src/ubuntumirclient/glcontext.cpp:71

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity8 (Ubuntu):
importance: Undecided → Medium
summary: - [Dash] unity8-dash crashed with SIGABRT in QMessageLogger::fatal()
+ [Dash] unity8-dash crashed with SIGABRT in qt_message_fatal()
tags: removed: need-i386-retrace
Michał Sawicz (saviq)
summary: - [Dash] unity8-dash crashed with SIGABRT in qt_message_fatal()
+ [Dash] unity8-dash crashed with ASSERT: "eglDestroyContext(mEglDisplay,
+ mEglContext) == EGL_TRUE"
Changed in unity8 (Ubuntu):
status: New → Incomplete
Revision history for this message
Alberto Mardegan (mardy) wrote :
Revision history for this message
Alberto Mardegan (mardy) wrote :
Revision history for this message
Gerry Boland (gerboland) wrote :

I'm still struggling to reproduce this. Another suspicion I have is ibus being loaded. Could you do

stop unity8-dash
initctl unset-env --global QT_IM_MODULE
start unity8-dash

and see if that makes any difference. Thanks

Revision history for this message
Alberto Mardegan (mardy) wrote :

I'm not sure how I can give the above command. If I run it from a terminal (which is not running withing unity8, though, but from another tty), I get this:

   stop: Name "com.ubuntu.Upstart" does not exist

Are there any other ways to issue that command?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I'm not sure how or if this might be related to Mir at all. But filing it in the Mir project till the possibility is excluded.

Revision history for this message
Gerry Boland (gerboland) wrote :

@mardy looks like your shell does not have the correct values for DBUS_SESSION_BUS_ADDRESS and UPSTART_SESSION. These commands will try fetch those values from the unity8 process:

export `xargs -n 1 -0 < /proc/$(pidof unity8)/environ | grep DBUS_SESSION_BUS_ADDRESS`
export `xargs -n 1 -0 < /proc/$(pidof unity8)/environ | grep UPSTART_SESSION`

Revision history for this message
Alberto Mardegan (mardy) wrote :

With the proper environment variable I could issue the commands suggested in comment #7, but that didn't help: no difference. :-(

I also tried unsetting the QT_QPA_PLATFORMTHEME variable and manually setting the QT_QPA_PLATFORM variable to "ubuntumirclient", but nothing helped.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mir (Ubuntu):
status: New → Confirmed
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

I got this in qemu logging into unity8 session in yakkety.

Revision history for this message
doniks (kaabud-lp) wrote :

I get this constantly crashing&restarting scopes window after roughly the following steps
- new installation of ubuntu 16.04.2
- add stable phone overlay ppa
- apt install unity8-desktop-session
- apt dist-upgrade
- log out of unity7
- log into unity8

(steps are typed from memory. if it helps I can redo the installation and note the steps down exactly.)

Revision history for this message
doniks (kaabud-lp) wrote :

> if it helps I can redo the installation and note the steps down exactly.
uhm, no, sorry. I DID redo the installation, but now I can NOT reproduce the problem

tags: added: unity8-desktop
Changed in mir (Ubuntu):
status: Confirmed → Invalid
Changed in mir:
status: New → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.]

Changed in unity8 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.