Comment 19 for bug 980917

good! anyway better than a crowd decided to change init etc with _no_
knowledge at all

On Thu, Jul 26, 2012 at 8:24 PM, Steve Langasek <
<email address hidden>> wrote:

> James has taken a crack at this and found it to appear not to be
> unintrusive, or at least not tractable in time for .1. Postponing to
> .2.
>
> ** Changed in: upstart (Ubuntu Precise)
> Milestone: ubuntu-12.04.1 => ubuntu-12.04.2
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/980917
>
> Title:
> Failed to create pty - disabling logging for job
>
> Status in “upstart” package in Ubuntu:
> Triaged
> Status in “upstart” source package in Precise:
> Triaged
>
> Bug description:
> I believe this bug is in Upstart due to similar bug that was recently
> fixed:
>
> - https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/936667
>
> I am booting Ubuntu 12.04 LTS (x86) as a domU under Xen. After the
> previous bug was fixed, I still received the errors but the system now
> boots which is an improvement. During the boot process I see a few
> combinations of this error:
>
> ====
> init: Failed to create pty - disabling logging for job
> init: Temporary process spawn error: No such file or directory
> ====
>
> After those two stop, I see a few more of these errors:
>
> ====
> init: Failed to create pty - disabling logging for job
> ====
>
> The above error also prints if I type "poweroff" or "shutdown"
>
> This system's ultimate destiny is to operate using a custom-compiled
> Linux kernel that does not exist on the filesystem. Both the Ubuntu-
> supplied Linux kernel and the custom-compiled Linux kernel are
> afflicted by this bug.
>
> Any suggestions would be greatly appreciated.
>
> -Tim
>
> //edit: added more details, edited for clarity.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/980917/+subscriptions
>