So, some more information.. this bug is "fixed" by doing: for x in /etc/init/plymouth*; do sudo mv $x $x.disabled; done
after doing so 100% of /dev/console output makes it to the console (whoohoo!). that lays this squarely on plymouth. There is some conversation with slangasek, smoser and utlemming at http://irclogs.ubuntu.com/2013/10/04/%23ubuntu-devel.html#t18:07 . Steve thinks its not entirely unreasonable to just disable plymouth via .override files in cloud-images. I think he would suggest that that be done at the package level and be handled by cloud-init. That wasn't clear to me though. Given the above, this is clearly a plymouth bug, its supposed to replay output that it captured, but it is losing some. ** Package changed: upstart (Ubuntu) => plymouth (Ubuntu) ** Changed in: plymouth (Ubuntu) Status: New => Confirmed ** Changed in: plymouth (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1235231 Title: plymouth loses output to /dev/console (such as ci-info: messages) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1235231/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
