Bug 73111
| Summary: | border characters corrupted in tui upgrade from 7.2 w/ full lang support | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Mike McLean <mikem> | ||||||||
| Component: | anaconda | Assignee: | Jeremy Katz <katzj> | ||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Mike McLean <mikem> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 8.0 | ||||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i386 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2003-01-20 22:36:24 UTC | Type: | --- | ||||||||
| 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: | 67218, 79579 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Mike McLean
2002-08-30 21:06:34 UTC
kickstart upgrade from 7.2/minimal/all_languages_supported produces the same problem Verified with manual upgrade. The installation starts out normal, but at some point (sorry I missed exactly where) during the package installation, the characters switch. Will attach the ks.cfg I used to make the initial 7.2 install. Created attachment 74064 [details]
ks.cfg used for the initial 7.2 install that I upgraded from
Created attachment 74084 [details]
anaconda-ks.cfg left by the upgrade
Created attachment 74085 [details]
upgrade.log from the (manual) upgrade
I'm guessing this is because a scriptlet was getting unicode_start to run which would have really confused the newt we had for the installer in 8.0. Does this seem to do better with the current tree? I haven't seen this in a long time. Closing. |