[Bug 1303815] Re: cloud image boot produces unnecessary output

[Dimitri John Ledkov]

So i've reproduced this on a normal desktop, even with a previous
plymouth (so behaviour is not a regression as far as i can tell so far)

over e.g. ssh connection
1) stop lightdm; start plymouth in shutdown mode
2) start plymouth-upstart-bridge
3) press esc to get messages/console instead of splash
4) restart a job, e.g. restart cups

Starting/stopping plymouth bridge messages are printed, followed by the
upstart job name.

Next i've set "console log" on plymouth-upstart-bridge, and
started/stopping messages went away to /var/log/upstart/plymouth-
upstart-bridge.log, however the naked upstart job name was still printed
to the console.

Stopping plymouth-upstart-bridge makes the messages go away. I'm still
trying to trace if it's plymouthd or plymouth-upstart-bridge spewing
things onto the console.

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

Title:
  cloud image boot produces unnecessary output

Status in “plymouth” package in Ubuntu:
  In Progress
Status in “plymouth” source package in Trusty:
  In Progress

Bug description:
  This is a regression in the most recent upload of plymouth (that fixed bug 1160079)
  We're now seeing annoyingly verbose output like this:

  Begin: Running /scripts/local-bottom ... done.
  done.
  Begin: Running /scripts/init-bottom ... done.
  [    4.113876] random: init urandom read with 70 bits of entropy available
   * Starting Mount filesystems on boot^[[74G[ OK ]
  mountall
   * Starting Populate /dev filesystem^[[74G[ OK ]
   * Starting Populate and link to /run filesystem^[[74G[ OK ]
   * Stopping Populate and link to /run filesystem^[[74G[ OK ]
  mounted-dev
  mounted-run
   * Stopping Populate /dev filesystem^[[74G[ OK ]
  startpar-bridge
  mounted-run
   * Stopping Track if upstart is running in a container^[[74G[ OK ]
  startpar-bridge
  mounted-dev
  startpar-bridge
  container-detect
  startpar-bridge

  It seems like there is even duplicate data going there, as you can see the multiple 'mounted-dev' output.
  I'm attaching a full log also.

  Related bugs:
   * bug 682831: lost console output early in boot
   * bug 1160079:  plymouth aborts in cloud images 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: plymouth 0.8.8-0ubuntu16
  ProcVersionSignature: User Name 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDmesg: [   18.108817] init: plymouth-upstart-bridge main process (194) killed by TERM signal
  Date: Mon Apr  7 13:36:16 2014
  DefaultPlymouth: Error: command ['readlink', '/etc/alternatives/default.plymouth'] failed with exit code 1:
  Ec2AMI: ami-61b3a108
  Ec2AMIManifest: ubuntu-us-east-1/images-testing/ubuntu-trusty-daily-amd64-server-20140407.manifest.xml
  Ec2AvailabilityZone: us-east-1e
  Ec2InstanceType: m3.medium
  Ec2Kernel: aki-919dcaf8
  Ec2Ramdisk: unavailable
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
  ProcCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0
  SourcePackage: plymouth
  TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1303815/+subscriptions