Comment 17 for bug 1560498

No it doesn't seem to be the same issue. Thanks for looking though -- I recall we copied the hack into another project but I haven't yet found where that was.

Although removing the original hack from the Mir examples is trivial, I suspect that's not actually the problem here because mir-demos should not crash Unity8 (?). The actual problem I suspect is our KMS/nested platform code which also hard codes pixel formats and those will often be wrong (xrgb when it's really argb). That part is probably non-trivial to fix.