[Bug 1292458] Re: [FFe] a bunch of updates to plymouth

[Steve Langasek]

Hello Dimitri, or anyone else affected,

Accepted plymouth into trusty-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/plymouth/0.8.8-0ubuntu16 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

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

Title:
  [FFe] a bunch of updates to plymouth

Status in “plymouth” package in Ubuntu:
  New

Bug description:
  * 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.
  * 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.

  
  This results in following improvements:
  * more complete /var/log/boot.log (e.g. from startup event, not just from dbus event)
  * now generates a /var/log/boot.log in the LXC containers
  * does not print empty/pointless " * Starting/Stopping" messages (e.g. those generated by startpar bridge)
  * ubuntu-logo theme now supports a scalingfactor, it's not auto-detected or user-adjustable, but there is an alternative theme with scaling factor 2, which one can choose to use with update-alternatives

  I believe we need/want all of those improvements for 14.04 LTS.

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