[jaunty] new kernel install with modified grub menu.lst disables update-grub
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| dpkg (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: dpkg
One of my systems has a problem with uspash hanging shutdown so I modified menu.lst's #defoptions =spash quiet and removed the "splash quiet" from all the installed kernels as well. Booting up I noticed that 2.6.28-15 was now available and installed it. Having faith, I also cleaned out -12 to -14 kernels in synaptic as it installed -15. Every time It tried to install (the -15) or remove a kernel it asked about a modified menu.lst and I selected the default "to keep the installed version" and it never updated menu.lst so even though -15 was installed and -12 -13 -14 were removed, on reboot only -12 to -14 were on the menu. A simple sudo update-grub fixed it. This seemed to only be a problem when modifying menu.lst.
So, a non-stock menu.lst on kernel install will not run update-grub and on reboot the old menu.lst will be shown.
What I suspect is if a modified config file (menu.lst) is kept, update-grub isn't run, although it should be (On kernel install AND remove)
| Joel Oliver (joelol75) wrote | #1 |
Sorry, I noticed that although sudo update-grub found the -15 kernel it DID NOT change the menu.lst at all (-12 to -14 were still there with no -15)
I then did an install of the -14 kernel again and this time allowed it to install the package maintainers version of menu.lst and then removed the -14 kernel. Surprised that it left #defoptions= blank like I wanted it.
I'm not sure if this is a bug then. But shouldn't it put the #defoptions= splash quiet back in there if I allowed it to install the package maintainers version? Or am I missing something?