touch-packages team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxxxxx>]

This is not a bug in upstart itself, upstart is behaving by design.  If
these initctl calls are blocking the boot but should not, then the jobs
should be changed to call with the --no-wait argument as you found.  If
the initctl calls need to block the boot but are failing to return, the
bug is in whatever is failing to run to completion.

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

Title:
  ofono does not start after upgrade (initclt stalls when sending an
  event)

Status in Canonical System Image:
  Confirmed
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  Some times, on first boot after either using ubuntu-device-flash or
  upgrading the phone via OTA, some processes do not start because
  initctl seems to stall and does not send events that trigger the
  launch of those processes. For instance, I see in my arale:

  $ ps -ef | grep initclt
  root       742   563  1 08:25 ?        00:00:00 initctl emit android
  root      1826   746  0 08:25 ?        00:00:00 initctl emit rild-ready OFONO_RIL_DEVICE=mtk OFONO_RIL_NUM_SIM_SLOTS=1

  and "ofonod" is not started because "rild-ready" is not emitted.

  A second boot solves the issue and I do not see any initctl process
  still executing after some seconds.

  This bug can certainly scare people when they see that they do not
  have telephony just after an OTA.

  I have reproduced in

  $ system-image-cli -i
  current build number: 80
  device name: arale
  channel: ubuntu-touch/devel-proposed/meizu.en
  last update: 2015-08-03 08:24:54
  version version: 80
  version ubuntu: 20150802
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480785/+subscriptions