[Bug 1850978] [NEW] Signed version of grub will result in failure of boot without a separated non-encrypted boot partition
Pejman Rezaei
1850978 at bugs.launchpad.net
Fri Nov 1 19:19:53 UTC 2019
Public bug reported:
Hi
I use Ubuntu 18.04.3
Further than the 1727956 bug, ubiquity installs the signed version of grub. If I want to install Ubuntu with just two partitions (ESP and a luks container which includes the root partition) and don't create any separated boot partition (neither encrypted nor non-encrypted), the signed version of grub will result in a non bootable system and is not compatible with this config. I checked all needed configs (crypttab, luks module in /etc/default/grub) and installed non-signed version of grub which is compatible with this config and working correctly. Also tested on other Linux distros.
Here the problem is the signed version of grub. For more info on this
scenario, you can take a look at this page which approves this problem.
http://www.chinnodog.com/ubuntu/ubuntu-fde-boot/
** Affects: grub2-signed (Ubuntu)
Importance: Undecided
Status: New
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Tags: grub luks lvm ubiquity
** Summary changed:
- Signed version of grub will result in failure of boot without a separated non-encrypted boot boot partition
+ Signed version of grub will result in failure of boot without a separated non-encrypted boot partition
** Also affects: grub2-signed (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1850978
Title:
Signed version of grub will result in failure of boot without a
separated non-encrypted boot partition
Status in grub2-signed package in Ubuntu:
New
Status in ubiquity package in Ubuntu:
New
Bug description:
Hi
I use Ubuntu 18.04.3
Further than the 1727956 bug, ubiquity installs the signed version of grub. If I want to install Ubuntu with just two partitions (ESP and a luks container which includes the root partition) and don't create any separated boot partition (neither encrypted nor non-encrypted), the signed version of grub will result in a non bootable system and is not compatible with this config. I checked all needed configs (crypttab, luks module in /etc/default/grub) and installed non-signed version of grub which is compatible with this config and working correctly. Also tested on other Linux distros.
Here the problem is the signed version of grub. For more info on this
scenario, you can take a look at this page which approves this
problem.
http://www.chinnodog.com/ubuntu/ubuntu-fde-boot/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1850978/+subscriptions
More information about the foundations-bugs
mailing list