[Bug 1528345] Re: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order

2024-04-26 Thread Launchpad Bug Tracker
[Expired for One Hundred Papercuts because there has been no activity for 60 days.] ** Changed in: hundredpapercuts Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1528345] Re: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order

2024-04-26 Thread Launchpad Bug Tracker
[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: grub2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528345

[Bug 1528345] Re: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order

2024-02-26 Thread Mate Kukri
This seems to have been an update publication issue in a version of Ubuntu that is no longer supported (14.10), I don't think there is bug described here that still exists. I am setting this to "Incomplete" to give some time for anyone to confirm being affected by this, I am also downgrading

[Bug 1528345] Re: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order

2019-07-24 Thread Brad Figg
** Tags added: cscc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528345 Title: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order To manage

[Bug 1528345] Re: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order

2019-01-28 Thread Steve Langasek
** Changed in: grub2 (Ubuntu) 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/1528345 Title: grub or kernel update broke Secure Boot by putting grubx64.efi instead

[Bug 1528345] Re: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order

2019-01-28 Thread carmelo
** Changed in: grub2 (Ubuntu) Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528345 Title: grub or kernel update broke Secure Boot by putting grubx64.efi instead

Re: [Bug 1528345] Re: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order

2018-12-28 Thread Steve Langasek
On Thu, Dec 27, 2018 at 08:25:41PM -, bokateeka wrote: > Try https://sourceforge.net/u/yannubuntu/ > Dual Boot repair disk Please do nothing of the sort. This "repair disk" is developed with zero coordination with the Ubuntu developers and the resulting changes to the disk are unsupportable

[Bug 1528345] Re: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order

2018-12-27 Thread bokateeka via ubuntu-bugs
Try https://sourceforge.net/u/yannubuntu/ Dual Boot repair disk https://sourceforge.net/projects/boot-repair-cd/files/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528345 Title: grub or

Re: [Bug 1528345] Re: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order

2016-01-07 Thread Steve Langasek
On Thu, Jan 07, 2016 at 07:14:48PM -, Marc Deslauriers wrote: > Wouldn't the grub2 package simply be held back if the proper version > required by grub2-signed isn't available? Not in all cases. > Why did the grub2-signed binary package get uninstalled during the > update? This is allowable

Re: [Bug 1528345] Re: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order

2016-01-06 Thread Steve Langasek
On Thu, Jan 07, 2016 at 03:59:30AM -, Seth Arnold wrote: > Will users that have only the -security pocket enabled run into this > issue until we publish a corresponding grub2-signed package into the > -security pocket? Yes. > Can the packages in -updates in wily, vivid, and trusty be

[Bug 1528345] Re: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order

2016-01-06 Thread Seth Arnold
Will users that have only the -security pocket enabled run into this issue until we publish a corresponding grub2-signed package into the -security pocket? Can the packages in -updates in wily, vivid, and trusty be binarycopied into the -security pocket? What steps need to be taken to publish

[Bug 1528345] Re: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order

2016-01-05 Thread planet
** Tags added: kernel-fs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528345 Title: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order To

[Bug 1528345] Re: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order

2016-01-05 Thread Brian Murray
** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528345 Title: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot

[Bug 1528345] Re: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order

2016-01-05 Thread Steve Langasek
This appears to have been caused by the publication of a grub2 security update on 12/15 without the corresponding grub2-signed package being published at the same time. We have had similar issues in the past with publication of grub2 and grub2-signed to the -updates pockets; the proposed solution

[Bug 1528345] Re: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order

2016-01-04 Thread Alberto Salvia Novella
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: grub2 (Ubuntu) Status: Confirmed => Triaged -- You received this bug

[Bug 1528345] Re: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order

2016-01-01 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: grub2 (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/1528345 Title:

[Bug 1528345] Re: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order

2016-01-01 Thread Alberto Salvia Novella
** Changed in: grub2 (Ubuntu) Importance: Undecided => Critical ** Also affects: hundredpapercuts Importance: Undecided Status: New ** Changed in: hundredpapercuts Status: New => Confirmed ** Changed in: hundredpapercuts Importance: Undecided => Critical -- You received