OK, so current investigation results indicate that this is probably an issue (race?) in our start-up scripts. The start-up wizard should be setting MIR_SOCKET=/run/user/32011/wizard_socket in the upstart environment [1], and restoring the previous value when shutting down [2].
However it seems that occasionally something goes wrong at the cleanup phase and the environment variable is not restored, or unity8 manages to start before the cleanup phase is performed.
OK, so current investigation results indicate that this is probably an issue (race?) in our start-up scripts. The start-up wizard should be setting MIR_SOCKET= /run/user/ 32011/wizard_ socket in the upstart environment [1], and restoring the previous value when shutting down [2].
However it seems that occasionally something goes wrong at the cleanup phase and the environment variable is not restored, or unity8 manages to start before the cleanup phase is performed.
[1] https:/ /bazaar. launchpad. net/~system- settings- touch/ubuntu- system- settings/ rtm-14. 09/view/ head:/wizard/ ubuntu- system- settings- wizard. conf /bazaar. launchpad. net/~system- settings- touch/ubuntu- system- settings/ rtm-14. 09/view/ head:/wizard/ ubuntu- system- settings- wizard- cleanup. conf
[2] https:/