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.
So, some more information.. plymouth* ; do sudo mv $x $x.disabled; done
this bug is "fixed" by doing:
for x in /etc/init/
after doing so 100% of /dev/console output makes it to the console (whoohoo!).
that lays this squarely on plymouth. irclogs. ubuntu. com/2013/ 10/04/% 23ubuntu- devel.html# t18:07 .
There is some conversation with slangasek, smoser and utlemming at
http://
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.