[Bug 1780897] Re: Installation failure on UEFI systems with SecureBoot disabled

[Łukasz Zemczak]

Yes, this dropped from my radar completely. The dependency chain change
required us to make installer-related changes (in both grub-installer
and ubiquity) that made sure the right packages aren't purged from the
system. But what I did miss is adding the new deps to the grub2-signed
package in case someone would be pulling in the new grub packages from
the archive during installation.

So actually the bug here is that *old* images are failing to install on
UEFI systems when automatic download of updates is switched on. This is
why it was not noticed - I only tested the changes on both the dailies
for bionic and cosmic.

** Summary changed:

- Installation failure on UEFI systems with SecureBoot disabled
+ Installation failure on UEFI systems using older images with automatic download of updates enabled

** Changed in: grub2-signed (Ubuntu Bionic)
       Status: Triaged => In Progress

** Changed in: grub2-signed (Ubuntu Cosmic)
       Status: Triaged => In Progress

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

Title:
  Installation failure on UEFI systems using older images with automatic
  download of updates enabled

Status in grub2-signed package in Ubuntu:
  In Progress
Status in grub2-signed source package in Bionic:
  In Progress
Status in grub2-signed source package in Cosmic:
  In Progress

Bug description:
  Regression caused by
  https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1778848

  Steps to reproduce

  1) Install ubuntu-18.04-desktop-amd64.iso in a VM using QEMU and OVMF
  2) Reboot the VM
  3) See GRUB shell instead of GDM

  The system can be rescued by running

  configfile (hd0,gpt2)/boot/grub/grub.cfg

  at the GRUB shell

  Installing grub-efi-amd64 in the rescued system then makes it
  bootable.

  
  Previously grub-efi-amd64-signed depended on grub-efi-amd64, and the system was bootable immediately after installation.

  Additionally, the removal of this dependency has resulted in a very
  sparse /etc/default/grub after installation.

  I've attached a simple script for installation with QEMU and OVMF.

  I suspect that installs are broken on actual hardware with SecureBoot
  disabled, but I'm not able to test that right now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1780897/+subscriptions