Red Hat Bugzilla – Bug 590661
GRUB bootloader should have a few seconds delay on a multi-boot setup
Last modified: 2010-05-18 20:07:33 EDT
Description of problem:
GRUB by default in configured in Fedora to not show the menu and have zero delay but in a multi-boot environment where Anaconda detects Windows and configures GRUB to boot Windows as a alternative, GRUB was configured by Anaconda to have a few seconds delay and show the menu so that the user can choose between Fedora and Windows.
Unfortunately this is not the case with Fedora 13 RC2 anymore. This results in a non-technical user unable to boot into Windows after installing Fedora 13. I am marking it as a blocker
Can anyone confirm how this behaved in F12?
Fedora 12 works as expected. This is a regression.
This never worked in F12 for me (I multi-boot several Linux distro's).
The zero delay sucks.
(In reply to comment #3)
> This never worked in F12 for me (I multi-boot several Linux distro's).
> The zero delay sucks.
And it still doesn't work in F13.
*** Bug 574994 has been marked as a duplicate of this bug. ***
Worked for me F12 on 2/2 of my machines as Rahul explains. 0 delay does suck..!
Reviewed by a QA, Release Engineering, etc. at 2010-05-11 "Go/No-Go Meeting. Move to F13Target, will accept into F13 final a well tested fix for this issue considering the potential negative press.
anaconda-13.42-1.fc13 has been submitted as an update for Fedora 13.
2010-05-13 -- anaconda-13.42-1.fc13. from Fedora13-Final.RC3 tested on Dell Dimension B120 Laptop System. Hard Drive had Fedora13-Final.RC2 and WindowsXPSP3 partitons before installation. Advertised delay in grub was present as expected.
When testing F13Final.RC3 as guest in VirtualBox-OSE with no dual OS the delay was 0 as advertised. Call this bug FIXED for my testing.
several people have confirmed this is fixed.
Fedora Bugzappers volunteer triage team