Get rid of Grub bootnext entries

If you have Grub then you might have noticed that,after an update,there are a few new entries with bootnext in it.

These entries do nothing and are only a result of a bug in a new Grub feature.

You can get rid of these by putting this line in /etc/default/grub :

GRUB_DISABLE_BOOTNEXT=true

then open a terminal and do one off the following: (as root)
update-grub
or
grub-mkconfig -o /boot/grub/grub.cfg /etc/default/grub

2 Likes

Bootnext is supposed to be a setting which determines which OS autoboots at the next reboot, for uefi boots only.
It should not need to appear in the grub menu … so yes, that is a bug.
I have not encountered it with my grub setup … it must be a new feature?

1 Like

It is a long time since we heard of any grub problems?
It used to be a regular thing on the forum.
Do you think maybe AI is taking over these sort of issues?

1 Like

What kind of bug is it? Does it cause a problem? Or is it some type of minor problem?

Gemini did not seem to believe this was a bug.

3 Likes

The GRUB 2.16 manual says GRUB_DISABLE_BOOTNEXT stops grub-mkconfig from generating bootnext menu entries and disables the 31_efi_bootnext script. Does the upstream documentation distinguish that from whether firmware honors an already-set BootNext value? That seems worth checking before deciding whether the entries are a bug or intended behavior, or changing boot settings based on the forum claim.

AI assisted; checked against the GRUB manual.

2 Likes

Well,bootnext can give you also an error when a new grub.cfg is made after an update.

With that error this cfg file is saved as grub.cf.new.

Not a real problem with removing the old one and rename the new file.

And if you have snapshots they will be included too

1 Like

Do you mean btrfs snapshots or Timeshift?

Renaming grub.cfg is a bug as far as I am concerned. … unless grub is altered to check for the new name?

1 Like

Thank you for giving proper reference.

1 Like