[Bug 1355617] Re: "plymouth ask-for-password" unable to read keyboard input on Xen PV console (hvc0)

Daniel van Vugt 1355617 at bugs.launchpad.net
Thu Apr 28 02:42:30 UTC 2022


Ubuntu 14.04 (trusty) reached end of standard support in April 2019:

  https://wiki.ubuntu.com/Releases

If you would like to continue with free support then please update to a
newer Ubuntu version and tell us if the problem still occurs.

If you would like to continue with Ubuntu 14.04 then there is a paid
support option detailed at https://www.ubuntu.com/esm


** Changed in: plymouth (Ubuntu)
       Status: Confirmed => Won't Fix

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

Title:
  "plymouth ask-for-password" unable to read keyboard input on Xen PV
  console (hvc0)

Status in plymouth package in Ubuntu:
  Won't Fix

Bug description:
  "plymouth ask-for-password" is unable to read keyboard input when the
  console is the Xen PV console device (hvc0).

  Since the "cryptroot" script that the "cryptsetup" package installs on
  initramfs's uses "plymouth ask-for-password" instead of
  /lib/cryptsetup/askpass if plymouth is available, this causes the boot
  process to hang at the password prompt when trying to boot with an
  encrypted root device that needs the operator to type the password on
  the console.

  As a very hacky workaround, modifying /usr/share/initramfs-
  tools/scripts/local-top/cryptroot to always use
  /lib/cryptsetup/askpass if $cryptkeyscript is not set (see attached
  patch) and then regenerating the initramfs with "update-initramfs -u"
  works as expected.

  Specifying /lib/cryptsetup/askpass as the "keyscript=" using the
  kernel command line ("cryptopts=") and/or /etc/crypttab didn't work
  for whatever reason, but I didn't spend a whole lot of time trying to
  figure out why.

  Some relevant system information:

  Ubuntu 14.04 (Trusty) on an amd64 Xen domU

  The system was debootstrap'd under Finnix on a VM supplied by
  Linode.com.

  cryptsetup 2:1.6.1-1ubuntu1 amd64
  linux-image-3.13.0-33-generic 3.13.0-33.58 amd64
  linux-image-virtual 3.13.0.33.39 amd64
  linux-virtual 3.13.0.33.39 amd64
  plymouth 0.8.8-0ubuntu17 amd64

  kernel command line: root=/dev/mapper/crypt-root console=hvc0 ro

  contents of /etc/crypttab:

  # <target name> <source device> <key file>      <options>
  crypt-swap      /dev/xvdb       /dev/urandom    swap,cipher=aes-xts-plain64,size=256,hash=sha512
  crypt-root      /dev/xvdc       none            rootdev,luks

  contents of /etc/fstab:

  # <source device>         <mount point>   <fs type>  <mount options>
  /dev/xvda                 /boot           ext4       defaults
  /dev/mapper/crypt-swap    none            swap       defaults
  /dev/mapper/crypt-root    /               ext4       errors=remount-ro
  none                      /proc           proc       defaults

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




More information about the foundations-bugs mailing list