Is unity8-dash definitely being started after unity8 emits SIGSTOP - which is its way of telling upstart that the mir server is ready for incoming connections?
If not, dash might have tried to connect to mir, before unity8 has brought up mir. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1354412 Title: unity8-dash crashed with SIGABRT in raise() while running first boot on flo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1354412/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
