[Bug 849954] Re: FFe: enable flicker-free boot with lightdm

[Launchpad Bug Tracker]

This bug was fixed in the package plymouth - 0.8.2-2ubuntu26

---------------
plymouth (0.8.2-2ubuntu26) oneiric; urgency=low

  * Add direct dependency on ttf-dejavu-core since that's the font used in
    the initramfs-tools hook, instead of trusting that fontconfig-config
    pulls in the right alternative.  LP: #828027.
  * debian/initramfs-tools/scripts/init-bottom/plymouth: /run doesn't get
    moved to ${rootmnt}/run until *after* our script has run, so don't try
    to check for it before calling plymouth update-root-fs - it's not like
    we would ever want to not pivot root, anyway.  Fixes the fact that we
    haven't been getting /var/log/boot.log for months now.
  * debian/plymouth.plymouth-stop.upstart: if stopped by lightdm, let
    lightdm handle the VT transition as it's able, so we get flicker-free
    boot.  LP: #849954.
 -- Steve Langasek <steve.langasek at ubuntu.com>   Mon, 19 Sep 2011 10:56:55 -0700

** Changed in: plymouth (Ubuntu Oneiric)
       Status: New => 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/849954

Title:
  FFe: enable flicker-free boot with lightdm

Status in The Ubuntu Flicker-Free Boot Project:
  New
Status in “plymouth” package in Ubuntu:
  Fix Released
Status in “plymouth” source package in Oneiric:
  Fix Released

Bug description:
  I have recently vetted the lightdm plymouth handling code to confirm
  that it is capable of a flicker-free hand-off from plymouth in the
  same way that gdm was.  We should have updated plymouth pre-beta to
  turn on flicker-free handling; since this didn't get done, this is now
  a freeze exception request.

  This is an important part of the Ubuntu desktop boot experience, and
  not having it enabled constitutes a regression from natty, so I think
  a freeze exception is warranted.  However, since lightdm has been the
  default DM for much of the oneiric cycle, we've not been getting any
  testing of the flicker-free code path in plymouth or the DRM drivers
  so there's definitely some risk of regression from turning it on as
  well.  As such, I don't believe we should enable this in the archive
  until the plymouth change has been tested with at least one system
  each of the intel, nouveau, and radeon drivers, both with and without
  cryptsetup installed (due to cryptsetup's effect of pulling plymouth
  into the initramfs, resulting in an earlier start).

  I have personally tested this with the intel+cryptsetup case only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-flicker-free-boot/+bug/849954/+subscriptions