Black screen: Mir servers (unity8, unity-system-compositor, mir_demo*) all crash on start-up in libhybris [linker.c:27: android_dlopen: Assertion `0' failed.']

[Daniel van Vugt]

Having mir-graphics-drivers-android9:amd64 installed prevents unity-system-compositor starting:

[2016-05-05 10:19:09.118354] mirplatform: Found graphics driver: mir:mesa-kms (version 0.22.0)
android_dlopen called but not implemented!
unity-system-compositor: linker.c:27: android_dlopen: Assertion `0' failed.

which was caused by:

sudo apt-add-repository ppa:ci-train-ppa-service/stable-phone-overlay

WORKING: hybris 0.1.0+git20151016+6d424c9-0ubuntu7
FAILING: hybris 0.1.0+git20151016+6d424c9-0ubuntu11

WORKAROUNDS:
 * Remove ppa:ci-train-ppa-service/stable-phone-overlay from your system to completely solve the problem; or
 * Don't use Unity8 -- other Mir servers will work after you remove package mir-graphics-drivers-android9:amd64 which is their last remaining dependency on libhybris.

[Daniel van Vugt (vanvugt)]

It appears the crash is in libhybris. Which is not only used by the Mir Android platform, but also used by Unity8 directly!

[Daniel van Vugt (vanvugt)]

See bug 1578462 which shows removing the android graphics driver is not enough to stop the crash from happening. Because unity8 seems to use hybris directly.

[Daniel van Vugt (vanvugt)]

This sounds relevant:

libhybris (0.1.0+git20151016+6d424c9-0ubuntu11) xenial; urgency=medium

  * hybris: common: add stub linker implementation <----- ????
  * debian: split out common parts of the default configuration
  * debian: add build support for arm64
  * hybris: add README file stating which architectures are supported
  * hybris: autotools want it to be README

 -- Simon Fels <email address hidden> Tue, 03 May 2016 17:29:41 +0200

[Michał Sawicz (saviq)]

Fix coming in https://requests.ci-train.ubuntu.com/#/ticket/1370

[Launchpad Janitor (janitor)]

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

[Daniel van Vugt (vanvugt)]

I was keeping those tasks open to work around a Launchpad bug/feature: People can't find the bug if they're searching in a task where it's set to Invalid. And generally they will be searching in one of those.

[Kevin DuBois (kdub)]

untargetted to mir milestones, as the problem is being fixed in hybris

[Daniel van Vugt (vanvugt)]

Realistically this bug is only critical for desktop and not for the phablet Canonical System Image. So we can move the milestone.

[John McAleely (john.mcaleely)]

Oh, how is hybris involved on a desktop image?

[Daniel van Vugt (vanvugt)]

Two ways:

1. Mir's android/hybris graphics driver is built for all architectures including amd64/i386. Because we can, and it gives us better test coverage. In theory this is also useful for supporting Intel-based droids that lack a PC BIOS.

2. Unity8 links directly to hybris for its own reasons. Not sure why that is...

[dinamic (dinamic6661)]

i'm no longer affected by this bug, last update fixed it for me

[Daniel van Vugt (vanvugt)]

Confirmed, the fix has landed (ppa:ci-train-ppa-service/stable-phone-overlay)

[Daniel van Vugt (vanvugt)]

I think the target milestone is wrong. The fix is probably in OTA11 (?) It's certainly in Yakkety now: https://launchpad.net/ubuntu/+source/libhybris