[Bug 1235231] Re: plymouth loses output to /dev/console (such as ci-info: messages)

Launchpad Bug Tracker 1235231 at bugs.launchpad.net
Fri Apr 4 00:43:53 UTC 2014


This bug was fixed in the package plymouth - 0.8.8-0ubuntu16

---------------
plymouth (0.8.8-0ubuntu16) trusty; urgency=medium

  [ Steve Langasek ]
  * Fix debian/patches/tty1-after-boot.patch: when we have multiple
    non-default console options on the kernel commandline,
    local_console_terminal will not be set, so we should avoid the resulting
    assert.  LP: #1160079, LP: #1235231.

  [ Dimitri John Ledkov ] LP: #1292458
  * debian/patches/use-upstart-private-socket.patch: instead of using
    system dbus, use private upstart socket in the plymouth-upstart-bridge.
  * debian/plymouth.plymouth-upstart-bridge.upstart: start
    plymouth-upstart-bridge on startup, and thus gather a more complete
    boot.log.
  * debian/patches/dont-bail-on-dummy-terms.patch: don't bail
    plymouth-upstart-bridge if TERM is not set and/or running on a dummy
    terminal, as we can run on those. This makes console-log useful in
    lxc-containers and actually contain messages from upstart jobs
    starting and stopping.
  * debian/patches/no-print-empty-description.patch: do not store
    description when dbus returns empty string, and thus stop printing
    empty "Starting... done" messages. LP: #1185560.
  * debian/plymouth.plymouth-upstart-bridge.upstart: update stop on
    conditions to stop when plymouth-shutdown finishes.
  * Make ubuntu-logo theme support scale factor, provide one plymouth
    theme with scale 1 and another with scale 2, until scale factor can be
    dynamically detected.
  * Mark plymouth-upstart-bridge to respawn.
 -- Dimitri John Ledkov <xnox at ubuntu.com>   Thu, 03 Apr 2014 16:37:29 +0100

** Changed in: plymouth (Ubuntu)
       Status: Confirmed => Fix Released

-- 
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:
  Fix Released
Status in “plymouth-disabler” 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