I find that the Boot Modify process in the MCC boot set up screen is not capable of changing the GRUB2 boot process. You can change the text or even check the "default" box and that does not change the way the boot loader reads. Seems to work fine with GRUB(1). Reproducible: Steps to Reproduce:
you mean the entries ? if yes cf what is written in errata + notes, and ihmo it's a bad ideas to implement that.
Component: Installer => RPM PackagesSummary: MCC -> Boot -> Set up boot system -> Modify does not effect Grub2 => MCC -> Boot -> Set up boot system -> Modify does not effect Grub2 entriesSource RPM: (none) => drakxtools-cursesSeverity: normal => minor
(In reply to Manuel Hiebel from comment #1) > you mean the entries ? if yes cf what is written in errata + notes, and ihmo > it's a bad ideas to implement that. Got it. Fine with me. I think quite a few folks like me will stumble across this. I'll change this bug to RESOLVED. Thanks
Status: NEW => RESOLVEDResolution: (none) => FIXEDSummary: MCC -> Boot -> Set up boot system -> Modify does not effect Grub2 entries => [RESOLVED]MCC -> Boot -> Set up boot system -> Modify does not effect Grub2 entries
well it's a bug, and btw no need to change the summary
Status: RESOLVED => REOPENEDResolution: FIXED => (none)Summary: [RESOLVED]MCC -> Boot -> Set up boot system -> Modify does not effect Grub2 entries => MCC -> Boot -> Set up boot system -> Modify does not effect Grub2 entries
I've tinkered with the "e" fuction on the boot screen and that does not seem to be able to change the text either. Maybe I don't understand what or how the Emacs commands work. I did notice that when the kernel updates that the GRUB2 does default to the new Kernel.
I tried to modify the default entry with the MCC, applying to the grub 2 bootloader. There is no advertising that this is not permitted. But, at the next boot, the default entry has not been changed. Mageia 3 RC i586, uptodate.
CC: (none) => yves.brungard_mageia
(In reply to Manuel Hiebel from comment #1) > you mean the entries ? if yes cf what is written in errata + notes, and ihmo > it's a bad ideas to implement that. I agree.
CC: (none) => zen25000
I confirm this day .I tried to modify the default entry with the MCC, applying to the grub 2 bootloader.It's not save by the MCC
CC: (none) => thierry.rouillon
(In reply to thierry rouillon from comment #7) > I confirm this day .I tried to modify the default entry with the MCC, > applying to the grub 2 bootloader.It's not save by the MCC Yes, this is expected and probably preferable that drakboot does not try to interfere with the grub2 menu. https://wiki.mageia.org/en/Mageia_3_Errata#Grub2 I feel that this should be a WONTFIX, however the option needs to be removed from drakboot first.
It is difficult for non-technical users to understand (from the Errata or wherever) why it's preferable that drakboot does not try to interference with the grub2 menu. It's like an unfinished feature. Will grub2 be obsoleted soon, or it has no worth working to implement the missing parts in the not too distant future? Removing the option from drakboot might be considered as a last resort, otherwise it seems like undermining the purpose of MCC. Don't forget that MCC is one of the best assets to Mageia.
CC: (none) => gruescubogdan
(In reply to Bogdan Gruescu from comment #9) > It is difficult for non-technical users to understand (from the Errata or > wherever) why it's preferable that drakboot does not try to interference > with the grub2 menu. I can understand that. IIUC grub legacy menus are created by drak* tools which have control over the menu content. In this respect it is quite acceptable that drak* tools should also offer a mechanism to modify them. In contrast grub2 menus are created by grub2 tools, and also updated by grub2 tools (for example on kernel update). Adding drak* capability to further modify the menu would create a recipe for bugs galore and over complicate the process. There is a tool - 'grub-customizer' which *attempts* to do this, and is a project in it's own right. However if you look at the open bugs list for grub-customizer then I think that you will agree that messing with the grub2 menu is no mean task. https://bugs.launchpad.net/grub-customizer > It's like an unfinished feature. Only while the option is offered and fails to work. > Will grub2 be obsoleted soon, No > or it has no > worth working to implement the missing parts in the not too distant future? > Removing the option from drakboot might be considered as a last resort, > otherwise it seems like undermining the purpose of MCC. Don't forget that > MCC is one of the best assets to Mageia. MCC does not currently offer to re-configure the KDE start menu - are you saying it should? I guess not, as that is best left to KDE, in the same way that I think the grub2 menu should be left to grub2. Just my two pence worth ;) Out of interest what is it that you want to change about your existing grub2 menu? Maybe there is a simple solution.
Firstly, I wish to thank you Barry for the details provided, it's more clear now. I assume that a skilled developer willing to customize whathever related to grub2 could put a sequence of appropriate grub2 commands in a terminal and achieve the desired result. The problem is that a very few users are able / willing to take this approach, it is also risky and time consuming. I've skimmed through https://bugs.launchpad.net/grub-customizer, there are 32 items on the list, but doesn't appear to be triaged well, perhaps some of them are only Ubuntu related, however there should be a quite great number of legitimate bugs. MCC offers a great advantage: a single tool readily available for all desktop environments provided by Mageia which is capable to achieve a series of most used configurations options. It's more convenient to use it whenever possible than saying: install and use package A to achieve objective X, install and use package B to achieve objective Y, open a terminal and write something (first you need to learn / search what to write) to achieve objective Z and so on. The downside is that MCC needs active mantainers and further problems are likely to occur when a desktop environment offers a similar tool for a particular task. Currently I understand that there is only a basic implementation of grub2 in MCC. Your suggestion about the removing of the options offered that doesn't work and perhaps adding a note about 'grub-customizer' makes sense as it will reduce the burden on packagers / developers, unfortunately at the cost of the users which will be deprived of the availability of a reliable tool to easily alter some of the grub2 options. The available choices should be carefully weighted ... (In reply to Barry Jackson from comment #10) > In contrast grub2 menus are created by grub2 tools, and also updated by > grub2 tools (for example on kernel update). > > Adding drak* capability to further modify the menu would create a recipe for > bugs galore and over complicate the process. That's very logical and consequently true, implementing it will also mean, in addition to the initial work, to extensively review the drak* code each time a change is made to grub2. It sound like a good option is that a middle way to be chosen from which to benefit both the users and the contributors. I've also seen this: https://wiki.mageia.org/en/Feature:BootPartitionShakeup > MCC does not currently offer to re-configure the KDE start menu - are you > saying it should? Of course not, that's the duty of the KDE developers. > I guess not, as that is best left to KDE, in the same way that I think the > grub2 menu should be left to grub2. In an ideal world one might expect a graphical tool to be provided by the grub2 developers for this stuff. Sometimes the distributions consider that is more beneficial in the long run to add additional functionalities instead of letting the users to accustom themselves to an unpleasant situation. > Out of interest what is it that you want to change about your existing grub2 > menu? Maybe there is a simple solution. I've tried grub2 for a few months but now I've returned to grub legacy mainly because I have an easy way to keep the grub entries tidy and there is also a 'Safe mode' entry which works and it's very useful in some situations. grub2 was too rigid and 'Safe mode' was either missing or didn't work as expected. Just as a personal taste, I find the font used in grub legacy menus more common and appropriate for a boot screen, fit better and the text in the boot menu is easily readable. grub2 menu entries had the same font as grub legacy at the beginning, and after a while you changed it to the more 'exotic' font similar to Mageia logo. Of course I can find a way to change the default to whatever else, and not saying to change it back if you consider is good to leave it as it is now ... just took the opportunity to answer your question :)
(In reply to Bogdan Gruescu from comment #11) > Currently I understand that there is only a basic implementation of grub2 in > MCC. Yes, basically enough to be able to switch between the available bootloaders. > ... unfortunately at the cost > of the users which will be deprived of the availability of a reliable tool > to easily alter some of the grub2 options. > The available choices should be carefully weighted ... Well they do have grub-customizer. > That's very logical and consequently true, implementing it will also mean, > in addition to the initial work, to extensively review the drak* code each > time a change is made to grub2. Exactly - and we do not have the people to do this. > I've also seen this: > https://wiki.mageia.org/en/Feature:BootPartitionShakeup Which is a whole new can of worms ;) > In an ideal world one might expect a graphical tool to be provided by the > grub2 developers for this stuff. Don't hold your breath. > Sometimes the distributions consider that is more beneficial in the long run > to add additional functionalities instead of letting the users to accustom > themselves to an unpleasant situation. I really don't see the 'unpleasant situation' - for me at least the menu created by grub2 does all I need. In multiboot situations (where I use a separate master grub2 partition) I remove os-prober to leave only the Mageia options and in other installations where there is only maybe one other OS I install os-prober so that the other OS is shown in the Mageia menu. > I've tried grub2 for a few months but now I've returned to grub legacy > mainly because I have an easy way to keep the grub entries tidy What do you find untidy about the grub2 menu? There is only really one issue that in my opinion needs fixing, where multiple installations of a given OS are not adequately identified. The "on /dev/sda9" etc. only currently appears in the sub-menus. > and there is > also a 'Safe mode' entry which works and it's very useful in some > situations. grub2 was too rigid and 'Safe mode' was either missing or didn't > work as expected. I'm not really sure what you mean by 'safe mode'. You can edit the kernel command line in grub2 using the 'e' option in the menu, so it's fairly straightforward to change kernel options to e.g. add '3' to boot into non-graphical mode etc. > Just as a personal taste, I find the font used in grub > legacy menus more common and appropriate for a boot screen, fit better and > the text in the boot menu is easily readable. That is interesting - it's the first adverse comment I have seen regarding the font, (however in truth I did expect more ;) > grub2 menu entries had the > same font as grub legacy at the beginning, and after a while you changed it > to the more 'exotic' font similar to Mageia logo. I was trying to keep some corporate identity and since diogenese had just put in so much effort to create the font it seemed appropriate :) > Of course I can find a way > to change the default to whatever else, and not saying to change it back if > you consider is good to leave it as it is now ... just took the opportunity > to answer your question :) Watch this space - I am working on an alternative theme package which will use a clearer, larger font for anyone who feels as you do. It will appear in the Cauldron repo, but will also install in Mageia 3. Regarding the 'risk' of dabbling with bootloader settings, you may like to test my (very easy to use) script that creates a grub2 boot CD or USB stick - instructions are in the script:- http://mtf.no-ip.co.uk/pub/linux/barjac/soft/mk-grub2-rescue
(In reply to Barry Jackson from comment #12) > Well they do have grub-customizer. Yes, it's much better than nothing. Certainly you see the difference: in the case of grub legacy, the user can configure it in less than a minute (even at the installation time) with the internal provided tool (drakboot) which is easy to use for all categories of users and expectantly more reliable than a third party program. > Exactly - and we do not have the people to do this. There are quite a lot of new developers whom expressed recently theirs intention to contribute, maybe it worth to make a last attempt and seek whether is anyone willing to help you, agreed ... there is lot of work on the horizon in different areas and the chances are slim under the current circumstances. > I really don't see the 'unpleasant situation' - for me at least the menu > created by grub2 does all I need. > In multiboot situations (where I use a separate master grub2 partition) I > remove os-prober to leave only the Mageia options and in other installations > where there is only maybe one other OS I install os-prober so that the other > OS is shown in the Mageia menu. Well, you did a great job configuring / implementing grub2, although there is a risk to fall into the trap asumming that the great majority of users have your knowledge and experience with grub2 (could be generalized). Examining the MCC, anyone observe that everything was designed in a form that is easy to understand with simple options (so don't need to read tutorials) and there are also some more advanced options for skilled users. If these values / assets diminish over time, in my opinion the negative impact will be quite high. > What do you find untidy about the grub2 menu? > There is only really one issue that in my opinion needs fixing, where > multiple installations of a given OS are not adequately identified. The "on > /dev/sda9" etc. only currently appears in the sub-menus. Nothing. For an unknown reason, I got an entry for each of my Windows partitions, and with grub legacy it's simpler to get rid of the two unnecessary entries and keep only the correct one. > I'm not really sure what you mean by 'safe mode'. You can edit the kernel > command line in grub2 using the 'e' option in the menu, so it's fairly > straightforward to change kernel options to e.g. add '3' to boot into > non-graphical mode etc. Now that you said it, I tried to add '3' and it worked well. But with grub legacy it's even more straightforward, the 'Safe mode' is already there, setting some other variables is just on a click away, in general the interface is more user friendly. It's not bug free, but regarding usability adding boot options seems faster. > That is interesting - it's the first adverse comment I have seen regarding > the font, (however in truth I did expect more ;) That's because there are more important issues to put on the table than wasting time on this digression, I've also hesitated to bring it into discussion. > I was trying to keep some corporate identity and since diogenese had just > put in so much effort to create the font it seemed appropriate :) Again, what I put here is just my opinion and might not be shared by the majority. The idea is how far you will go. There is the 'Mageia' word in 'Mageia Grub2 ...", there is the Mageia logo, the Mageia background ... and I think the line must be drawn there, adding also Mageia font to the menus appears too intrusive. I know Ubuntu did the same, but their font is more similar to a regular font and therefore not so, say 'splashy'. I remembered how nice and clear it looked in the early stages (better than current grub legacy), and after you changed it I was somewhat dissapointed, the font was like an obstacle, distracting attention in a negative way. In the end it's just an application for boot options and users expect quality, fleetness and functionality and the corporate identity should be kept to somewhat subtle. Imagine how MCC would look like if someone add there extra and excessive branding. > Watch this space - I am working on an alternative theme package which will > use a clearer, larger font for anyone who feels as you do. It will appear in > the Cauldron repo, but will also install in Mageia 3. It depends on the screen size and resolution, but the current font size seems good to me, larger might be ugly. > Regarding the 'risk' of dabbling with bootloader settings, you may like to > test my (very easy to use) script that creates a grub2 boot CD or USB stick > - instructions are in the script:- > http://mtf.no-ip.co.uk/pub/linux/barjac/soft/mk-grub2-rescue Very good idea with this script, really ... why not considering / proposing to include it in MCC after reaching the desired quality in its development? I've found two issues with it during my limited tests and I will attach a file to illustrate that in a new comment.
Created attachment 4188 [details] test with grub2-rescue Terminal output and comments after testing Barry's script.
(In reply to Bogdan Gruescu from comment #14) > Created attachment 4188 [details] > test with grub2-rescue > > Terminal output and comments after testing Barry's script. Thanks for your test - that's really odd, however it's off topic for this bug so maybe we can persue this via email. I wonder if you waited long enough for the detection? ~ It works OK here and the prompts are correct re. stick insertion. Regarding fonts, maybe you would like to test the package grub2-mageia3-theme-dejavu which is now in Cauldron (you may need to wait for your local mirror to sync). Just install it - it should remove the original theme automatically.
Thanks Barry, you should have received my email regarding the script by the time you read this message. I've tried 'grub2-mageia3-theme-dejavu' (quite likely it should be renamed as 'grub2-mageia-theme-dejavu' as suggested @dev ml). I am not sure what to say ... some tweaks might be recommanded because (if I remembered correctly) this screen was prettier in the early stages than it is now. - maybe the font wasn't bold initially; - maybe the font colors were different, it think also the black color was involved somewhere there; - the combination between white and light blue font with the not so dark blue background it might not be the perfect choice; but I see you tried to use Mageia colors; - overall, despite the above the current colors seems to create an impression of 'calm', so it might *not* be a good ideea to add there very shinning colors. You may also consider the idea to offer the users the choice regarding the theme package to install, insofar as this is not disturbing / annoying. For example, at the installation of the 'lightdm' package, the user is prompted about which greeter package to be installed.
(In reply to Bogdan Gruescu from comment #16) > Thanks Barry, you should have received my email regarding the script by the > time you read this message. > > I've tried 'grub2-mageia3-theme-dejavu' (quite likely it should be renamed > as 'grub2-mageia-theme-dejavu' as suggested @dev ml). > I am not sure what to say ... some tweaks might be recommanded because (if I > remembered correctly) this screen was prettier in the early stages than it > is now. The first tests used DejaVu and I did experiment with a darker blue font at one time, however this is purely subjective. The current font colour is a lighter shade of the 'glow' colour in the background image (bottom right) which it was intended to complement. > - maybe the font wasn't bold initially; I think it was but I may be mistaken > - maybe the font colors were different, it think also the black color was > involved somewhere there; No, never black. However the menu items are now in a larger point size, which was a deliberate attempt to make this theme more legible for those of us without 20:20 vision ;) > - the combination between white and light blue font with the not so dark > blue background it might not be the perfect choice; but I see you tried to > use Mageia colors; Yes > - overall, despite the above the current colors seems to create an > impression of 'calm', so it might *not* be a good ideea to add there very > shinning colors. I will leave it as is for now unless there are strong objections. > You may also consider the idea to offer the users the choice regarding the > theme package to install, insofar as this is not disturbing / annoying. For > example, at the installation of the 'lightdm' package, the user is prompted > about which greeter package to be installed. I don't think this is worth the work involved, as most new users would not know the difference at install time. It's a simple job to change it later.
I agree with all of your responses. In addition, perhaps the artwork team should take care, or at least to form a judgement on fonts, appearance and so on. Sorry that this part of discussion was a digression from the subject of this bug.
It seems that drakboot is still offering to edit the grub2 menu when it should not. This bug drifted off topic, but the original bug is still there and looks bad when an advertised feature does not work. Can this be removed from drakboot so users cannot attempt to use it?
Priority: Normal => HighCC: (none) => thierry.vignaudSeverity: minor => major
For on year, I planned to change 2nd screen for grub2, only offering to choose: - default entry - extra parameters But I'd no time for doing it
Blocks: (none) => 416
Created attachment 6407 [details] use a dedicate screen for grub2 (1/2) eg: this seems to do it
Created attachment 6408 [details] do not run update-grub2 twice (2/2)
Keywords: (none) => PATCH
(CCing the usual suspects) @Thomas, Marja: WDYT?
CC: (none) => marja11, tmb
Created attachment 6409 [details] prepare for reusing code (1/3)
Attachment 6407 is obsolete: 0 => 1 Attachment 6408 is obsolete: 0 => 1
Created attachment 6410 [details] use a dedicate screen for grub2 (2/3)
Created attachment 6411 [details] do not run update-grub2 twice (3/3)
Created attachment 6418 [details] 2nd "drakboot --boot" screen + "Advanced" pop-up (In reply to Thierry Vignaud from comment #23) > (CCing the usual suspects) > @Thomas, Marja: WDYT? So far: perfect, thanks! I tried the patches in an installed system, the first "drakboot --boot" screen seemed to have stayed the same (on my EFI-system: no more choice between bootloaders), the 2nd is much nicer than it was before, attaching a screenshot (made after pressing the "Advanced button". After clicking "Finish" a new bootloader was written as expected. A Mageia install on an external HD that I had detached, had indeed disappeared from the menu, and booting up the system still worked fine. Both drop down lists (in the 2nd screen and in the Advanced pop-up) look fine. I did not feel called to select anything there, though.
Created attachment 6420 [details] the new bootloader configuration screen in installer It works in installer, too, see attached screenshot. (It was maybe not needed to rebuild stage2 against the new drakxtools, but I did) It took longer than I had expected for the new screen to appear (the first screen appeared immediately). However, the log doesn't think it was as bad as I remember ;-) * step "summary" took: 0:01:36 I still don't know how to properly add packages to be tested to a local mirror, so I added the new drakxtools ones and renamed them to the version that was on the mirror.
You changed what we installed and was working. Switching from !UEFI to UEFI on upgrade is not supported. If you manually shoot yourself in the foot, we cannot help you. If you want a pure UEFI install, you must perform a new install.
Status: REOPENED => RESOLVEDResolution: (none) => WONTFIX
Sorry wrong bug
Status: RESOLVED => REOPENEDResolution: WONTFIX => (none)
(In reply to Marja van Waes from comment #28) > It took longer than I had expected for the new screen to appear (the first > screen appeared immediately). This is b/c we've to run update-grub2 first in order to have a list of the generated entries so that one can choose the default one
BTW glad to see you're now en expert on patching/debugging the stage2 :-)
commit 80b43f6ee1b335af44c3ce3dbf6bb1a1311847d5 Author: Thierry Vignaud <thierry.vignaud@...> Date: Fri May 1 11:42:40 2015 +0200 add a dedicate step for grub2 (mga#9627) rationale: grub2 entries are autogenerated, thus: - we cannot just reuse labels from previous bootloader (grub-legacy/lilo) - we cannot alter entries --- Commit Link: http://gitweb.mageia.org/software/drakx/commit/?id=80b43f6ee1b335af44c3ce3dbf6bb1a1311847d5
Comment on attachment 6411 [details] do not run update-grub2 twice (3/3) Not commited as we would need to check if nothing was changed (default entry, ...) in order to skip update-grub
Attachment 6411 is obsolete: 0 => 1
Comment on attachment 6410 [details] use a dedicate screen for grub2 (2/3) Fixed patch commited
Attachment 6410 is obsolete: 0 => 1
Closing
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
*** Bug 12419 has been marked as a duplicate of this bug. ***
CC: (none) => kvv-vp
*** Bug 15165 has been marked as a duplicate of this bug. ***
CC: (none) => borut
*** Bug 18536 has been marked as a duplicate of this bug. ***
CC: (none) => herbert
Testing this in x86_64 UEFI system: It currently puts an entry in /boot/grub2/grubenv to be used IIUC when GRUB_DEFAULT=saved. From my testing it appears not to add GRUB_DEFAULT=saved to /etc/default/grub if it is not already there. Doing this manually and running update-grub2 throws a warning and the new default fails to work. [baz@jackodesktop grub2]$ update-grub2 Password: Generating grub configuration file ... Found theme: /boot/grub2/themes/maggy/theme.txt Found linux image: /boot/vmlinuz-4.6.0-desktop-1.mga6 Found initrd image: /boot/initrd-4.6.0-desktop-1.mga6.img Found linux image: /boot/vmlinuz-4.6.0-desktop-0.rc7.1.mga6 Found initrd image: /boot/initrd-4.6.0-desktop-0.rc7.1.mga6.img Found linux image: /boot/vmlinuz-4.6.0-desktop-0.rc6.2.mga6 Found initrd image: /boot/initrd-4.6.0-desktop-0.rc6.2.mga6.img Found linux image: /boot/vmlinuz-4.6.0-desktop-0.rc6.1.mga6 Found initrd image: /boot/initrd-4.6.0-desktop-0.rc6.1.mga6.img Found linux image: /boot/vmlinuz-4.6.0-desktop-0.rc5.2.mga6 Found initrd image: /boot/initrd-4.6.0-desktop-0.rc5.2.mga6.img Found linux image: /boot/vmlinuz-4.6.0-desktop-0.rc5.1.mga6 Found initrd image: /boot/initrd-4.6.0-desktop-0.rc5.1.mga6.img Found linux image: /boot/vmlinuz-4.6.0-desktop-0.rc4.1.mga6 Found initrd image: /boot/initrd-4.6.0-desktop-0.rc4.1.mga6.img Found linux image: /boot/vmlinuz-4.4.6-desktop-1.mga6 Found initrd image: /boot/initrd-4.4.6-desktop-1.mga6.img Found linux image: /boot/vmlinuz-4.4.5-desktop-1.mga6 Found initrd image: /boot/initrd-4.4.5-desktop-1.mga6.img Found linux image: /boot/vmlinuz-desktop Found initrd image: /boot/initrd-desktop.img Found Mageia 5 (5) on /dev/sda4 Found Mageia 6 (6) on /dev/sda5 Warning: Please don't use old title âMageia (4.6.0-desktop-1.mga6) 6 (on /dev/sda5)â for GRUB_DEFAULT, use âAdvanced options for Mageia 6 (6) (on /dev/sda5)>Mageia (4.6.0-desktop-1.mga6) 6 (on /dev/sda5)â (for versions before 2.00) or âgnulinux-advanced-18c8d8d4-dee6-4219-9dbf-a96d439ea76e>gnulinux---18c8d8d4-dee6-4219-9dbf-a96d439ea76eâ (for 2.00 or later) done The head of /boot/grub2/grubenv is: # GRUB Environment Block saved_entry=Mageia (4.6.0-desktop-1.mga6) 6 (on /dev/sda5) ##########################################################---snip
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Please open a new bug. This one is already very long and was close one year ago.
If you use GRUB_DEFAULT=saved you must also add the line GRUB_SAVEDEFAULT=true . Both lines must be present in /etc/default/grub or "save" will not work.
CC: (none) => cae
Please open a new bug and comment there :-)
Thanks Charles - please comment in https://bugs.mageia.org/show_bug.cgi?id=18560
Please stop reopening this one
commit ad128f02d165f26d7eec3781952f108efb588c67 Author: Thierry Vignaud <tvignaud@...> Date: Fri May 27 16:38:51 2016 +0200 grub2: set GRUB_DEFAULT + GRUB_SAVEDEFAULT else grub2-set-default won't work (mga#9627, mga#16059) but do not overwrite it if user has changed its value --- Commit Link: http://gitweb.mageia.org/software/drakx/commit/?id=ad128f02d165f26d7eec3781952f108efb588c67 Bug links: Mageia https://bugs.mageia.org/9627 https://bugs.mageia.org/16059