Comment 8 for bug 1665123

This doesn't seem to be version-related at all. Even when trying to switch unity8-session to use the mir-libs 0.26.1 snap on an up to date xenial+overlay system, I hit this bug.

It seems the host Mir server (USC) is telling unity8 to directly load /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.12. This can't be seen from the snap (since Ubuntu Core is mounted at /usr/lib -- unless we used classic mode...).

This has worked in our snap because we have an LD_PRELOAD trick that rewrites such dlopens into our snap space.

Even MIR_SERVER_PLATFORM_PATH doesn't help, it gets ignored in favor of host server's location. Which is probably the right thing to do if the drivers must match. Just ends up biting us here.

I'll avoid using mir-libs in our snap for now, instead bundling the libraries in. Apparently the Mir team is working on making this coupling less painful.