I believe that the culprit here is the final stanza of /usr/sbin/update-grub, 
which tries to 
compute the new default number by performing arithmetic on the old one:  if you 
have
entered 'saved' as your default, the arithmetic fails.  I think it needs to be 
wrapped in a
test for numeric, e.g.:

   if test -n "$defaultEntryNumber"; then

In the meanwhile, a workaround would appear to be setting 'updatedefaultentry' 
to 'false',
which should sidestep the whole issue.

-- 
update-grub failes when "default" is set to "saved" instead of numeric value
https://bugs.launchpad.net/bugs/164513
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to