[Bug 1269992] Re: 2.02~beta2 requires manual testing

[Colin Watson]

Elfy (#5): Thanks for your report.  We run across this pattern with
every substantial enough change to GRUB.  It's not actually a problem
with the new upstream per se - it points to a misconfiguration in how
GRUB is installed, and unfortunately we've never quite tracked down the
root cause.  However, I bet you'll find that if you run "sudo debconf-
show grub-pc" you'll find that grub-pc/install_devices is set to
something that doesn't include the device you're actually booting from
(and please do tell us the current value).  You can fix this by using
"sudo dpkg-reconfigure grub-pc" and telling it to install to the master
boot record of every disk in your system (it may be possible to get by
with less, but this is generally a reasonable approach).

Edwin (#6): Thanks for your report.  Timeout handling has changed around
a bit recently, and not all the packaging is quite up to date yet (the
transition is a bit tricky).  You might like to review:

  info -f grub -n 'Simple configuration'

... to see how to adjust your configuration.  If it still doesn't work,
then do attach your /etc/default/grub so I can see what might be going
on.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1269992

Title:
  2.02~beta2 requires manual testing

Status in “grub2” package in Ubuntu:
  Triaged

Bug description:
  I'm syncing GRUB 2.02~beta2 from Debian experimental into trusty-
  proposed.  This requires some manual testing before we let it loose on
  trusty users in general, so this bug exists to ensure that it doesn't
  reach trusty before we're sure it's ready.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1269992/+subscriptions