<greyback__> my guess is that dash is being started before the unity8 mir server is running <tsdgeos> may be <tsdgeos> i know not enought about upstart stuff <tsdgeos> start on started unity8 <tsdgeos> is that too early? <greyback__> hmm, need to check what "started" actually means <greyback__> expect stop <greyback__> Specifies that the job's main process will raise the SIGSTOP signal to indicate that it is ready. init(8) will wait for this signal before running the job's post-start script, or considering the job to be running. <greyback__> hmm, think the state "started" after post-start script run <greyback__> so my theory is bad <greyback__> I'm quoting http://upstart.ubuntu.com/cookbook/
-- 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
