I've done lots and lots of work on this class of problem over the last several months. I'm afraid that there are too many bugs about it, too many of which consist of lots of different people chiming in with lots of similar symptoms which would have to be individually untangled to find the different underlying causes, to update each one of them individually.
This is probably in fact fixed for new systems, but once the GRUB packaging has forgotten its installation target on any particular system due to old bugs, it's more or less impossible to recover that information in any vaguely reliable way. In the cases where we don't re-prompt automatically, it's generally because it doesn't even know that it has the wrong install location recorded in the debconf database (i.e. it has information that looks plausible, but which is wrong). You need to run 'sudo dpkg-reconfigure grub-pc' to fix it properly on a given system. For a more detailed treatment of this, see my blog (which is focused on Debian versions of grub2, but the issues are largely the same): http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/debian/2010-06-21-grub2-boot-problems.html http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/debian/2010-07-02-grub2-with-luck.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/609280 Title: Grub error : symbol grub_xputs not found -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
