Comment 12 for bug 1511095

The stack trace shows a crash in mi::DisplayInputRegion::bounding_rectangle() because we don't have any displays in the region. A fix for the immediate crash is at:

https://code.launchpad.net/~afrantzis/mir/maybe-fix-1511095-for-0.17/

From the supplied info I can't tell if not having any detected active displays is a valid situation or it's indeed a problem and the root cause of what we are seeing. Whatever the case we shouldn't crash like this, so this fix is a definite improvement, even if it turns out not to be a final fix.