[Bug 1843483] Re: Setting an alternative UEFI Folder name when installing GRUB causes it to be stuck in 'Minimal Bash-like Editing' mode

feren zuaroos at outlook.com
Tue Sep 10 19:28:04 UTC 2019


** Summary changed:

- Setting an alternative UEFI ID causes GRUB to be in 'Minimal Bash-like Editing' mode
+ Setting an alternative UEFI Folder name when installing GRUB causes it to be stuck in 'Minimal Bash-like Editing' mode

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1843483

Title:
  Setting an alternative UEFI Folder name when installing GRUB causes it
  to be stuck in 'Minimal Bash-like Editing' mode

Status in grub2 package in Ubuntu:
  New

Bug description:
  Info:
  Ubuntu Release: Ubuntu 18.04
  grub-efi-amd64-bin: 2.02-2ubuntu8.13

  I originally reported this to Calamares, because of the fact it
  affected Feren OS and Feren OS was the original place I found this
  issue happen, but whenever a custom ID for GRUB is set that isn't
  'ubuntu' it will result in GRUB being always in Minimal Bash-like
  Editing is Supported mode.

  Reproduction Steps:
  1. Delete everything in /boot/efi/EFI including folders to make a clean slate (excluding Windows EFI Directories if they're there, they won't change anything)
  2. Do `grub-install /dev/sda --uefi-secure-boot --bootloader-id=efifoldername` in Terminal with 'efifoldername' being any folder name that isn't 'ubuntu'.
  3. Restart the system

  What was expected:
  GRUB would boot normally even with a different EFI folder ID

  What actually happened:
  GRUB booted into Minimal Bash-like Editing is Supported unless the ID is explicitly set to 'ubuntu'.

  Additional Notes:
  I also proceeded to do extra tests before reporting this issue in Terminal on the affected machine:
  'grub-install /dev/sda --uefi-secure-boot --bootloader-id=feren' Resulted in broken GRUB (Feren OS's EFI folder name since this bug was first noticed by me through Feren OS using a different EFI directory name)
  'grub-install /dev/sda --uefi-secure-boot --bootloader-id=ubuntu' Resulted in working GRUB
  'grub-install /dev/sda --uefi-secure-boot --bootloader-id=testlabel' Resulted in broken GRUB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1843483/+subscriptions



More information about the foundations-bugs mailing list