[Bug 1235231] Re: plymouth loses output to /dev/console (such as ci-info: messages)
Scott Moser
smoser at ubuntu.com
Mon Nov 25 16:31:09 UTC 2013
Theres a plea for review/accept at http://irclogs.ubuntu.com/2013/11/25/%23ubuntu-devel.html#t14:18 that is met with 2 questions:
a.) why isn't this in plymouth package (because slangasek requested it not be)
b.) why isn't this in cloud-init package (because its not at all related to cloud-init)
Rbasak mentioned that disabling plymouth does have fallout, for example
lightdm is 'start on started plymouth'. Other upstart jobs on my system
that mention plymouth are:
$ grep -r plymouth /etc/init -l | grep -v "/plymouth"
/etc/init/console-font.conf
/etc/init/lightdm.conf
/etc/init/failsafe.conf
/etc/init/setvtrgb.conf
/etc/init/mountall.conf
/etc/init/friendly-recovery.conf
lightdm and failsafe are the ones that seem most worrysome there.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1235231
Title:
plymouth loses output to /dev/console (such as ci-info: messages)
Status in The Plymouth splash screen:
Confirmed
Status in “cloud-init” package in Ubuntu:
Confirmed
Status in “plymouth” package in Ubuntu:
Confirmed
Bug description:
During early boot, plymouth captures writes to /dev/console. As I
understand it, it is supposed to re-play that content later. Whether
or not it intends to is not the issue. In our cloud-images (and in
other cases) users may write data to /dev/console that needs to be
seen on the other side (ie a serial logger or 'get-console-ouptput'
api call).
See the attached 'my-logger.conf' for an upstart job that simply
writes data early in boot to /dev/console. Sometimes data "lost" is
available in /var/log/boot.log, but sometimes it doesn't even seem to
make it there. bug 682831 has an attachment 'myhack-init' that does a
similar thing but starts outputting by replacing /sbin/init and then
calling /sbin/init itself.
Related bugs:
* bug 682831: lost console output early in boot
== Original bug report ==
On precise cloud images, I get a console output line like this:
ci-info: eth0 : 1 192.168.122.204 255.255.255.0 52:54:00:7f:d8:ca^M
On saucy cloud images, this is missing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/plymouth/+bug/1235231/+subscriptions
More information about the foundations-bugs
mailing list