My attempt to target this bug was obviously in error. I meant to update
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1447756
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096531
Title:
** Changed in: upstart
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096531
Title:
After touch /forcefsck and reboot: Assertion failed in
** Changed in: upstart (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096531
Title:
After touch /forcefsck and reboot: Assertion failed in
Please don't mark ubuntu bugs as fix released, instead wait for the
package to build and migrate into -release pocket, then the bug should
get autoclosed from the changelog entry.
** Changed in: upstart (Ubuntu)
Status: Fix Released = Fix Committed
--
You received this bug notification
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
** Changed in: upstart
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096531
Title:
After touch /forcefsck and reboot: Assertion failed in
** Branch linked: lp:ubuntu/upstart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096531
Title:
After touch /forcefsck and reboot: Assertion failed in
log_clear_unflushed
To manage
Investigation shows that this problem is only triggered by '/forcefsck':
the actual problem results from jobs that satisfy both conditions below:
- *end* before /var/log/upstart/ becomes writeable.
- has spawned one or more processes that continue to run *after* the job has
finished and after
Work-arounds for this problem:
= Work-Around 1 =
Boot with '--no-log' on kernel command-line.
EFFECT: This will disable all job log output. This is potentially rather
extreme, so users may wish to use work-around 2 below.
= Work-Around 2 =
1) Boot with '--no-log' on kernel command-line.
2)
Thanks for reporting this issue Blair. I can confirm the problem is
recreatable using the i386 raring-server image.
** Changed in: upstart (Ubuntu)
Status: New = Confirmed
** Changed in: upstart (Ubuntu)
Importance: Undecided = High
** Changed in: upstart (Ubuntu)
Status:
The one issue with the KVM image is that it'll hang for 2 minutes upon
boot and not tell you its 'ubuntu' user password.
I can reproduce this using the daily server ISO:
- Download
rsync://cdimages.ubuntu.com/cdimage/ubuntu-server/daily/current/raring-server-amd64.iso
- Start VirtualBox
- Make
11 matches
Mail list logo
