upstart produces no boot log for bricked machines
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: upstart
Karmic packages installed over the past few days produce many boot errors which fail to be logged anywhere.
There are many threads relating to upstart requiring the upstart-logd compat package to provide boot and shutdown logging.
These logs are essential for debugging boot and shutdown problems.
Maybe these logs can be shut off in final releases.
Both these logs should be turned on during development otherwise developers are reduced to multiple reboots trying to quickly write down errors as they flash across the screen.
Whoever is maintaining upstart will serve us all by auto installing the required packages and turning on logging for both boot and shutdown during Karmic development.
Please post an update about how to manually enable boot and shutdown logging so current boot problems causing bricked machines after last few days of Karmic package updates can be identified and fixed before tomorrow's next Alpha release.
summary: |
- upstart produces no boot log + upstart produces no boot log for bricked machines |