From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510 Description of problem: Please note that i file this bug with mc simply because that's the program that exhibits the behaviour, while i suspect it's not mc's fault. Boot in runlevel 3, run mc in the console, it's displayed fine. Reboot in single mode, run mc... it's all garbled. Version-Release number of selected component (if applicable): mc-4.6.0-15 How reproducible: Always Steps to Reproduce: 1.reboot in single mode 2.run mc 3. Actual Results: mc is displayed wrong, like different parts of the program's interface are mashed together Expected Results: mc should be displayed normally Additional info: Note that the problem is not specific to FC2. I think the first time i saw it on RH9, but it could be older than that.
I see the same thing on FC3t1. "export LANG=en_US.UTF-8" fixes this. I think this should be considered an initscript issue. However the (incompolete) UTF-8 patches for mc probably also play a part. Setting a charset other than UTF-8 doesn't work entirely correct (this is not limited to single user mode). Maybe we could test Vladimir Nadvornik's extensions to the UTF-8 patches which can be found at http://www.suse.de/~nadvornik/mc.html. They seem to work quite well for me. Merging them with upcoming 4.6.1 will be a bit more work however.
Is this still an issue on FC3? If so this bug should be transferred to initscripts as it is a configuration issue.
Leonard, I just verified on a fairly up-to-date FC3 system, and yes, it is still an issue.
Sorry for multiple posts - on the same FC3 system, i just verified "export LANG=en_US.UTF-8" and indeed it fixes the display issue with mc in single mode.
Moving to initscripts as this is caused by the locale not being set in single user mode.
Fedora Core 2 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC3 updates or in the FC4 test release, reopen and change the version to match.
*** This bug has been marked as a duplicate of 105653 ***