[Bug 1865959] Re: plymouth hook hangs waiting for input

[Dave Jones]

On Wed, 4 Mar 2020 at 01:15, Steve Langasek <steve.langasek at canonical.com>
wrote:

> Why is the default.plymouth alternative not set up on the rpi images?
> Are no theme packages installed?
>

The plymouth-theme-ubuntu-text package is installed, but that doesn't seem
to provide any "alternative"; i.e. update-alternatives --query
default.plymouth just spits out "error: no alternatives for
default.plymouth". I'm not familiar enough with plymouth to know whether
that's intended or not; our boot on the Pi (for classic at least) has
always been the usual verbose kernel+init output, though it might be worth
looking into changing that at some point.

Nonetheless, I'd argue the script should still check that THEME_PATH isn't
empty before attempting to grep with it so we don't hang in the middle of
an upgrade.

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

Title:
  plymouth hook hangs waiting for input

Status in The Ubuntu-power-systems project:
  New
Status in plymouth package in Ubuntu:
  Fix Committed

Bug description:
  In the fix for LP: #1864586 the following change was made:

   THEME_PATH="$(update-alternatives --query default.plymouth 2>/dev/null | sed -e '/^Value:/!d' -e 's/^Value: \(.*\)/\1/')"
  +IMAGE_PATH=$(grep "ImageDir *= *" ${THEME_PATH} | sed 's/ImageDir *= *//')
   THEME="$(basename ${THEME_PATH:-none} .plymouth || true)"
   THEMES="/usr/share/plymouth/themes"

  Unfortunately, if the default.plymouth alternative is not set (as is
  the case in the Raspberry Pi images for instance), then THEME_PATH
  winds up blank. The introduced IMAGE_PATH line then hangs waiting for
  input (as grep isn't given a filename to read).

  I ran into this during an "apt upgrade" (which called update-
  initramfs, and thus the plymouth hook) on a focal pi image; worked
  around it by hitting Ctrl+D to let it continue, which allowed
  everything to proceed as normal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1865959/+subscriptions