[Bug 1450783] Re: grub-install with --bootloader-id option creates unusable boot configuration with secure boot

2024-06-17 Thread Mate Kukri
The way this works on core.efi+modules based installs is that the
installer modifies core.efi with a path to grub.cfg.

This cannot be done in signed images, as that obviously invalidates the
signature.

It would make sense to change upstream GRUB to have a feature that is
"please load config from same directory as EFI executable" is an option,
but I don't believe this to be the case.

I think this should be contributed upstream.

** Changed in: grub2 (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  grub-install with --bootloader-id option creates unusable boot
  configuration with secure boot

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1450783] Re: grub-install with --bootloader-id option creates unusable boot configuration with secure boot

2021-02-10 Thread Eugene Seppel
I need to have two Ubuntu installations on my PC, and spent several hours in 
vain because of this bug reported 5 years ago -- needed to boot 10 times from 
liveusb to figure out what is wrong.
Please prioritize it!

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

Title:
  grub-install with --bootloader-id option creates unusable boot
  configuration with secure boot

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1450783] Re: grub-install with --bootloader-id option creates unusable boot configuration with secure boot

2020-03-29 Thread Ed A
grub-install --bootloader-id=customfoldername # <-- this is exactly what
I wanted

it didn't work for me at first, but then I found this:
https://askubuntu.com/questions/1129269/install-grub-using-custom-boot-
loader-id-e-g-myubuntu - "... After running grub-install with
--bootloader-id, run grub-install without any arguments. It will create
an ubuntu entry. Delete it if you want to, but now your id is going to
work "magically". Very annoying, seems to be an old bug. Hope I helps."

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

Title:
  grub-install with --bootloader-id option creates unusable boot
  configuration with secure boot

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1450783] Re: grub-install with --bootloader-id option creates unusable boot configuration with secure boot

2019-03-28 Thread mr calvin
Another similar bug report 1247933

Im my case I have had big issues installing "new" hard disks or even USB
flash drives, which also have the equal hardcoded "ubuntu" bootloader-
id, and as you then have several disk with the same ID you have problems
booting. As a main rule you should be able to name your bootloader
something rather unique for each installation so future HDD mix want
cause boot problems. Calling them all the same is in my experience a bad
practice.

I really this could be fixed/up-prioritized.

I know time is limited resource for everybody, but having an option
"--bootloader-id" that actually doesn't work for how many years is
really critisable. At least remove the option from the documentation if
knowone plan to fix it in the near future. A lot a people might waste a
lot of time, I did for sure!

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

Title:
  grub-install with --bootloader-id option creates unusable boot
  configuration with secure boot

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1450783] Re: grub-install with --bootloader-id option creates unusable boot configuration with secure boot

2015-09-16 Thread Fred Palmer
I changed GRUB_DISTRIBUTOR so I could tell which install was which.
I have my main working 14.04LTS install on sda, but install other test installs 
on sdb.
I try to install grub to ESP - efi system partition on sdb and installer even 
says installing to sdb. But it always installs to sda.
I then try renaming so I can keep them separate in UEFI.

All of these are grubx64.efi with different grub.cfg with  different configfile 
entries for different UUIDs.
/efi/BOOT/bootx64.efi 
/efi/trusty/grubx64.efi 
 /efi/ubuntu/grubx64.efi 
 /efi/vivid/grubx64.efi 

But they all use the one grub.cfg in /efi/ubuntu.

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

Title:
  grub-install with --bootloader-id option creates unusable boot
  configuration with secure boot

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1450783] Re: grub-install with --bootloader-id option creates unusable boot configuration with secure boot

2015-05-04 Thread Mathieu Trudel-Lapierre
This sound like a variant of bug 1242417.

Are you only directly calling grub-install --bootloader-id=myid ? Are
you setting GRUB_DISTRIBUTOR elsewhere as well?

GRUB_DISTRIBUTOR would be set in /etc/default/grub at the very least and
would likely interfere with how/where things get installed as well.

That said, I also see that /EFI/ubuntu is hardcoded in efi images; I
just haven't found exactly how from a quick look at grub2.

Marking is Triaged/Low; this won't be an issue for most people, we
appropriately handle "usual" installations. It probably still needs to
get fixed so that --bootloader-id works as expected, but bug 1242417 had
some reasons for being fixed the way it was and I'll need to talk to
Colin and/or Steve.

** Changed in: grub2 (Ubuntu)
   Status: New => Triaged

** Changed in: grub2 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  grub-install with --bootloader-id option creates unusable boot
  configuration with secure boot

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs