Open benbullard79 opened 1 year ago
This may be related to file system type. I saw this on systems using F2FS. Recently I Re-installed Cooker using XFS and do not see this issue. I do not believe users using EXT4 are seeing this but am not sure.
I am going to close this. As far as I can tell this is an issue only for those using f2fs
who also are multi-booting. I am a multi-booter and in OMLx right now I do not use btrfs
or f2fs
because they do not work well in multi-boot scenario for me. ext4
which most folks probably use and xfs
both work OK in multi-boot scenario. Does not seem like this is where we want to spend our resources at this time.
I am using f2fs
mostly for systems on my desktop and this issue is still present.
OpenMandriva version: Cooker and ROME
Describe the bug: When boot system is using
f2fs
the last booted entry does not become the defaultSteps to reproduce: You need a multi-boot computer. Install either Cooker or ROME using
f2fs
for / partition and in spite of settings in/etc/default/grub
the Grub2 default is always the first entry in grub2 menu on the boot-loader system.Observed behavior: In spite of settings in
/etc/default/grub
the Grub2 default is always the first entry in grub2 menu on the boot-loader system.Expected behavior: Last booted entry should become the default.
Additional comment: These lines are present in
/etc/default/grub
:Have also tried:
GRUB_SAVEDEFAULT=true
Logs and screenshots if relevant
grub.txt
grub.cfg.txt