Ask Your Question

Why does midnight commander take too much time to start or hang at a blinking cursor?

asked 2011-11-15 12:55:33 -0500

FranciscoD_ gravatar image

updated 2014-09-28 15:34:12 -0500

mether gravatar image

I've just started using midnight-commander. It's an amazing amazing tool. I have one issue though, it takes quite a while to start up sometimes. Sometimes it starts up immediately, while in other cases, it just has the cursor blinking. Has anyone experienced this? Any work arounds? I did find this, but I'm unsure if I should use it. I'm using it inside my byobu(gnu screen) session, if that makes a difference. My terminal emulator is the default gnome-terminal.

edit retag flag offensive close merge delete

3 Answers

Sort by ยป oldest newest most voted

answered 2011-11-16 01:13:53 -0500

lzap gravatar image

Sometimes Midnight Commander do not want to come up when you are running it with bad configuration for X Window Server. For example you are running it through ssh on a server where the DISPLAY IP is firewalled, then MC sometimes "freeze" for about 30 seconds during the start.

The solution is to try this:

DISPLAY= mc -ab --nomouse

If it helps, try to delete one option after another to see what causes this. It also can be Samba or NFS - check your Midnight configuration (or delete it just for a test). More info here:

edit flag offensive delete link more


I haven't used it over ssh, this is just on the local machine.. For some reason, "mc -x" starts immediately.

FranciscoD_ gravatar imageFranciscoD_ ( 2011-11-16 08:42:13 -0500 )edit

answered 2011-11-15 23:48:55 -0500

asto gravatar image

Works fine for me. Other than the minor annoyance of having to disable terminal shortcuts before I could use MC shortcuts.

edit flag offensive delete link more

answered 2015-04-13 09:20:04 -0500

x-yuri gravatar image

PROMPT_COMMAND might be causing it.

edit flag offensive delete link more

Question Tools


Asked: 2011-11-15 12:55:33 -0500

Seen: 4,577 times

Last updated: Nov 16 '11