mc when run in an xterm has no problems When I try to run mc in a tty without X the screen flashes on/off at about 1/2 second rate with most chars readable & with some garbage. Application is unusable. How reproducible: every time
Add please as an attachment "rpm -qa" result.
CC: (none) => krytarowski
[barry@TheBox ~]$ rpm -qa mc mc-4.7.5.2-2.mga1
Attach all packages. Do you use framebuffer? Does it occur with other applications? Here everything is fine.
only the 1 package involved. Not tested any other apps. I only run without X for some maintenance or checking. Not sure about framebuffer. My installation is standard mageia1 started in runlevel 3 followed by 'startx starticewm' to start X and the wm
Well if you could just type "rpm -qa" WITHOUT "mc" I would try to reproduce it with the same environment on my virtualmachine.
About the framebuffer - if you can see eye candy Mageia theme when the system is booting you have properly set up framebuffer.
Created attachment 1038 [details] list of pkgs unsorted
Created attachment 1039 [details] list of pkgs alpha order
no framebuffer. I boot to runlevel 3 on tty1, then run startx starticewm starts x on tty7
On Mandriva 2010 mc runs correctly on tty2 with x on tty7. On tty7 with X mc runs and is usable but lines bordering the display are replaced with garbage. This may be a problem with char set selection. rpm on mandriva is.... [barry@TheBox ~]$ rpm -qa mc mc-4.7.0-0.pre2.3mdv2010.0 HTH
This problem with mc Solved, but what are the implications of a change? On tty2 (no X) I ran... TERM=linux export TERM and mc runs correctly. Then I did the same under X on tty7 So it looks like mc & utf8 are not compatible
Ok thank you for the solution, I will check it tomorrow.
Some more info..... Before starting X.... Login on tty1 as user. Run 'echo $TERM' gives rxvt-unicode. mc is garbage Login on tty2 as root Run 'echo $TERM' gives linux - mc is ok Then startx from tty1 gives x on tty7, Run 'echo $TERM' in xterm gives 'rxvt-unicode'. mc is ok. TERM appears to be set in my ~/.bashrc
I confirm that TERM=rxvt-unicode makes from mc garbage. List of available terms is in /etc/termcap I don't think then we should consider this as a bug, can we close?
ok closing
Status: NEW => RESOLVEDResolution: (none) => INVALID
Probably not a mageia bug, but if mc runs in an xterm with x but not in a tty without x when in both instances the value of $TERM is 'rxvt-unicode' is this not a fault in the mageia boot routine? Thanks for your help Kamil. Barry
Ok, let me check it again. I've got "xterm" by default and it works fine both in X and tty.
Status: RESOLVED => REOPENEDResolution: INVALID => (none)
OK, I've checked it again. for the same set of packages I just got TERM=linux for a user. If you try to cheat mc and use different TERM type, then it's your fault not the of mc. You can try to set TERM to xterm, or try to set rxvt-unicode with some .X* init scripts for X Window.
Status: REOPENED => RESOLVEDResolution: (none) => INVALID