https://bugs.kde.org/show_bug.cgi?id=369077
David Izquierdo <da...@izquierdofernandez.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |da...@izquierdofernandez.co
| |m
--- Comment #6 from David Izquierdo <da...@izquierdofernandez.com> ---
I just stumbled with this issue after clearing an ESP because of a windows
reinstall. Since there was no /EFI/ubuntu directory, grub only booted into its
shell. Running `set` in the GRUB shell showed that $prefix (the variable from
which grub knows where to load its actual config file from) is indeed hardcoded
to /EFI/ubuntu, but EFI/ubuntu is never created once it goes away.
My suggestion to work-around this issue is to either override the grub2-common
package with a wrapper for grub-install that will `cp -rf
/boot/efi/EFI/{neon,ubuntu}`, or to use /boot/efi/EFI/ubuntu in the first
place. Otherwise, the expectation that grub-install fixes the bootloader is
broken.
Unless we can actually get secure-boot working for our grub, that is.
--
You are receiving this mail because:
You are watching all bug changes.
