It appears this has not come from any Mir code change. It happens even with older Mir code. Something in the OS (xenial) has changed to cause this bug.
It appears this has not come from any Mir code change. It happens even with older Mir code. Something in the OS (xenial) has changed to cause this bug.