>We need to check if we're emitting the SIGSTOP message to upstart > after AppMan is ready, so that upstart starts the dash & OSK at the right time
That would be preferable, yes. Or we emit a custom signal when AppMan ready, but is there any reason to allow stuff to launch before AppMan is ready? Maybe the OSK? > Or else we make the Mir reject incoming connections until AppMan is ready That would mean the dash would abort when it launched too early, cause a .crash and delay launching it for real. ** Changed in: qtmir (Ubuntu) Status: Confirmed => Triaged ** Changed in: qtmir (Ubuntu) Importance: Undecided => High ** Changed in: qtmir (Ubuntu) Assignee: (unassigned) => Gerry Boland (gerboland) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394208 Title: Unity8 unable to find the dash, which is also running in the background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1394208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs