unity-api-bugs team mailing list archive

[James Hunt <1357252@xxxxxxxxxxxxxxxxxx>]

The simplest way to see the problem (the following works as expected on
a desktop system, creating the cgroup and resulting in no error output):

$ id
uid=32011(phablet) gid=32011(phablet) groups=32011(phablet),4(adm),5(tty),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),114(autopilot),1001(radio),1002(bluetooth),1003(android_graphics),1004(android_input),1005(audio),1013(android_media),1015(sdcard_rw),1021(gps),2001(android_cache),3002(android_net3),3003(android_net),3004(android_net2),9997(android_nvram)
$ cgm create freezer freeze-me
call to cgmanager_create_sync failed: invalid request


And here's the cgmanager.log entry for the above request:

got creds pid 12565 (32011:32011)
do_create_main: do_create_main:263: controller='freezer', cgroup='freeze-me', ucred p=(pid=638, uid=0, gid=0), ucred r=(pid=12565, uid=32011, gid=32011)
do_create_main: do_create_main:273
do_create_main: do_create_main:279
do_create_main: do_create_main:288
do_create_main: do_create_main:318: r.pid=12565, r.uid=32011, r.gid=32011, dirpath='/run/cgmanager/fs/freezer'
may_access: may_access:925:uid=32011, gid=32011, path='/run/cgmanager/fs/freezer', mode=2
may_access: may_access:931: (O_RDONLY=0, O_RDWR=2, O_WRONLY=1)
may_access: may_access:944:sb.st_uid=0, sb.st_gid=0, sb.st_mode=16877 (0x41ed)
may_access: may_access:950
may_access: may_access:962
may_access: may_access:988
may_access: may_access:1014
may_access: may_access:1019
may_access: may_access:1024
may_access: may_access:1029
cgmanager.jodh:do_create_main: pid 12565 (uid 32011 gid 32011) may not create under /run/cgmanager/fs/freezer

-- 
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:
  New
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