LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Slackware 14.1 -- MC works poorly with Screen (https://www.linuxquestions.org/questions/slackware-14/slackware-14-1-mc-works-poorly-with-screen-4175486060/)

bleedingturnips 11-27-2013 11:23 AM

Slackware 14.1 -- MC works poorly with Screen
 
I'm a long-time Slackware user. I recently upgraded from 14.0 to 14.1.

I do most of my work at the command line using Screen. Unfortunately, since my upgrade, with I use MC with Screen, MC responds VERY slowly. For example, when I try to scroll through the file tree using the arrow keys, it takes MC several seconds to respond to each key stroke. When I use MC without Screen, it behaves normally.

Has anyone else had this problem?

My computer is a Lenovo ThinkPad W520 if this makes any difference.

Thanks.

JWJones 11-27-2013 11:31 AM

I am using 14.1 with mc and tmux, and all is well, but I have not tried it with screen. Perhaps I'll give it a whirl and report back.

JWJones 11-27-2013 11:58 AM

OK, just tested this on my 32-bit slack 14.1 box, and the problem is the same using mc with either screen or tmux! In a straight tty session, the problem doesn't exist. So now I am curious, too, as to what the issue is.

bleedingturnips 11-27-2013 12:06 PM

Thanks for verifying the issue!

GazL 11-27-2013 12:29 PM

Not seeing the issue here running mc under either screen or tmux in either xterm or rxvt. I did rebuild my mc package however (to patch the passing the directory args on the command line thingy), don't know whether that would make a difference. I would suspect the terminal you're running it under to make a bigger difference. Might be worth trying some others to see if it's just one specific terminal emulator.

This was on 64bit.

Alien Bob 11-27-2013 12:35 PM

I can not reproduce this either, on Slackware 14.1 64-bit (multilib) and KDE's konsole.


Eric

bleedingturnips 11-27-2013 01:06 PM

Thanks, all.

I should add that I'm running Slackware 14.1 64-bit (multilib).

I experience the problem in console mode (no GUI). I haven't tried using screen and mc using xterm or konsole. But I can test a little later and report back. (I don't have my Slackware machine with me at the moment.)

guanx 11-27-2013 02:24 PM

Just stop gpm if you can live without it. You have something in "/var/log/syslog" as keywords for searching the Internet.

Alien Bob 11-27-2013 02:24 PM

Quote:

Originally Posted by bleedingturnips (Post 5071573)
Thanks, all.

I should add that I'm running Slackware 14.1 64-bit (multilib).

I experience the problem in console mode (no GUI). I haven't tried using screen and mc using xterm or konsole. But I can test a little later and report back. (I don't have my Slackware machine with me at the moment.)

Yes, in the console I can reproduce the error.

Eric

bleedingturnips 11-27-2013 02:38 PM

Thanks, Eric, for the confirmation.

Thanks, Guanx. I'll try stopping gpm since I don't use it anyway.

GazL 11-27-2013 04:26 PM

Quote:

Originally Posted by Alien Bob (Post 5071608)
Yes, in the console I can reproduce the error.

Eric

The weird thing is I can't. It seems to be working fine here, but as I said, I've rebuilt mc, and I'm also using linux 3.12.1, which I suppose could also be a factor if there's something not quite right with the kernel tty layer. Most odd.

edit: could be gpm - I don't enable that.

bleedingturnips 11-27-2013 06:21 PM

I'm back on my Slackware machine. I stopped rc.gpm, rebooted, and now MC seems to be behaving properly with Screen.

Thanks, everyone.

qunying 11-27-2013 06:57 PM

I got the same problem on console. It seems related to gpm, once I killed gpm, mc function normally under tmux or screen. (I am running a custom kernel 3.12.1, Slackware64).

But there is one strange behavior, if I run it under root, no such delay happened.


All times are GMT -5. The time now is 04:12 AM.