[Bug 1880250] Autopkgtest regression report (plymouth/0.9.4git20200323-0ubuntu6.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted plymouth (0.9.4git20200323-0ubuntu6.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/245.4-4ubuntu3.2 (arm64)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#plymouth

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1880250

Title:
  Ctrl-C message displayed without any actual disk check

Status in plymouth package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in plymouth source package in Focal:
  Fix Committed
Status in systemd source package in Focal:
  Confirmed
Status in plymouth source package in Groovy:
  Fix Released
Status in systemd source package in Groovy:
  Confirmed

Bug description:
  [Impact]

   * fsck messages is shown by plymouth, despite all fscks already
  completed.

  [Test Case]

   * Install Ubuntu Desktop with full disk encryption

   * Observe that fsck messages (press ctrl+c) is shown, and remains
  there on screen for a little while as plymouth transitions to gdm

   * After installing the update, observe that when fsck completes the
  messages are cleared and the transition to gdm is done without
  fsck/ctrl+c message present.

   * After this change lands in -updates, and daily desktop images are
  built with this, double check that casper-md5sum transition is also
  smooth.

  
  [Regression Potential] 

   * plymouth spinner theme is adjusted to clear the footer, at the end
  of fsck, even if systemd-fsckd didn't do that. At the moment there are
  two consumers of the fsck apis systemd-fsckd & casper-md5sum used on
  installed systems and live-isos respectively. If something else pushes
  messages to the footer, they might get cleared at the end of fsck.

  [Other Info]
   
   * Original bug report

  It seems the transition to bgrt lost something with Ubuntu's disk
  check details. The only thing I see on my screen during a long disk
  check is the "press Ctrl-C to stop all in progress disk checks" with
  no progress.

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