Red Hat Bugzilla – Bug 215316
pygrub traceback when moving cursor one to the right and backspacing
Last modified: 2007-11-30 17:07:37 EST
+++ This bug was initially created as a clone of Bug #208316 +++
Or moving cursor as far right as it'll go.
Traceback (most recent call last):
File "/usr/bin/pygrub", line 483, in ?
File "/usr/lib/python2.4/curses/wrapper.py", line 44, in wrapper
return func(stdscr, *args, **kwds)
File "/usr/bin/pygrub", line 439, in run_main
sel = g.run()
File "/usr/bin/pygrub", line 346, in run
File "/usr/bin/pygrub", line 389, in run_main
l = self.edit_line(line)
File "/usr/bin/pygrub", line 259, in edit_line
ret = t.edit()
File "/usr/bin/pygrub", line 135, in edit
r = curses.textpad.Textbox.edit(self)
File "/usr/lib/python2.4/curses/textpad.py", line 157, in edit
if not self.do_command(ch):
File "/usr/bin/pygrub", line 120, in do_command
IndexError: pop index out of range
Error: Boot loader didn't return any data!
Was fixed in this xen-unstable ChangeSet:
user: Tim Deegan <Tim.Deegan@xensource.com>
date: Thu Nov 09 14:23:24 2006 +0000
summary: [PYGRUB] Fix a few bounds violations in pygrub's command-line editor.
Created attachment 141047 [details]
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
Is there any help IBM can offer with this BZ?
Asking for exception. The justication is that the steps to reproduce this
are quite simple: "
--Steps to Reproduce---
1. launch a RHEL guest and auto-attach console (xm create guest -c)
2. On the Grub menu, hit 'e' to edit the boot entry
3. Hit 'e' a second time to edit that line
4. Use the right arrow key to move the cursor past the last character in the line
5. hit backspace"
and that a customer could hit this while playing with Xen.
Fixed in xen-3.0.3-16.el5
QE ack for RHEL5.
A package has been built which should help the problem described in
this bug report. This report is therefore being closed with a resolution
of CURRENTRELEASE. You may reopen this bug report if the solution does
not work for you.