Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This morning I bumped into something I've never seen before and I can't seem to find a way to fix it. I was inspecting a large bzipped tarball (e.g. tar jtf myfile.tar.bz2) and before it completed, I hit Ctrl+C to abort the output since I'd seen as much as I needed to see. The output stopped and the prompt appeared.

So far, nothing out of the ordinary, but then I tried to type. And nothing appeared. And the cursor didn't move. Or blink. What I typed did register, though. Although there's no visible indication that I had done anything, the command I typed executed when I pressed Enter. The Enter key does work.

Has anyone ever seen this? Any idea how I can get back to zero without having to quit and relaunch terminal?


share|improve this question
up vote 8 down vote accepted

It happens sometime that the shell get all messed up.
I found that sending a reset give me back my prompt.
I found 2 ways to do that:
1- Using the mouse to select Shell > Send Reset (command-R)
2- typing reset in the terminal

Hope this helps!

share|improve this answer
I'd love to know why the shell gets messed up, but this really did help. I can reproduce the issue at will, but as soon as I type reset (even though I can't see it) and hit Enter...poof! Good as new. Thank you. – Rob Wilkerson Aug 18 '10 at 19:38

I've experienced the exact same thing. I run a bash script which calls "matlab -nodisplay", then runs a matlab subroutine, then quits. When I get back to the terminal, I can no longer see the cursor, although everything that I type does register. Typing "reset" fixes the problem.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .