Comment 24 for bug 1120660

Has this been fixed? I seem to be affected by this bug, yet I cannot update upstart to the newest version, as it triggers kernel panic when it's configured. I also cannot boot up with the --no-log option, because this causes a kernel panic immediately when the system begins to boot. I would welcome ideas on how to upgrade upstart while omitting the configuring phase, or getting around the kernel panic in some other way.

Should I report a new bug, or is it actually the same as this one, and it's just my system that cannot upgrade?