Description of problem: with drakrpm-update, the last few kernel package updates overwrite the existing /etc/default/grub configuration without even prompting for the applied changes (rpmnew/rpmsave) Version-Release number of selected component (if applicable): kernel-desktop-4.6.2-2 x86-64 (it's been happening for the last few weeks updates as well)
CC: (none) => smorgan, tmb
Are you sure that's not a duplicate of bug #18112? What exactly has been overwritten?
Keywords: (none) => NEEDINFOCC: (none) => thierry.vignaud
That's a bug in drakboot, right? It shouldn't be that. My issue is that whenever I upgrade the kernel, the /etc/default/grub file is overwritten with the distro one, making me lose the modifications I made to the GRUB2 configuration parameters (by editing the file directly, not by using drakboot, and running update-grub2). Forgot to mention I'm on a BIOS system, if that matters.
That means you probably have an outdated drakxtools. What reports "rpm -q drakxtools"?
The version installed when I made the last kernel upgrade was drakxtools-17.39-1.mga6. Right now your command returns drakxtools-17.41-1.mga6. I've been keeping packages up to date pretty much daily lately
(In reply to Davide Nifosi from comment #4) > The version installed when I made the last kernel upgrade was > drakxtools-17.39-1.mga6. I think that contained the fix for bug 18112 Which exact modifications did you make to /etc/default/grub ? Do they get fully reverted when a new kernel gets installed?
CC: (none) => marja11, zen25000
(In reply to Davide Nifosi from comment #0) > Description of problem: > > with drakrpm-update, the last few kernel package updates overwrite the > existing /etc/default/grub configuration without even prompting for the > applied changes (rpmnew/rpmsave) Regarding rpmnew/rpmsave in grub2, these are intentionally not provided to avoid the possibility of users accepting/rejecting them incorrectly. Their existence triggers a GUI dialog in rpmdrake which can be confusing and where the wrong response to this dialog could cause a system to become un-bootable. See https://bugs.mageia.org/show_bug.cgi?id=17263
The last kernel update (4.6.3-1) did not overwrite my /etc/default/grub file and my custom settings (from 2016-06-23) were preserved. I haven't done anything except keeping my system updated, so if some package was fixed you can close the bug. (In reply to Marja van Waes from comment #5) > I think that contained the fix for bug 18112 > > Which exact modifications did you make to /etc/default/grub ? > Do they get fully reverted when a new kernel gets installed? GRUB_DEFAULT=saved -> GRUB_DEFAULT=0 and removed GRUB_SAVEDEFAULT=true The first time this happened (can't remember when, probably more than a month ago) I also had a few more edits (kernel commandline), so it seems like it just replaced the configuration with the default one.
Dup *** This bug has been marked as a duplicate of bug 18112 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE