The reported regressions are all fixed, and I have finished validating
reboots in the autopkgtest-cloud.
We are still unable to secure boot on arm64 (bug 1954683). But as this
is not strictly a regression (the userspace grub-check-signatures always
failed and prevented installation of grub, now ad
Hi Julian,
I have tested grub 2.06-2ubuntu3 in both BIOS and EFI mode on VMs, and I
can confirm that your patches have fixed both of the issues I was
seeing.
Thanks for the quick turnaround! I will keep testing these packages, but
it all seems good under secureboot.
Thanks,
Matthew
--
You rece
I can confirm the issue with the VM. Enabling debugging makes things
work again (set debug=all), which is sad. Needs further investigation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953490
Title:
Hi Julian, Derk,
I have been testing grub2-2.06-2ubuntu2 in -proposed in KVM, on both
BIOS and EFI VMs, and both appear to be broken.
On BIOS, grub2 doesn't get installed automatically, so I have to
manually run "grub-install /dev/vda". When I do, I reboot into grub
2.06, and upon selecting a ker
filed bug #1954566
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953490
Title:
keep grub 2.06 in proposed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gr
FYI Jammy-proposed testing issues
grub-efi-amd64-bin/jammy-proposed,now 2.06-2ubuntu2 amd64 [installed]
GRand Unified Bootloader, version 2 (EFI-AMD64 modules)
grub-efi-amd64-signed/jammy-proposed,now 1.175+2.06-2ubuntu2 amd64 [installed]
GRand Unified Bootloader, version 2 (EFI-AMD64 versio
