Bug 32165

Can you say when this problem appeared for you? 'Regression' suggests that it worked better previously: what is your setup? Cauldron system, or recent M9 installation? EFI?) what has changed?
 $ rpm -q --last grub2
should indicate whether/when Grub2 has been updated recently.

I agree about the other bug referenced.

CC: (none) => lewyssmith

(In reply to Lewis Smith from comment #1)
> Can you say when this problem appeared for you? 'Regression' suggests that
> it worked better previously: what is your setup? Cauldron system, or recent
> M9 installation? EFI?) what has changed?

I can't be sure if the bug is not present previous to mga 8 to 9 migration , is a BIOS machine, maybe or may be not is due to a update because i usually use rpmnew files as main file when the update applet ask for action  

>  $ rpm -q --last grub2
> should indicate whether/when Grub2 has been updated recently.
> 
rpm -q --last grub2
grub2-2.06-27.mga9.x86_64                     mié 17 may 2023 14:34:32

LC_ALL=C rpm -q --last grub2
grub2-2.06-27.mga9.x86_64                     Wed May 17 14:34:32 2023


> I agree about the other bug referenced.

I just consider this regression because is a behaviour previously reported as fixed

Can we understand that you experience this problem after upgrading an MBR/BIOS machine from M8 to M9? And that you did not see it before the upgrade?

(In reply to Lewis Smith from comment #3)
> Can we understand that you experience this problem after upgrading an
> MBR/BIOS machine from M8 to M9? And that you did not see it before the
> upgrade?

Yes, but only because i decide to boot with old kernel, a think that i don't usually do, so i can't say that the issue is not present on mageia 8.

Since some versions ago my systems are mageia only so i don't have to boot other system, and i don't remember i suffer of issues related to kernel, so as i say before run a old kernel is not a think that do regularly

Still valid on recent grub2 update
LC_ALL=C rpm -q --last grub2
grub2-2.06-28.mga9.x86_64                     Fri Aug 11 16:05:58 2023

Source RPM: grub2-2.06-27.mga9.src.rpm => grub2-2.06-27.mga9.src.rpm,grub2-2.06-28.mga9.src.rpm

This has been the default behaviour for new installs since 2016 - see bug 18560.

To prevent the saved entry being automatically updated, edit /etc/default/grub and change

  GRUB_SAVEDEFAULT=true

to

  GRUB_SAVEDEFAULT=false

Then you can either use drakboot or the command grub2-set-default to set the default menu entry and it will persist.

CC: (none) => mageia

(In reply to Martin Whitaker from comment #6)
> This has been the default behaviour for new installs since 2016 - see bug
> 18560.
> 
> To prevent the saved entry being automatically updated, edit
> /etc/default/grub and change
> 
>   GRUB_SAVEDEFAULT=true
> 
> to
> 
>   GRUB_SAVEDEFAULT=false
> 
> Then you can either use drakboot or the command grub2-set-default to set the
> default menu entry and it will persist.

Then we need a errata to inform about this

Keywords: (none) => FOR_ERRATA8, FOR_ERRATA9

Please check https://wiki.mageia.org/en/Mageia_9_Errata#Boot , i add this bug to section, if you like i backport to Mageia 8

Why does this need to be in errata? As pointed out by Martin this is standard behaviour. It is even standard behaviour on other major distributions like openSUSE!

(In reply to sturmvogel from comment #9)
> Why does this need to be in errata? As pointed out by Martin this is
> standard behaviour. It is even standard behaviour on other major
> distributions like openSUSE!

If not in Errata in Release Notes but i think must be informed in somewhere, 
so we avoid the user expect to boot in a expected default option and if don't take attention ends in other previously selected boot option. Even in the errata we can add that is a expected behaviour due is the standard.

For the moment i enhance the note in the Errata, i let in your hands the decision of Move to Release Notes or erase the note.

This follow our kind and helpful habit of explaining for users about things that may be unexpected even if so by design.  Design is often about taste anyway.

CC: (none) => fri
Keywords: FOR_ERRATA8, FOR_ERRATA9 => IN_ERRATA8, IN_ERRATA9

And it is not a bug.

Resolution: (none) => WORKSFORME
Status: NEW => RESOLVED

drakboot allows you to select the default entry without indicating that this is for the next boot only, so it is a bit misleading. It would be a useful enhancement to add an extra checkbox to enable/disable the GRUB_SAVEDEFAULT setting.

Good idea

Status: RESOLVED => REOPENED
Resolution: WORKSFORME => (none)
Severity: normal => enhancement
Status comment: (none) => Suggestion in comment 14