bugGNU GRUB - Bugs: bug #48856, Timeout not transitive to sub-menus


You are not allowed to post comments on this tracker with your current authentication level.

bug #48856: Timeout not transitive to sub-menus

Submitted by:  Jaromír Cápík <jaromir_capik>
Submitted on:  Mon 22 Aug 2016 12:35:30 PM UTC  
Category:  None Severity:  Major
Priority:  5 - Normal Item Group:  Software Error
Status:  None Privacy:  Public
Assigned to:  None Originator Name: 
Open/Closed:  Open Release: 
Release:  1.99 Reproducibility:  Every Time
Planned Release:  None

Wed 14 Sep 2016 08:06:13 AM UTC, comment #3:

No, it is not more clear, sorry. Please attach minimal config files to reproduce it.

Andrei Borzenkov <arvidjaar>
Project Member
Fri 26 Aug 2016 01:49:10 PM UTC, comment #2:

Hello Andrei.

In my case the issue is reproducible even with version 2.0.2~beta2.

It is not about one grub.cfg file, it is about a combination of two config files (one for the main menu and second for a submenu).

In the 1st case try to define a timeout in the main menu (let say 20 seconds) and in a submenu (let say 8 seconds). The default for the main menu must point to the submenu where you defined the 8s timeout. If there's no user intervention, then the system boots automatically in ~28 seconds. But if there is a user intervention and the user selects the submenu by hand, then he has to interrupt the 8s countdown each time he selects the submenu by hand. In this case there should be no countdown anymore since the user stepped in and wanted to select something by hand. The countdown is annoying in this case (if it is longer, then it adds unwanted delay for automatic boots ... if it is low, then it forces user to react quickly)

In the 2nd case try to define a timeout in the main menu (again 20s) and remove timeout settings from the submenu. If there's no user intervention, then you'll get in the submenu after 20 seconds of inactivity, but then you'll stuck in the submenu unless you manually select an entry from it (or do a different operation). That makes no sense. The timeout should get us automatically to the leaf entry that boots something.

In the 3rd case try to remove timeout settings from the main menu and define a timeout 8s in the submenu. If there's no user intervention, then you'll stuct in the main menu unless you manually select the submenu and then you'll get the 8s timeout. That also doesn't make sense as this requires manual intervention. My question is ... What is this good for?

For me the only reasonable implementation should have just one common timeout setting in the main menu config and once it is reached, then we should automatically and without more waiting descend to the lowest level of submenu (till we reach the leaf entry) and boot it.

Is it more clear now?


Jaromír Cápík <jaromir_capik>
Mon 22 Aug 2016 01:26:36 PM UTC, comment #1:

I can't reproduce it. When I set default to submenu entry, it is correctly executed after configured timeout. Please attach minimal grub.cfg showing wrong behavior.

Andrei Borzenkov <arvidjaar>
Project Member
Mon 22 Aug 2016 12:35:30 PM UTC, original submission:

The current timeout behavior doesn't make much sense. The purpose of the timeout is to select one of the choices automatically when no user intervention is detected. In some cases the entry we want to select as default is in one of the configured sub-menus and in that case the grub behavior needs to be tweaked. If the timeout setting is omitted in the sub-menu config, then we stuck in the sub-menu forever in case of no user input. And if we configure a timeout in the sub-menu, then it forces the user to hit a key in order to stop the second (and often unexpected) countdown even when he already interrupted the countdown by making a manual choice in the main menu.
I believe the timeout should be just one (defined in the main menu) and once it is reached, the grub should automatically (and with no more waiting) descend to all sub-menus respecting the configured default entries for all sub-menus it goes through.

Jaromír Cápík <jaromir_capik>


No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by arvidjaar (Posted a comment)
  • -email is unavailable- added by jaromir_capik (Submitted the item)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.




    No changes have been made to this item

    Back to the top

    Powered by Savane 3.4