*** This bug is a duplicate of bug 1237332 ***
https://bugs.launchpad.net/bugs/1237332
Is this actually a dup of bug#1237332 (Fatal exceptions raised in the
Mir code have no usable stack trace) or is it just that it is impossible
to analyse this bug because 1237332 exists? Or to put it another way,
if that bug is fixed will this one then also be automatically fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235876
Title:
unity-system-compositor crashed with SIGABRT in
__gnu_cxx::__verbose_terminate_handler() resuming with two screend
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1235876/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
