Description of problem: Hello. During the installation of Mageia (network or offline), in the window in which the pause is set before the automatic boot of the system, this same pause can not be set to "0". If you enter a pause before loading with the value "0", the default value is set to default "5" seconds. In an already installed system, the delay value is missing (an empty value). However, a pause of 0 seconds can still be set if you enter a double zero, i.e. "00". This is of course a small thing, but misleading. Version-Release number of selected component (if applicable): All versions of Mageia Linux How reproducible: To reproduce this, you need to install Mageia Linux and change the system boot delay parameter to "0". See screenshots in the attached files...
Created attachment 11813 [details] Setting the system boot delay to "0"
Created attachment 11814 [details] Result of setting the system boot delay to "0" = empty value = 5 seconds
Hi, Thanks reporting this. Assigning to Mageia Tools Maintainers, Meanwhile, you should try to have just 1 sec delay in this drakboot GUI. Therefore, you can edit /etc/default/grub as root and make change here. But if you're not familiar with this, do not please.
Source RPM: (none) => drakxtools-18.33-1.mga8.src.rpmSeverity: normal => minorAssignee: bugsquad => mageiatoolsCC: (none) => ouaurelien
Summary: The "0" delay before loading is not set => The "0" delay before loading is not set for GRUB in drakboot
Fixed in git: http://gitweb.mageia.org/software/drakx/commit/?id=6b4eb8a46f56195daaefe12f6b623019db0fb782
CC: (none) => thierry.vignaudResolution: (none) => FIXEDStatus: NEW => RESOLVED
Keywords: (none) => USABILITY
Hi, Thierry Vignaud. The changes you've made work fine, but they haven't been released as new packages yet. Is this update planned? I rediscovered this topic just in case. Thank you for your cooperation.
Resolution: FIXED => (none)Status: RESOLVED => REOPENED
Hello. With the latest updates "drakxtools-18.34-1", the "0" delay works correctly. I will close this bug so as not to distract you once again. Thanks.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED