As described in the duplicate bug #1235209, this happens when an application tries to close itself. The application session is closed, destroying underlying mir surface resources, but then information about the destroyed surface (it's name) is requested leading to a crash. Still trying to get the details about why the name is requested.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234609 Title: unity8 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1234609/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
