touch-packages team mailing list archive

[Gerry Boland <1475526@xxxxxxxxxxxxxxxxxx>]

This does suggest unity8-dash is starting but either
1. there is no mir server, such as unity8, running
2. MIR_SOCKET is not set to the correct mir server socket 
3. the permissions on the socket file mean dash cannot connect

We rely on upstart to ensure Dash starts when unity8 claims to be ready to accept connections. 
Upstart starts unity8, and puts it in the "starting" state. When unity8 is ready to accept client connections, it emits a SIGSTOP. Upstart intercepts this and SIGCONTs unity8. It then can start anything which requires the unity8 job to be "running" - such as unity8-dash.

It's also upstart's job to set the MIR_SOCKET env var, and other env
vars required. And to ensure permissions are correct.

So something in the above has gone wrong.

I am aware of unity8 not always shutting down correctly, which might
leave cruft behind. But I wold have thought upstart was cleaning that
cruft up, and only launching unity8-dash after a working unity8 had
started.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1475526

Title:
  unity8-dash crashes during power tests

Status in qtubuntu package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Unity8-dash crashes fairly often while running power usage tests.  I
  hope someone will be able to determine the root cause based on crash
  dumps and other logs.

  Here are some of the 170 instances I've seen so far... inside each are
  numbered directories for each test run, and the crash dumps are inside
  of those under var-crash/ .

  Arale rc-proposed 61, runs 2, 3, and 4:
  http://people.canonical.com/~platform-qa/power-results/2015-07-16_18:21:18-arale-61-power_usage_display_on/

  Arale devel-proposed 61, runs 2, 5, and 8:
  http://people.canonical.com/~platform-qa/power-results/2015-07-16_21:58:20-arale-61-power_usage_idle/

  Arale devel-proposed 60, runs 1, 2, 6, and 7:
  http://people.canonical.com/~platform-qa/power-results/2015-07-16_15:26:03-arale-60-power_usage_flight_mode_on/

  Krillin rc-proposed 62, runs 1, 3, 4, 5, 6, 7, and 8:
  http://people.canonical.com/~platform-qa/power-results/2015-07-13_02:02:39-krillin-62-power_usage_idle/

  Krillin devel-proposed 132, runs 1, 3, 6, and 7:
  http://people.canonical.com/~platform-qa/power-results/2015-07-13_22:02:04-krillin-132-power_usage_display_on/

  These are merely samples from recent test runs. I have plenty more if
  you need them, or can add additional logging to get more data from
  future tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1475526/+subscriptions