Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#75862 - [grub] revert upstream bug which causes GRUB to reboot
Attached to Project:
Arch Linux
Opened by Felipe Contreras (felipec) - Saturday, 10 September 2022, 03:42 GMT
Last edited by Allan McRae (Allan) - Saturday, 10 September 2022, 06:23 GMT
Opened by Felipe Contreras (felipec) - Saturday, 10 September 2022, 03:42 GMT
Last edited by Allan McRae (Allan) - Saturday, 10 September 2022, 06:23 GMT
|
DetailsDescription:
The upstream bug caused a huge fuss since it prevented many Arch Linux systems from booting. The issue is caused by calling `fwsetup` carelessly, if the user calls `grub-mkconfig` without calling `grub-install` then `fwsetup --is-supported` is called, which immediately reboots the machine. There's no need for that since clearly versions of 30_uefi-firmware.in prior to 2022-08-18 worked just fine. There's no need to wait for upstream to revert their careless changes, we can do that ourselves. Patch attached. Additional info: * 2:2.06.r322.gd9b4638c5-4 * Upstream has acknowledged the problem: https://lists.gnu.org/archive/html/grub-devel/2022-08/msg00374.html |
This task depends upon
Closed by Allan McRae (Allan)
Saturday, 10 September 2022, 06:23 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#75701
Saturday, 10 September 2022, 06:23 GMT
Reason for closing: Duplicate
Additional comments about closing: