Bug 18638 - Request for grub graphical gets grub2 graphical
Summary: Request for grub graphical gets grub2 graphical
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2016-06-06 16:21 CEST by Frank Griffin
Modified: 2016-06-17 11:14 CEST (History)
2 users (show)

See Also:
Source RPM: drakx-installer-stage2-17.34-1.mga6
CVE:
Status comment:


Attachments
do not override bootloader on upgrade (mga#18638) (940 bytes, patch)
2016-06-08 16:59 CEST, Thierry Vignaud
Details | Diff

Description Frank Griffin 2016-06-06 16:21:42 CEST
I did a fresh install and took the default bootloader setting for the MBR without realizing that the default had changed from grub to grub2.  I redid the install as an upgrade, and when I got to the summary screen I configured bootloader again as grub-graphical on the MBR.  It said "Installing Bootloader", but when I rebooted I had grub2 again.
Comment 1 Rémi Verschelde 2016-06-06 16:26:43 CEST
This is not a bug but a feature, grub-legacy is being dropped for new installs as it does not support ext4 filesystems formatted with e2fsprogs-1.43 (see bug 18583).

CC: (none) => thierry.vignaud

Comment 2 Rémi Verschelde 2016-06-06 16:27:56 CEST
Though grub-legacy should still be supported for upgrades of existing systems, so it might be still considered a bug that it was proposed but installed grub2 instead.

But Thierry just pushed many changes in this regard so it might be fixed already in drakx 17.34.1.
Comment 3 Thierry Vignaud 2016-06-06 16:42:32 CEST
Yes, you'd better test latest drakx 17.34.1 (I guess you tried 17.33 as patched by Anne?)
Normally it *should* work as intended but I mostly focused on fixing/improving grub2 support.

Keywords: (none) => NEEDINFO

Comment 4 Frank Griffin 2016-06-06 16:55:13 CEST
I had just updated cauldron this morning, and the version there is drakx-installer-stage2-17.34-1.mga6.x86_64.rpm.

Two comments: if we're not going to give it to him, it shouldn't be in the dropdown list; or better still, choosing it from the dropdown list should give a popup saying why it's not available.  Was this discussed at all on the ML ?
Marja Van Waes 2016-06-08 14:40:19 CEST

CC: (none) => marja11
Assignee: bugsquad => thierry.vignaud
Source RPM: (none) => drakx-installer-stage2-17.34-1.mga6

Comment 5 Thierry Vignaud 2016-06-08 16:59:00 CEST
please attach your /root/drakx/report.bug.xz
Comment 6 Thierry Vignaud 2016-06-08 16:59:29 CEST
Created attachment 7952 [details]
do not override bootloader on upgrade (mga#18638)

Please try this patch
Comment 7 Frank Griffin 2016-06-08 17:21:45 CEST
Will do as soon as my in-flight fresh install completes.

Just to be clear, the previous install was a fresh install.  I can't recall whether the default bootloader choice was grub-graphical or grub2-graphical; I just assumed it was grub-graphical and left it unchanged.  When I saw the grub2 menu on boot, I redid the install as an upgrade, and this time explicitly chose grub-graphical in Summary, but at reboot it was still grub2.  So it wasn't the case that I was doing an upgrade to an existing grub system.
Comment 8 Mageia Robot 2016-06-09 16:26:00 CEST
commit 538bd80652dfae4e45bdfb3e54892929262daa29
Author: Thierry Vignaud <thierry.vignaud@...>
Date:   Wed Jun 8 16:58:12 2016 +0200

    do not override bootloader on upgrade (mga#18638)
---
 Commit Link:
   http://gitweb.mageia.org/software/drakx/commit/?id=538bd80652dfae4e45bdfb3e54892929262daa29
Comment 9 Thierry Vignaud 2016-06-17 11:14:14 CEST
Presumed fixed

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


Note You need to log in before you can comment on or make changes to this bug.