[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kcm_grub2] [Bug 332262] Problem with GRUB2 setup in kde system configuration
From:       Konstantinos Smanis <konstantinos.smanis () gmail ! com>
Date:       2014-04-03 20:53:13
Message-ID: bug-332262-17878-MDm17wsbTd () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=332262

Konstantinos Smanis <konstantinos.smanis@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDSINFO                   |RESOLVED
         Resolution|WAITINGFORINFO              |FIXED
      Latest Commit|                            |http://commits.kde.org/kcm-
                   |                            |grub2/8a60f1a1f75cc012ec7de
                   |                            |ca85e6783037ed6fccd

--- Comment #5 from Konstantinos Smanis <konstantinos.smanis@gmail.com> ---
Git commit 8a60f1a1f75cc012ec7deca85e6783037ed6fccd by Konstantinos Smanis.
Committed on 03/04/2014 at 20:42.
Pushed by ksmanis into branch 'master'.

Allow zero GRUB_HIDDEN_TIMEOUT.

Seems like the Kubuntu scripts treat GRUB_HIDDEN_TIMEOUT=0 as a special
case where they completely bypass GRUB_TIMEOUT and boot without showing
the menu at all. I think this happens when you have only one OS
installed but I didn't bother to do extended testing.

Allowing a zero timeout value may seem a bit counterintuitive to the
user, but it's a valid value after all, let's allow it.

Also improved the common-case scenario in unquoteWord() for empty
strings.

M  +4    -0    src/common.cpp
M  +7    -4    src/kcm_grub2.cpp
M  +0    -3    ui/kcm_grub2.ui

http://commits.kde.org/kcm-grub2/8a60f1a1f75cc012ec7deca85e6783037ed6fccd

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]