[regression] Mir EGL clients all crash with SIGSEGV in XGetXCBConnection()

Bug #1696797 reported by Alan Griffiths
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Invalid
High
Unassigned
mesa (Ubuntu)
Fix Released
High
Unassigned
miral (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Running today's daily ISO, enabled universe and installed:

    $ sudo apt install miral-examples mir-graphics-drivers-desktop qterminal qtubuntu-desktop

Then,

    $ miral-app -launcher qterminal

works.

But after doing,

    $ sudo apt upgrade -y

It crashes as seen here.

Probably related:

    $ sudo apt install mir-demos
    $ mir_demo_server --test-client mir_demo_client_eglplasma

also crashes.

Avoiding EGL use by:

    $ miral-app -kiosk

Works until an EGL app is started

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: miral-examples 1.3.2+17.04.20170330.5-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
CasperVersion: 1.383
CurrentDesktop: GNOME
Date: Thu Jun 8 16:15:14 2017
ExecutablePath: /usr/bin/miral-shell
LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170607)
ProcCmdline: /usr/bin/miral-shell --file /run/user/999/miral_socket --desktop_file_hint=miral-shell.desktop
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: miral
StacktraceTop:
 XGetXCBConnection () from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
Title: miral-shell crashed with SIGSEGV in XGetXCBConnection()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Alan Griffiths (alan-griffiths) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 XGetXCBConnection (dpy=dpy@entry=0x7fc530001080) at ../../src/x11_xcb.c:9
 dri2_get_xcb_connection (dri2_dpy=dri2_dpy@entry=0x7fc534000f70, disp=<optimized out>, disp=<optimized out>, drv=<optimized out>) at ../../../src/egl/drivers/dri2/platform_x11.c:1204
 dri2_initialize_x11_dri3 (drv=<optimized out>, disp=0x7fc534000990) at ../../../src/egl/drivers/dri2/platform_x11.c:1344
 dri2_initialize_x11 (drv=<optimized out>, disp=0x7fc534000990) at ../../../src/egl/drivers/dri2/platform_x11.c:1513
 dri2_initialize (drv=<optimized out>, disp=0x7fc534000990) at ../../../src/egl/drivers/dri2/egl_dri2.c:847

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in miral (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: miral-shell crashed with SIGSEGV in XGetXCBConnection()

This looks like a typical Mesa regression. And Mesa got updated 13 hours ago (4 hours prior to this bug report). That's probably no coincidence :)

https://launchpad.net/ubuntu/+source/mesa

information type: Private → Public
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Yep. The crash happens in all Mir GL clients. Other Mir demo servers start up OK, but miral-shell crashes because it has an internal client (SpinnerSplash).

summary: - miral-shell crashed with SIGSEGV in XGetXCBConnection()
+ [regression] Mir EGL clients all crash with SIGSEGV in
+ XGetXCBConnection()
tags: added: regression-release
Changed in mesa (Ubuntu):
importance: Undecided → High
Changed in miral (Ubuntu):
status: New → Invalid
Changed in mir:
status: New → Invalid
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

On the other hand, this appears to be the same as bug 1526658, which was fixed in Mir itself...

Changed in mir:
importance: Undecided → High
status: Invalid → New
Revision history for this message
Chris Halse Rogers (raof) wrote :

So, the problem here is going to be the EGL platform detection - it's failing to detect Mir, and is instead trying (and failing) to connect to an X server.

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

Yep. A problem we've hit a few times before...

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

This bug was fixed in the package mesa - 17.1.2-2ubuntu2

---------------
mesa (17.1.2-2ubuntu2) artful; urgency=medium

  * egl-platform-mir.patch
  * egl-platform-rs.patch
    - Fix configure.ac so that the Mir EGL platforms are actually
      built. (LP: #1526658) (LP: #1696797)

 -- Christopher James Halse Rogers <email address hidden> Fri, 16 Jun 2017 17:51:50 +1000

Changed in mesa (Ubuntu):
status: New → Fix Released
Changed in mir:
status: New → Invalid
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.