Bug 18294

Summary:	Installing kernel update in M6dev1 changes grub2 default boot option
Product:	Mageia	Reporter:	Herman Viaene <herman.viaene>
Component:	RPM Packages	Assignee:	Kernel and Drivers maintainers <kernel>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	zen25000
Version:	Cauldron	Keywords:	6dev1, 6sta1
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Herman Viaene 2016-04-29 09:27:34 CEST

Description of problem:
Laptop with UEFI and M6dev1-64 installed. The laptop has M5 as grub2 default boot option, Windows 10 is also in the grub2 menu.
When the regular updating involves a kernel update, the M6 puts itself as the default boot option.


Version-Release number of selected component (if applicable):


How reproducible:
Happened on each (two) kernel updates I remember.

Steps to Reproduce:
1.
2.
3.

Herman Viaene 2016-04-29 09:28:07 CEST

Keywords: (none) => 6dev1

Comment 1 Herman Viaene 2016-05-04 14:42:41 CEST

In sta1, it is now the opposite: UEFI installation respects the default boot option, but on a legacy BIOS laptop, the defauly gets overwritten with the M6 installation.

Keywords: (none) => 6sta1

Comment 2 Herman Viaene 2016-06-01 14:16:31 CEST

By keeping M6sta1 updated (kernel updates involved), the problem switches sides. At updating my x86-64 UEFI laptop with kernel-desktop 4.6.0-2, the grub2 default option was again overwritten. The same update on my old legacy BIOS laptop left the grub2 default option intact.

Comment 3 Barry Jackson 2016-06-01 17:45:04 CEST

I think there is possibly confusion here between the grub2 menu in Mga5 and the one in Mga6 as they both currently look the same.

May I suggest that you install grub2-mageia5-theme-dejavu in Mageia5 so you can tell which menu you are looking at. (This one uses dejavu font rather than the 'Mageia' font)

I suspect that possibly what you may be seeing is not the boot order in one menu changing, but the Mga5 menu being replaced by the Mga6 menu?

I think also that comments about the other PC-BIOS machine should be left totally out of this bug report as it will confuse the issue.

CC: (none) => zen25000

Comment 4 Marja Van Waes 2016-08-26 12:48:55 CEST

Mass-reassigning all bugs with "kernel" in the summary that are still assigned to tmb (or wrongly assigned to someone with "tmb" in his e-mail address) to the kernel packagers group, but without adding "kernel" to the SRPM field.

Please reassign if needed, or add kernel to the SRPM field if this is correct.

Assignee: knightmb => kernel

Comment 5 Herman Viaene 2019-02-19 16:54:38 CET

This issue seems to be gone since the EOL of M5.

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