This bug is also existant on Red Hat Enterprise Linux 4 U2 for pSeries
+++ This bug was initially created as a clone of Bug #153961 +++
Description of problem:
anaconda text dialogues in rescue mode are messed up. The ones presented by
loader (language, keyboard) are ok; those presented after anaconda is started
rescue mode (networking, installed image selection) have odd characters, boxes
are not lined up correctly, mostly unusable.
If you enable networking, after selecting dhcp, anaconda will print a Python
error because some __call__ is given 5 arguments where 6 were expected, or the
other way round.
I booted from the i386 rescuecd, without any arguments.
Version-Release number of selected component (if applicable):
-- Additional comment from email@example.com on 2005-04-08 16:00 EST --
Appears to be fixed in FC4-re0407.
-- Additional comment from firstname.lastname@example.org on 2005-04-12 11:57 EST --
Actually wasn't fixed there, but fixed in rawhide.
Obvioius fix to backport, rescue mode should work.
The error exists on x86, with RHEL4 U2, so setting the arch to all:
Traceback (most recent call last):
File "/usr/bin/anaconda", line 604 in ?
rescue.runRescue(rootPath, not rescue_nomount, id)
File "/usr/lib/anaconda/rescue.py", line 209 in runRescue
rc = apply(win, (screen, ) + args)b>/<Alt-Tab> between
elements | <Space> selects | <F12> next screen TypeError: __call__() takes
exactly 6 arguments (5 givien)
Should be fixed in anaconda 10.1.1.26-1
*** Bug 175181 has been marked as a duplicate of this bug. ***
Not sure if these problems would show up on a rescue boot of the DVD, or only if
using a disc which is only for rescue. However, if they would show up on a
rescue boot of the DVD, verified that it's fixed on RHEL4U3 re1221.0 for i386.
*** Bug 178499 has been marked as a duplicate of this bug. ***
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
Internal Status set to 'Resolved'
Status set to: Closed by Client
Resolution set to: 'RHEL 4 U4'
This event sent from IssueTracker by uthomas