'grub2' does not carry over correct 'timeout' time from 'grub'
Bug #386789 reported by
Brett Alton
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Fix Released
|
High
|
Colin Watson | ||
Karmic |
Fix Released
|
High
|
Colin Watson |
Bug Description
Binary package hint: grub2
Using Ubuntu Jaunty 9.04, I followed the instructions[1] for testing grub2 on my Dell XPS Gen 5. Everything went smoothly and I submitted my machine to the wiki.
However, although this doesn't bother me, I noticed my 'timeout' was set to 10 seconds with 'grub' and 5 seconds with 'grub2'.
I figure 5 seconds is a good default, but some might have it set at '0' or '60' seconds, depending on their preferences and I figured this number should be carried over when running 'upgrade-
I'll post the old 'grub' configuration and the new 'grub2' configuration.
Related branches
Changed in grub2 (Ubuntu): | |
status: | New → Confirmed |
Changed in grub2 (Ubuntu Karmic): | |
assignee: | nobody → Colin Watson (cjwatson) |
Changed in grub2 (Ubuntu Karmic): | |
milestone: | none → karmic-alpha-6 |
Changed in grub2 (Ubuntu Karmic): | |
status: | Triaged → Fix Committed |
Changed in grub2 (Ubuntu): | |
status: | Fix Released → New |
To post a comment you must log in.
This also applies to the new GRUB_HIDDEN_TIMEOUT parameter. We need to clear this up for Karmic.