unity-api-bugs team mailing list archive

[James Hunt <1357252@xxxxxxxxxxxxxxxxxx>]

Currently, there is a minor bug whereby if upstart is running in debug
mode and trying to start a job that uses the 'cgroup' stanza will dump
cgroup debug details into the jobs log [1].

This could be useful here though since it should be possible to either
boot the session init in debug mode and see what turns up in
~/.cache/upstart/*.log. I've attached a patch to enable debug mode at
session init startup but you can always enable at any time using
'initctl log-priority debug'.

It would also be worth enabling debug mode for cgmanager by tweaking
/etc/init/cgmanager.conf and setting 'cgmanager_opts="--debug"' in that
file as shown (or simply creating /etc/init/cgmanager.override
containing 'env cgmanager_opts="--debug"'.


[1] - MP to resolve this is: https://code.launchpad.net/~jamesodhunt/upstart/make-cgroups-quiet-in-debug-mode/+merge/230762

** Patch added: "ubuntu-touch-session.patch"
   https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+attachment/4178538/+files/ubuntu-touch-session.patch

-- 
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:
  "Application failed to start." during autopilot tests after the newest
  ubuntu-app-launch landing

Status in Ubuntu Application Launcher:
  Triaged
Status in Upstart:
  New

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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+subscriptions