Red Hat Bugzilla – Bug 134442
grub doesn't scroll properly in gnome-terminal
Last modified: 2007-11-30 17:10:50 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Description of problem:
If a grub session started within a gnome-terminal is long enough to
require scrolling, the screen becomes garbled since not all of the
terminal scrolls, and new output is often lost. The problem does not
occur in the console (VT1), nor does it occur in xterms. I haven't
tried konsole or other terminal emulation programs.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Start gnome-terminal. Resize to, say, 80x25.
2.start grub (don't bother to become root; better not, to avoid mistakes)
3.Issue commands such as `root (hd0,0)' repeatedly. It doesn't matter
if it makes sense, just get it to keep generating output until you'd
expect it to start scrolling. Just pressing ENTER might be good
enough to observe the problem, but having some error messages along
the way helps figure out what happens (or fails to :-)
Actual Results: When it should begin scrolling, it begins garbling
Expected Results: Regular scrolling, just like in text consoles and xterm
If you happen to run 2 or 3 setup commands in a single session, you
won't be able to tell whether the last ones completed successfully.
This is bad.
If you resize gnome-terminal to say 79x25, it's even worse: the
initial cursor will be one line below the initial prompt.
Is it any better if you set TERM to xterm before running grub?
It was already xterm (but why? does gnome-terminal actually implement
an xterm terminal?). FWIW, setting it to vt100 appears to work around
Does it work better with TERM=gnome?
Yup, TERM=gnome fixes it.
if setting TERM to gnome fixes it, the problem isn't ncurses-- it's
gnome-terminal-- gnome-terminal is not 100% compatible with xterm, but
we leave TERM set to stock xterm (our xterm definition is
unpatched/unmodified for this reason and will stay that way) for
compatiblity with many different terminals.
*** This bug has been marked as a duplicate of 128375 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.