I chose Medium on the assumption that the only Mir code affected here was a couple of examples (and that the real problem is Mesa bug 1480755). However the issue affecting Unity8 might be the same mistake from the examples also made in real_kms_display_configuration.cpp and elsewhere. So yeah that would qualify as high then.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in 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] Status in Mir: Triaged Status in mesa package in Ubuntu: Triaged Status in mir package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.11+16.04.20160310.4-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/7e3f860c1afbbc114bf73f9d7a2966209a25093d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1560498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
