touch-packages team mailing list archive

[James Hunt <1381075@xxxxxxxxxxxxxxxxxx>]

brian has pointed out that changing /usr/share/apport/kernel_oops isn't
necessary; apport now has a generic pipe program in the form of
/data/bzr/apport/apport/data/recoverable_problem.

We will need to make minor changes to the recoverable_problem utility
since it currently requires a pid but in this scenario we don't have one
- the process that upstart has been respawning is no longer running (and
we don't want apport using the pid of upstart).

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

Title:
  [ubuntu-touch] upstart should report applications that hit respawn
  limit to errors.ubuntu.com

Status in “apport” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  New

Bug description:
  We have important system and session services that we rely on being
  running and functional.

  If such a component hits the upstart respawn limit for any reason, we
  should be able to get a report that something is seriously wrong.

  Inspiration for this bug as per the discussion in:
  https://bugs.launchpad.net/ubuntu/+source/indicator-
  network/+bug/1371320

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