Bug 816522

Summary: grub menu entry editor confused by tabs in config
Product: [Fedora] Fedora Reporter: Michal Schmidt <mschmidt>
Component: grub2Assignee: Peter Jones <pjones>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: bcl, dennis, mads, pjones
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-30 23:10:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 752653    

Description Michal Schmidt 2012-04-26 10:26:00 UTC 
Description of problem:
It appears that the GRUB menu gets confused by tab characters in the config. Long lines overflow the editing box and it is very difficult to edit the entries, because the cursor position appears in places inconsistent with the text edited.

Version-Release number of selected component (if applicable):
grub2-1.99-19.fc17

How reproducible:
always

Steps to Reproduce:
1. Make sure you are actually using the current GRUB version: grub2-install /dev/vda
2. Reboot
3. Press 'e' in the GRUB menu.
4. Use the cursor keys, try to get to the end of a line. Try editing something.
  
Actual results:
You won't reach the visible end of the line.
When you start typing something, you're actually editing text that does not lie exactly at the place where the cursor appears.

Expected results:
Consistently usable menu editor.

Additional info:
This may present a difficulty for debugging boot problems. We often need people to edit their kernel command line.
Fixing this post-release may be a problem, because AFAIK updating the grub2 package does not actually cause the new version to be used for the next boots.

I built grub2-2.0-0.23 from Fedora git and it seems to be fixed there. Can we get it into F17?
Comment 1 Michal Schmidt 2012-04-26 10:30:12 UTC 
I forgot to mention that it affects the default installation. No configuration changes are necessary to reproduce the bug.
Comment 2 Mads Kiilerich 2012-04-30 23:10:06 UTC 
grub2-2.0-0.24.beta4.fc17 has been pushed to f17 stable - closing