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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1560498 Title: Unity8 using vmwgfx_dri.so crashed in mir::graphics::nested::detail::DisplayBuffer::make_current() -> eglMakeCurrent() -> ... -> dri2_image_get_buffers() [platform_mir.c:138] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1560498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
