[Bug 1096531] Re: After touch /forcefsck and reboot: Assertion failed in log_clear_unflushed

[Launchpad Bug Tracker]

This bug was fixed in the package upstart - 1.6.1-1ubuntu2

---------------
upstart (1.6.1-1ubuntu2) raring; urgency=low

  [ Stéphane Graber ]
  * Call autoreconf so we can use the same packaging for snapshots as for
    release tarballs. Add depends on dh-autoreconf and autopoint.

  [ James Hunt ]
  * init/log.c: Cherry-pick of upstream fix for jobs which end before
    the log disk becomes writeable and which spawn off additional
    processes which persist after the main job process has ended
    (LP: #1096531).
 -- James Hunt <james.hunt at ubuntu.com>   Tue, 22 Jan 2013 15:18:30 +0000

** Changed in: upstart (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1096531

Title:
  After touch /forcefsck and reboot: Assertion failed in
  log_clear_unflushed

Status in Upstart:
  Fix Committed
Status in “upstart” package in Ubuntu:
  Fix Released

Bug description:
  I made a copy of raring-server-cloudimg-amd64-disk1.img, launched in
  KVM on my 12.10 system, updated all the packages on it and then
  rebooted it after touching /forcefsck.  Even though its a clean
  reboot, it still core dumpes.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: upstart 1.6.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
  Uname: Linux 3.7.0-7-generic x86_64
  ApportVersion: 2.7-0ubuntu2
  Architecture: amd64
  Date: Sun Jan  6 06:39:07 2013
  MarkForUpload: True
  ProcEnviron:
   TERM=screen
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1096531/+subscriptions