You have to ignore all those destructor calls in the stacktraces because
they're probably side-effects of unwinding after an exception. The real
question is what exception occurred. The log shows it was:
terminate called after throwing an instance of
'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error>
>'
what(): Failed to set DRM crtc
** Summary changed:
- unity-system-compositor crashed with SIGABRT in
__gnu_cxx::__verbose_terminate_handler()
+ unity-system-compositor crashed with SIGABRT in
__gnu_cxx::__verbose_terminate_handler() [ what(): Failed to set DRM crtc]
** Also affects: mir
Importance: Undecided
Status: New
** Information type changed from Private to Public
** Changed in: unity-system-compositor (Ubuntu)
Status: New => Invalid
** Changed in: mir
Importance: Undecided => Critical
** Changed in: mir
Milestone: None => 0.1.8
** Summary changed:
- unity-system-compositor crashed with SIGABRT in
__gnu_cxx::__verbose_terminate_handler() [ what(): Failed to set DRM crtc]
+ unity-system-compositor crashed [what(): Failed to set DRM crtc]
--
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
