[regression] Mir 0.6 GL clients crash immediately on startup (Mesa is trying to use X11 instead of Mir)

Bug #1350163 reported by Daniel van Vugt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Critical
Alexandros Frantzis
0.6
Fix Released
Critical
Alexandros Frantzis
mesa (Ubuntu)
Invalid
Critical
Chris Halse Rogers
mir (Ubuntu)
Fix Released
Critical
Unassigned

Bug Description

[regression] Mir GL clients crash immediately on startup.

This is on a freshly updated utopic system.

(gdb) bt
#0 0x00007ff4f1b706d7 in XGetXCBConnection ()
   from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1
#1 0x00007ff4f352abb1 in dri2_initialize_x11_dri2 (drv=<optimised out>,
    disp=0x122e910)
    at ../../../../../../src/egl/drivers/dri2/platform_x11.c:1172
#2 dri2_initialize_x11 (drv=<optimised out>, disp=0x122e910)
    at ../../../../../../src/egl/drivers/dri2/platform_x11.c:1291
#3 0x00007ff4f352357d in _eglMatchAndInitialize (dpy=0x122e910)
    at ../../../../../src/egl/main/egldriver.c:613
#4 0x00007ff4f3523864 in _eglMatchDriver (dpy=dpy@entry=0x122e910,
    test_only=test_only@entry=0) at ../../../../../src/egl/main/egldriver.c:643
#5 0x00007ff4f351ea6a in eglInitialize (dpy=0x122e910, major=0x0, minor=0x0)
    at ../../../../../src/egl/main/eglapi.c:355
#6 0x0000000000402db0 in mir_eglapp_init (argc=1, argv=0x7fffb9ac9ec8,
    width=0x7fffb9ac96c8, height=0x7fffb9ac96cc)
    at /home/dan/bzr/mir/dev/examples/eglapp.c:386
#7 0x0000000000401ee9 in main (argc=1, argv=0x7fffb9ac9ec8)
    at /home/dan/bzr/mir/dev/examples/egltriangle.c:85

Tags: regression

Related branches

Changed in mir:
milestone: none → 0.6.0
summary: - [regression] Mir GL clients crash immediately on startup
+ [regression] Mir GL clients crash immediately on startup (Mesa is trying
+ to use X11 instead of Mir)
Revision history for this message
Chris Halse Rogers (raof) wrote : Re: [regression] Mir GL clients crash immediately on startup (Mesa is trying to use X11 instead of Mir)

Ah. This is autodetect failing; if you set EGL_PLATFORM=mir then everything works.

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

Workaround (for the client):
env EGL_PLATFORM=mir ...

affects: mir → mesa (Ubuntu)
Changed in mesa (Ubuntu):
assignee: nobody → Chris Halse Rogers (raof)
milestone: 0.6.0 → none
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

At a guess we removed/changed some symbol in libmirclient (yesterday) and that prevents libEGL from finding/using libmirclient properly.

Changed in mir:
importance: Undecided → Critical
status: New → Invalid
milestone: none → 0.6.0
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Added a "Mir" task back in, temporarily just so the team can find this bug.

summary: - [regression] Mir GL clients crash immediately on startup (Mesa is trying
- to use X11 instead of Mir)
+ [regression] Mir 0.6 GL clients crash immediately on startup (Mesa is
+ trying to use X11 instead of Mir)
Changed in mir:
status: Invalid → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Actually, make it "New" for Mir. If there's some symbol we've accidentally hidden then that's a Mir bug.

Changed in mesa (Ubuntu):
status: New → In Progress
Changed in mir:
assignee: nobody → Alexandros Frantzis (afrantzis)
status: New → In Progress
tags: added: regression
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Bisected. The regression happened in:

------------------------------------------------------------
revno: 1799 [merge]
author: Alan Griffiths <email address hidden>
committer: Tarmac
branch nick: development-branch
timestamp: Tue 2014-07-29 08:40:30 +0000
message:
  client: provide linker scripts to control the symbols exported by [mesa|android] libmirclientplatform.

  Approved by Chris Halse Rogers, Kevin DuBois, PS Jenkins bot.
------------------------------------------------------------

Changed in mesa (Ubuntu):
status: In Progress → Invalid
Changed in mir:
milestone: 0.6.0 → 0.7.0
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:mir/devel at revision None, scheduled for release in mir, milestone Unknown

Changed in mir:
status: In Progress → Fix Committed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Fix committed manually to lp:mir/0.6 at r1808.

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

mir (0.6.0+14.10.20140811-0ubuntu1) utopic; urgency=medium

Changed in mir (Ubuntu):
importance: Undecided → Critical
status: New → Fix Released
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Sorry for the confusion. Most of the 0.7.0 series got merged into 0.6.0 at a late stage. I've verified everything in 0.6.0 is also fixed in 0.7.0. So although the branched fixes in 0.7.0 have not been "released" yet, the equivalent fixes in 0.6.0 have. No need to mention them in 0.7 any more.

no longer affects: mir
Changed in mir:
status: New → Fix Released
importance: Undecided → Critical
assignee: nobody → Alexandros Frantzis (afrantzis)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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