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

[Christian Bachmaier]

@seb128
Yes, it was definitively working before the update to 0.9.4git20200109-0ubuntu3.2 . The only thing I also changed was to remove the package libplymouth4 as it is no longer needed and not in the repo any more because of libplymouth5. Unfortunately, libplymouth4 was not autoremoved.

> apt-cache search libplymouth
libplymouth-dev - graphical boot animation and logger - development files
libplymouth5 - graphical boot animation and logger - shared libraries

So I believe this is not the reason...

-- 
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:
  Fix Committed
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