[Bug 936667] Re: Upstart early job logging causes boot failure for systems with no initramfs (error is "No available ptys")

[Turbéki András Rusztem]

Fox example, open a console/terminal, and write this line, and then press Enter:
sudo pico /boot/grub/grub.cfg
You can replace pico word with an other simple text editor(gedit).
Please enter your root/admin password, and then, please press Enter key, then locate with the keyboard arrows similar to this, and not the recovery copy of this, or an older version of this, with older version number! Verify, that the line begins with menuentry, what contains later in the line, and so locate the correct!
menuentry 'Ubuntu, Linux 3.2.0-24-generic verzióval' --class ubuntu --class gnu-linux --class gnu --class os {
	recordfail
	gfxmode $linux_gfx_mode
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='(hd0,msdos5)'
	search --no-floppy --fs-uuid --set=root f10afaa4-bb63-4de3-90d4-2cf3bae096c1
	linux	/boot/vmlinuz-3.2.0-24-generic root=/dev/sda5 rootfstype=ext4 ro   crashkernel=384M-2G:64M,2G-:128M quiet slient plymouth.enable=0
}
Write to the end of the line begins with linux, the --no-log flag, like this:
	linux	/boot/vmlinuz-3.2.0-24-generic root=/dev/sda5 rootfstype=ext4 ro   crashkernel=384M-2G:64M,2G-:128M quiet slient plymouth.enable=0 --no-log
Then press in pico(if You use this) Control+O, and then Control+X key combinations, then type into the console: exit, and then please press Enter!
Or in other text editor(that run with root/admin rights), please save the file, then close the editor!
Then please reboot Your computer, to verify!
Please don't modify other characters, if You write a mistake, please don't save with Control+O, or with other text editor, then close the text editor(the pico can close with Control+X), and don't save(in pico, please say No(the first character of Your languages No word), then restart from the console command line!
If you save a mistake, your computer will probably not boot at next time!
But, if your PC install kernel updates, this file will rebuilt, and this workaround must be reapplied, and also must reapply the disable of initrd, but, if You don't use initrd, i haven't a permanent workaround, because i'm also new to Ubuntu.
Sorry for my bad English!

-- 
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/936667

Title:
  Upstart early job logging causes boot failure for systems with no
  initramfs (error is "No available ptys")

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

Bug description:
  When booting 12.04 after a recent update, I see "init(4): no available
  ptys" being displayed faster than a machine gun. When I add --no-log
  as a kernel option and I'm able to boot just fine.

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