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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511095 Title: unity-system-compositor crash, no interaction on windowed mode To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1511095/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
