Marking as invalid, as this was not related to the TPM or module signing
issues we have seen, and the reporter found the problem on crypttab.
Thank you.
Cascardo.
** Changed in: linux (Ubuntu Eoan)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu)
Status: Confirmed =>
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Eoan)
Status: New => Confirmed
** Changed in: linux (Ubuntu Eoan)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
I did some investigation. It seems that in /etc/crypttab, the third
column of the encrypted disk does points to a key file, and the content
of the key file is the passphrase.
Not sure why this is created, but I've previously used Ubuntu's disk
utility to change the passphrase of my root disk,
It seems that after I performed certain updates, I could not even boot
the system with 5.3.0-18 kernel now, which seems to suggest the problem
might not originate from the kernel itself.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Thanks for the report, Shaform. There are a few other bug reports
against 5.3.0-22 and we're trying to understand if there's a common
link. It looks like you're using LUKS/dm-crypt to do full disk
encryption of your root partition so we're waiting to hear if that's
common throughout the other
** Description changed:
Ubuntu cannot boot if using kernel version 5.3.0-19 & 5.3.0-22.
However, kernel version 5.3.0-18 works fine.
The root disk is encrypted. When booting with 5.3.0-18, a passsphrase
input field is displayed during boot. However, such an input field does
not
6 matches
Mail list logo
