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
09:11:55
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
Verification-done on trusty with grub2 2.02~beta2-9ubuntu1.16 /
grub2-signed 1.34.18:
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
This bug was fixed in the package shim-signed - 1.33.1~16.04.3
---
shim-signed (1.33.1~16.04.3) xenial; urgency=medium
* debian/control: Depends: on grub2 2.02~beta2-36ubuntu3.20 to ensure shim
cannot be installed without the new grub2 version that fixes chainloading
issues.
Hello Peter, 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
https:
Verification-done with shim-signed in xenial-proposed:
ii shim-signed 1.33.1~16.04.3+15+1 amd64
Secure Boot chain-loading bootloader (Microsoft-signed binary)
I've checked that a Secure Boot-enabled system correctly validates the
shim binary that gets installed to disk, that it
Hello Peter, or anyone else affected,
Accepted shim-signed into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/shim-
signed/1.33.1~16.04.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
h
This bug was fixed in the package grub2-signed - 1.66.20
---
grub2-signed (1.66.20) xenial; urgency=medium
* Rebuild against grub2 2.02~beta2-36ubuntu3.20. (LP: #1792575)
grub2-signed (1.66.19) xenial; urgency=medium
* Rebuild against grub2 2.02~beta2-36ubuntu3.19. (LP: #1785033
Autopkgtests failures for ubuntu-image appear to be unrelated, the tests
show the machine has already booted at that point -- this is some kind
of other networking issue post-boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu3.20
---
grub2 (2.02~beta2-36ubuntu3.20) xenial; urgency=medium
* debian/patches/linuxefi_fix_relocate_coff.patch: fix typo in
relocate_coff() causing issues with relocation of code in chainload.
(LP: #1792575)
*
Verification-done with the xenial grub2/grub2-signed versions:
$ dpkg -l grub\* | grep ii
ii grub-common 2.02~beta2-36ubuntu3.20 amd64GRand
Unified Bootloader (common files)
ii grub-efi-amd642.02~beta2-36ubuntu3.20 amd64GRand
Unified Bootloader
Hello Peter, 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.20 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
** Tags added: id-5b36ccda18d5e26eda679909
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792575
Title:
Boot failure with efi shims from 20180913.0
To manage notifications about this bug go to:
htt
This bug was fixed in the package grub2 - 2.02-2ubuntu8.6
---
grub2 (2.02-2ubuntu8.6) bionic; urgency=medium
* debian/patches/linuxefi_fix_relocate_coff.patch: fix typo in
relocate_coff() causing issues with relocation of code in chainload.
(LP: #1792575)
* debian/patches/
This bug was fixed in the package grub2-signed - 1.93.7
---
grub2-signed (1.93.7) bionic; urgency=medium
* Rebuild against grub2 2.02-2ubuntu8.6 (LP: #1792575)
grub2-signed (1.93.6) bionic; urgency=medium
* Rebuild against grub2 2.02-2ubuntu8.5 (LP: #788298)
-- Mathieu Trudel-
This bug was fixed in the package shim-signed - 1.37~18.04.2
---
shim-signed (1.37~18.04.2) bionic; urgency=medium
* debian/control: add Breaks: grub-efi-amd64-signed (<< 1.93.7), as the new
version of shim exercises a bug in relocation code for chainload that was
fixed in t
Looks good to me here; I was able to have Windows 10 chainload from
grub2 2.02-2ubuntu8.6 / grub2-signed 1.93.7.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Peter checked (I asked him, since they have hardware that clearly
exhibits the issue) and it looks like this is a verification-done:
grub2 2.02-2ubuntu8.6
grub2-signed 1.93.7
I still have to do a quick check with Windows 10 to make sure that
aspect of the fix also works correctly, and that shim-s
I'm also unable to verify the fix using the MAAS CI. However I did
confirm the new shim works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792575
Title:
Boot failure with efi shims from 20180913.
Could repro the orig. issue and verify the fix works. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792575
Title:
Boot failure with efi shims from 20180913.0
To manage notifications about
I can't seem to be able to reproduce this problem (after testing again)
on a VM, so I'll need help to reproduce the bug, and then to validate
the fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: shim-signed (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792575
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2-signed (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792575
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792575
Title:
Not a bug in shim, but we are adding a Breaks in shim-signed for the
purposes of SRUs to avoid people upgrading into a broken state. As such,
the task for cosmic in Invalid; but absolutely in progress / committed
for other releases.
** Changed in: shim-signed (Ubuntu)
Status: New => Invalid
This does not appear to be a bug in shim at all, closing the shim tasks
as Invalid.
** Changed in: shim (Ubuntu)
Status: New => Invalid
** Changed in: shim (Ubuntu)
Assignee: Canonical Foundations Team (canonical-foundations) =>
(unassigned)
** Changed in: shim (Ubuntu Xenial)
Hello Peter, or anyone else affected,
Accepted grub2 into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/grub2/2.02-2ubuntu8.6
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.
** Description changed:
+ [Impact]
+ Chainloading grub via grub in a netboot context using MAAS's Boot to local
disk feature.
+
+ [Test cases]
+ 1) Deploy UEFI system using MAAS
+ 2) After deployment, have the system reboot to local disk (via netboot).
+
+ [Regression potential]
+ It is possibl
This bug was fixed in the package grub2-signed - 1.106
---
grub2-signed (1.106) cosmic; urgency=medium
* Rebuild against grub2 2.02+dfsg1-5ubuntu4. (LP: #1792575)
-- Mathieu Trudel-Lapierre Mon, 17 Sep 2018
08:47:45 -0400
** Changed in: grub2-signed (Ubuntu)
Status: New
This bug was fixed in the package grub2 - 2.02+dfsg1-5ubuntu4
---
grub2 (2.02+dfsg1-5ubuntu4) cosmic; urgency=medium
* debian/patches/linuxefi_fix_relocate_coff.patch: fix typo in
relocate_coff() causing issues with relocation of code in chainload.
(LP: #1792575)
-- Mathie
** Also affects: grub2-signed (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792575
Title:
Boot failure with efi shims from 20180913.0
To manage
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792575
Title:
Boot failure with efi shims from 20180913.0
To manage notifi
** Tags added: id-5b9c1dc8ce84408c14c66e7e
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792575
Title:
Boot failure with efi shims from 20180913.0
To manage notifications about this bug go to:
htt
Since the shim change has been reverted, I'm unsubscribing field-
critical.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792575
Title:
Boot failure with efi shims from 20180913.0
To manage notifi
** Changed in: shim (Ubuntu)
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792575
Title:
Boot failure with efi shi
Marking this as invalid for MAAS> Once this issue is fixed and SRU'd to
Xenial, it will be rolled out automatically.
In the meantime, the bootloaders have been reverted from the archive,
and from the MAAS image repositories.
** Changed in: maas
Status: New => Invalid
--
You received this
Hi, that would be those:
$ dpkg -l | grep grub-efi
ii grub-efi-amd642.02~beta2-36ubuntu3.18
amd64GRand Unified Bootloader, version 2 (EFI-AMD64 version)
ii grub-efi-amd64-bin2.02~beta2-36ubuntu3.18
am
So, the patch would apply, but you're not seeing the error messages that
I expect you should be seeing if that was the problem. We can certainly
try to apply the patch (I will make it available in a PPA), but I'm not
sure that will help.
For one thing, you are using the same grub in both cases, an
The package versions we need are for grub-efi-amd64 and grub-efi-
amd64-signed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792575
Title:
Boot failure with efi shims from 20180913.0
To manage no
Just to provide some more context
1. Machines were deployed with Xenial and bootloders from image streams
version 20180906, which was using an older shim (versions as per "a"
below)
2. The shim has been updated in the ubuntu archive for cosmic and
bionic, but for xenial they still in -proposed (n
40 matches
Mail list logo
