Bug 737339

I have played a bit with it  ... it seems that setting GRUB_HIDDEN_TIMEOUT and GRUB_HIDDEN_TIMEOUT_QUIET and then recreating the config is supposed to achieve that ... but it seems that this is mostly ignored. I will show a "Welcome to grub" screen and then switch to the default grub menu instead of directly booting the OS.

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

*** This bug has been marked as a duplicate of bug 727831 ***

(In reply to comment #3)
> 
> *** This bug has been marked as a duplicate of bug 727831 ***

That's not a dupe.

The other bug has been fixed by just making the timeout shorter but the issue here is that we do show the menu *at all* , which breaks "flicker free boot".

(In reply to comment #4)
That's not a bug. It's more like a feature.

See
http://linuxpoison.blogspot.com/2010/11/how-to-change-grub-2-default-timeout.html

If you think it's a bug in the default installation, better report this against anaconda, the installer.

(In reply to comment #5)
> (In reply to comment #4)
> That's not a bug. It's more like a feature.
> 
> See
> http://linuxpoison.blogspot.com/2010/11/how-to-change-grub-2-default-timeout.html

No.

(In reply to comment #6)
> If you think it's a bug in the default installation, better report this against
> anaconda, the installer.

It requires anaconda changes to be fully fixed but we have to fix grub first (to use keystatus to allow interacting with it by holding down shift).

Here you should get help:

https://fedoraproject.org/wiki/Features/Grub2

Due to the recent change of the package maintainer, I am wondering if someone feels responsible at all for such an important package. Otherwise, grub2 usage has to be removed and grub1 be kept for the default installation - as stated at "Contingency Plan".

pjones is taking care of grub2. that's why this bug is assigned to him.

I can't reproduce this behaviour with Fedora 16 Beta RC4 Xfce live and installed.

Discussed at 2011-10-07 blocker review meeting. Rejected as a blocker bug and NTH: it does not hit any criteria and we would not want to poke this after the freeze.

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Still the case even in rawhide.

pjones, any plans to do anything about this at any point?

> pjones, any plans to do anything about this at any point?

Not really, no.  This is something grub2 doesn't do, and the patch for grub1 didn't do very well.  If somebody contributes a patch upstream, that'd be fine, but it's unlikely we'd want it by default.

Ah, now I read back, the report is a bit more complex than I thought.

I wasn't thinking about the 'flicker free boot' thing, just the simple fact that anaconda no longer sets the timeout to 0 for single-boot installs. That's something we can fix if we choose to, right? Though of course there's the giant bikeshed thread about it ATM.

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

this is still valid, i.e., we still don't default to hiding the menu in non-multiboot cases as we did with grub-legacy. Still a question whether changing it is desired.

This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Yes, still no-one's made any decisions about this. Le sigh.

This is fixed by:

https://fedoraproject.org/wiki/Changes/HiddenGrubMenu

Which is in place now for Fedora 29, closing.

FWIW, I'm not 100% sure it's actually *working* yet. Fresh Rawhide installs in openQA do show the grub menu on first boot, and while I was looking through the logs from a Workstation live install to try and figure out https://bugzilla.redhat.com/show_bug.cgi?id=1618794 , I noticed some errors that seem to indicate the 'mark boot as successful' thing that's part of this Change wasn't working correctly. I'll look into this and put some more details in the Change bug or a new bug, but just thought I'd mention it.