New kernel changes default to 0 in menu.lst

Asked by John Rose

In Karmic, reboot after new kernel install (caused by Update Manager) causes 'Must be authenticated' by grub when it tries to boot using old kernel. This is because kernel update results in Default value in menu.lst being changed from 0 to 2. I amend menu.lst and it boots OK using new kernel. I changed menu.lst (before upgrade from Jaunty to Karmic) so that it had an md5 password set and changed Howmany valuer to 3. Why is this change to Default value happening on kernel change and I how do I prevent it?
PS on another PC using Jaunty, this change to Default value does not occur even though it also has password md5 set and Howmany set to 3.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
actionparsnip
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

Log a bug. Default should not change

Revision history for this message
John Rose (johnaaronrose) said :
#2

How do I log a bug with the kernel update The facility seems to have been removed from launchpad now that logging generally takes place by means of reporting in the appropriate app?

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3

If you find a bug in Ubuntu or any of its derivatives, please file a bug using the command « ubuntu-bug <package> » - See https://help.ubuntu.com/community/ReportingBugs for other ways to report bugs

Revision history for this message
John Rose (johnaaronrose) said :
#4

What package should it be?

Revision history for this message
Best actionparsnip (andrew-woodhead666) said :
#5

I'd say grub2 or grub, whichever you use.

Revision history for this message
John Rose (johnaaronrose) said :
#6

Thanks actionparsnip, that solved my question.