Public bug reported: Binary package hint: ubiquity
After upgrading from 64-bit Ubuntu Karmic to Ubuntu Lucid beta in a multi-boot environment, I have been unable to access the Windows loader from the GRUB2 menu, despite the fact that the loader is displayed. I see this on two machines, both running AMD double-core processors. On one machine, a laptop, when I click the Windows loader in GRUB (1.98-1ubuntu5), the computer reboots instead of opening the loader. On my stationary box, I instead get a blinking dash on the console, seemingly waiting for a command, but without a prompt. I've checked using GParted, and the non-Ubuntu OS installations are still there, but as noted above, canot be opened. Updating using «sudo update-grub», which I've tried many times, doesn't help. I've been experiencing this problem on the laptop ever since Lucid beta 1 was released (the gory details can be found on pp 38 & 39 of the GRUB2 Basics thread (http://ubuntuforums.org/showthread.php?t=1195275&page=38) on the English-language Ubuntu fora, to which I first posted on 23 March), and on the stationary box ever since the release of beta 2.... Henri ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: grub2 lucid windows-loader -- Unable to access non-Ubuntu loaders from GRUB2 menu in Lucid https://bugs.launchpad.net/bugs/571893 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
