ubiquity's grub-installer script fails during installation of grub-efi-amd64-signed package
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I've encountered this bug during installation of KDE neon (uses Ubuntu 18.04 LTS as base system) on my computer, but it seems this bug is rather caused by the ubiquity package itself.
Steps to reproduce:
1. Have secure boot enabled in BIOS settings,
2. Start Ubuntu/etc installation in UEFI mode and with internet access,
3. Let the installer to download updates during installation,
4. Use manual partitioning to specify the root partition on the disk, where an EFI partition already exists.
What you expect to happen: The system is successfully installed on a secure boot enabled computer in EFI mode.
What happened instead: GRUB installation fails, thus the installation fails.
Details:
After the root filesystem is copied, the installer continues with other tasks such as apt update, user accounts management, grub installation, etc. but it failed every time during the bootloader installation stage.
By examining the syslog of live environment during installation, I have seen installation of grub-efi-
case "$grub_package" in
*)
# Will pull in os-prober based on global setting for Recommends
apt-install $grub_package || exit_code=$?
case $grub_package in
*-signed)
apt-install shim-signed || true
apt-install grub-pc || true
;;
esac
;;
esac
On my computer, the "apt-install $grub_package" command tries installing grub-efi-
Proposals for fixing the problem:
1. Modify /usr/share/
or,
2. Make shim-signed package a dependency for grub-efi-
I'm currently unavailable to attach any syslog files because I've already fixed the problem before installation and therefore my /var/log/
description: | updated |
Status changed to 'Confirmed' because the bug affects multiple users.