unity-api-bugs team mailing list archive

[James Hunt <1357252@xxxxxxxxxxxxxxxxxx>]

This still needs further investigation bug I think what's happening is
that cgmanager is racing with dbus. And since other jobs refer to
cgmanager they end up starting too early, resulting in the possibility
that the session init starts too early (before it's been cgroup-
constrained).

If correct, he solution to this problem is simple - change cgmanagers
'start on' condition to:

    start on started dbus

Currently, cgmanager *may* start before D-Bus because the 'start on'
condition is optimised to start cgmanager as soon as *its* requirements
are met. However, this seems nonsensical in this scenario because
although cgmanager is starting as early as it can, at the point it
starts D-Bus may not be running so clients cannot actually make use of
cgmanager yet!

Please could those affected by this problem test on their hardware to
see if they can still recreate the problem after running the following:

$ sudo mount -oremount,rw /
$ echo "start on started dbus" | sudo tee -a /etc/init/cgmanager.override
$ sudo reboot

-- 
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to Ubuntu Application Launcher.
https://bugs.launchpad.net/bugs/1357252

Title:
  Upstart jobs specifying cgroup fail to start occasionally

Status in Ubuntu Application Launcher:
  Incomplete
Status in Upstart:
  In Progress
Status in “cgmanager” package in Ubuntu:
  Confirmed

Bug description:
  After the ubuntu-app-launch landing in #188
  (http://people.canonical.com/~ogra/touch-image-stats/188.changes), UI
  Toolkit autopilot tests have started failing, see
  http://ci.ubuntu.com/smokeng/utopic/touch/mako/190:20140815:20140811.1/9676/ubuntuuitoolkit/
  and the #188 results too. It's different tests each time, but a bit
  above 10 of them tend to fail on each full run.

  Reproducable locally, where I got 11 such failures.

  To reproduce:
  [terminal 1]
  1. flash/update device if needed
  2. adb shell
  3. apt install ubuntu-ui-toolkit-autopilot
  4. powerd-cli display on bright # leave running, also unlock the screen so that lenses are shown
  [terminal 2]
  5. phablet-config autopilot --dbus-probe enable # wait until finishes
  6. phablet-test-run ubuntuuitoolkit

  A full test suite run will take around 0.5h and should produce a bunch
  of 'Application failed to start.':s.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+subscriptions