On Xenial dev version now and this bug is showing up again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469995
Title:
grub-efi-amd64-signed Forced Uninstall Causes Boot Failure
To manage
Thank you very much
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469995
Title:
grub-efi-amd64-signed Forced Uninstall Causes Boot Failure
To manage notifications about this bug go to:
This happened again on December 10. I am going to try and keep my
computer on and hope that the signed version is released asap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469995
Title:
DaytonaJohn (daytonajra), where did you copy the signed grubx64.efi to?
Was it to /usr/lib/grub? Thanks for any help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469995
Title:
Copied it to /boot/efi/EFI/ubuntu/grubx64.efi
On 12/10/2015 07:27 PM, Bill Miller wrote:
> DaytonaJohn (daytonajra), where did you copy the signed grubx64.efi to?
> Was it to /usr/lib/grub? Thanks for any help.
>
--
You received this bug notification because you are a member of Ubuntu
Bugs,
You should be able to fix this by either:
1) Not agreeing to remove grub-efi-amd64-signed but instead waiting for
an update for it (and filing a bug pointing out that it is unavailable
as appropriate) - but of course I appreciate that users don't magically
know this and shouldn't have to.
2)
Just a bit more information. The secure boot fails because these updates
replace the signed grubx64.efi with an unsigned version. I copied a
signed grubx64.efi from a backup (overwriting the one from the updates),
and now my secure boot is working correctly again.
--
You received this bug
Outch! Thanks for the report, I just stop before dist-upgrading. Hope
the bogus dependence will be fixed soon to avoid lots's of end-users
support!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: grub2-signed (Ubuntu)
Status: Confirmed = Triaged
** Changed in: hundredpapercuts
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469995
I should also add that it looks to be forced to be removed because
grub-efi-amd64 was updated to:
2.02~beta2-22ubuntu1.1
vs
2.02~beta2-22ubuntu1 which is what grub-efi-amd64-signed
(1.46+2.02~beta2-22ubuntu1) depends on.
--
You received this bug notification because you are a member of Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2-signed (Ubuntu)
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/1469995
Title:
Also it seems to be impossible to force the old 2.02~beta2-22ubuntu1
version, at least on Synaptic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469995
Title:
grub-efi-amd64-signed Forced
I had to run from shell:
sudo apt-get --reinstall install grub-efi-amd64=2.02~beta2-22ubuntu1
grub-efi-amd64-bin=2.02~beta2-22ubuntu1 grub-common=2.02~beta2-22ubuntu1
grub2-common=2.02~beta2-22ubuntu1 grub-efi-amd64-signed
sudo apt-mark hold grub-efi-amd64 grub-efi-amd64-bin grub-common
** Changed in: grub2-signed (Ubuntu)
Importance: Undecided = High
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
** Changed in: hundredpapercuts
Status: New = Confirmed
** Changed in: hundredpapercuts
Importance: Undecided = Critical
** Changed in:
14 matches
Mail list logo
