[Bug 1926972] Re: Xubuntu with LUKS FDE hangs upon boot after Hirsute upgrade

[yitzhaq]

Apologies for the delayed follow-up to this.
No, booting from any other medium works fine. I also got further in figuring out under what circumstances this happens, and it appears to be EFI-related.

So if I bring up the boot media menu on boot, and manually choose the
Ubuntu EFI partition (the only one), the system actually boots fine. But
if I don't do this, and let it go to default, the problem consistently
happens. I am not using Secure Boot (it's not supported by the system),
and as mentioned I'm running the last BIOS available for this model.
Tinkering with booting in legacy/BIOS mode has not been successful, and
manually choosing Ubuntu EFI from the boot menu is currently the only
way I've found to get the system to successfully boot.

I have tried everything I can think of to rectify this, including
completely reinstalling GRUB according to Boot-Repair's recommendations,
but to no avail.

Here's the output of Boot-Repair, which also did not fix the problem:

https://paste.ubuntu.com/p/jVvMSWwGxn/

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

Title:
  Xubuntu with LUKS FDE hangs upon boot after Hirsute upgrade

Status in cryptsetup package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Hirsute, I'm unable to boot my Xubuntu laptop with
  LUKS FDE. It was working fine on Groovy, and I have made no changes
  besides upgrading.

  The system now hangs on boot. Nothing is displayed (completely black
  screen, no passphrase prompt,  no cursor, nothing), and the keyboard
  does not respond (not even Caps Lock). This does not appear to be the
  reported known Xubuntu issue about having to press ESC (once or twice)
  to see the password prompt; as mentioned, the keyboard does not appear
  to respond at all. I have also confirmed that this is not #1915579, as
  the installed lvm2 version includes the fix, and I have manually
  confirmed that /usr/share/initramfs-tools/hooks/lvm2 is 755.

  /etc/crypttab looks fine as far as I can tell, and nothing complained
  during upgrade. I have tried doing dpkg-reconfigure (and apt-get
  install --reinstall) against grub-pc, initramfs-tools, cryptsetup and
  the latest installed kernel, to no avail. No complaints from any of
  that either.

  ~ # cat /etc/crypttab 
  sda4_crypt UUID=<my-uuid-is-listed-here> none luks,discard

  All package versions are current as of writing (including hirsute,
  hirsute-updates, hirsute-security). The volume mounts fine when
  booting from installation media.

  Not sure which package to report this against, as I don't know where
  the problem is located.

  HW in case it matters (though I doubt it) is a Lenovo ThinkPad X220
  running latest BIOS (1.46), with Samsung 860 EVO S-ATA. BIOS is
  configured with "Legacy first", rather than UEFI.

  Any help greatly appreciated.

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