A couple of thoughts on this... 1. Tinkering with display hardware may fail at times if its not ready for some reason. So Mir should be resilient to such exceptions and recover.
2. If an error is actually unrecoverable we need to start changing those throws to abort() or similar. So we get clean stack traces and can easily diagnose then fix the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294510 Title: unity-system-compositor crashed [what(): Failed to set DRM crtc] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1294510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
