Bug 790808

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0

The "timeout" option in YaST2 bootloader option modifies /etc/default/grub as follows:

* If "Hide Menu on Boot" is unchecked and timeout is nonzero, it sets GRUB_TIMEOUT to the value specified in this field, and sets GRUB_HIDDEN_TIMEOUT to 0. This is correct.

* If "Hide Menu on Boot" is checked and timeout is nonzero, sets GRUB_HIDDEN_TIMEOUT to the value specified in this field, and sets GRUB_TIMEOUT to 0. This is also correct.

Reproducible: Always

Steps to Reproduce:
The problems occur if you try to set the timeout to 0, the lowest valid option in both YaST and /etc/default/grub. Regardless of whether or not "Hide Boot Menu" is checked, no changes will be written (to these settings). So when revisiting the module, you'll see whatever the settings were before you tried to hide the menu and remove the timeout.
Actual Results:  
For example, if you check "Hide Menu on Boot" and set the timeout from a positive number to 0, "Hide Menu on Boot" will be unchecked the next time you visit the module and the timeout will be whatever it previously was. (Since neither GRUB_TIMEOUT nor GRUB_HIDDEN_TIMEOUT were modified, GRUB_TIMEOUT remains positive and the menu is not hidden.)

Expected Results:  
If timeout is set to 0, both GRUB_TIMEOUT and GRUB_HIDDEN_TIMEOUT should be set to 0.

Or if we think it's always a bad idea to do that, set the minimum timeout value to 1. But since GRUB allows it, YaST probably should, too. =)