This bug was fixed in the package grub2 - 2.02~beta2-9ubuntu1.16
---
grub2 (2.02~beta2-9ubuntu1.16) trusty; urgency=medium
[ Ivan Hu ]
* debian/patches/0001-i386-linux-Add-support-for-ext_lfb_base.patch:
Add support for ext_lfb_base. (LP: #1785033)
[ dann frazier ]
* Add
This bug was fixed in the package grub2-signed - 1.34.18
---
grub2-signed (1.34.18) trusty; urgency=medium
* Rebuild against grub-efi-amd64 2.02~beta2-9ubuntu1.16
(LP: #1785033) (LP: #1642298) (LP: #1696599) (LP: #1792575)
-- Mathieu Trudel-Lapierre Wed, 09 Jan 2019
Verification-done for trusty for grub2 and grub2-signed:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Hello Mathieu, or anyone else affected,
Accepted grub2 into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/grub2/2.02~beta2-9ubuntu1.16 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: grub2 (Ubuntu Trusty)
Status: Won't Fix => In Progress
** Changed in: grub2-signed (Ubuntu Trusty)
Status: Won't Fix => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think we'll need to backport the UEFI Secure Boot patches to trusty
after all -- there's a large number of changes in them, but it seems
better than attempting to adapt other patches (such as Windws 7/10
chainloading fixes with new shim, and memory truncation fixes). Having
the patchset at the
Superseded by LP: #1708245 for trusty.
** Changed in: grub2 (Ubuntu Trusty)
Status: New => Won't Fix
** Changed in: grub2-signed (Ubuntu Trusty)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu3.12
---
grub2 (2.02~beta2-36ubuntu3.12) xenial; urgency=medium
* debian/patches: Rework linuxefi/SecureBoot support and sync with upstream
SB patch set: (LP: #1696599)
- linuxefi_backport_arm64.patch: backport
This bug was fixed in the package grub2-signed - 1.66.12
---
grub2-signed (1.66.12) xenial; urgency=medium
* Rebuild against grub2 2.02~beta2-36ubuntu3.12. (LP: #1696599)
-- Mathieu Trudel-Lapierre Wed, 14 Jun 2017
14:39:30 -0400
--
You received this bug
Finally got to verifying this for chainloading as well, on both xenial
and zesty -- marking xenial as verification-done now.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of
This bug was fixed in the package grub2 - 2.02~beta3-4ubuntu2.2
---
grub2 (2.02~beta3-4ubuntu2.2) zesty; urgency=medium
* debian/patches: Rework linuxefi/SecureBoot support and sync with upstream
SB patch set: (LP: #1696599)
- linuxefi_arm_sb_support.patch: add Secure Boot
This bug was fixed in the package grub2-signed - 1.80.2
---
grub2-signed (1.80.2) zesty; urgency=medium
* Rebuild against grub2 2.02~beta3-4ubuntu2.2. (LP: #1696599)
-- Mathieu Trudel-Lapierre Wed, 14 Jun 2017
14:46:59 -0400
** Changed in: grub2-signed
** Changed in: grub2-signed (Ubuntu Yakkety)
Status: Fix Committed => Won't Fix
** Changed in: grub2 (Ubuntu Yakkety)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Verification-done for zesty with grub2 2.02~beta3-4ubuntu2.2 and
grub2-signed 1.80.2:
Booting in insecure mode, with Secure Boot enabled and with SB disabled
(but UEFI enabled) have been tested and all work as expected.
** Tags removed: verification-needed-zesty
** Tags added:
** Tags removed: verification-failed
** Tags added: verification-needed-xenial verification-needed-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696599
Title:
backport/sync UEFI, Secure
Verification-done for xenial with grub2 2.02~beta2-36ubuntu3.12 and
grub2-signed 1.66.12:
Booting behaves correctly with Secure Boot enabled or disabled; and when
Secure Boot is enabled but shim validation is disabled. Booting in the
chainload case could not be tested (I do not have a Windows key
Hello Mathieu, or anyone else affected,
Accepted grub2-signed into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/grub2-signed/1.66.12 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Mathieu, or anyone else affected,
Accepted grub2 into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/grub2/2.02~beta2-36ubuntu11.4 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Mathieu, or anyone else affected,
Accepted grub2 into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/grub2/2.02~beta2-36ubuntu3.12 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
I've updated the description to make the rationale clearer. This is a
general backport of the patchset coming from "upstream" (in this case,
being the "UEFI community" instead of GNU GRUB, and personified in this
git tree from fedora), which include changes such as:
- general cleanup and fixes
** Description changed:
[Impact]
- Since the implementation of UEFI Secure Boot in Ubuntu, there has been a
large number of changes to the EFI patchset, handled "upstream" at
https://github.com/vathpela/grub2-fedora/tree/sb. This is a complex set of
enablement patches across a number of
Just to be clear, what is the purpose of this backport? As you know,
“upstream has done more work” isn't usually justification for an SRU :)
Presumably this is expected to fix bugs and/or support new systems?
Could you give a brief run-down of what this fixes/newly supports?
--
You received
Updating status to clarify that this is already uploaded and included in
the artful release.
** Changed in: grub2-signed (Ubuntu Artful)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
23 matches
Mail list logo