Why does my OS X Terminal display a blank window instead of a command prompt after installing MySQL?

Question

After installing MySQL 5.1.50 64-bit and running the package that configures MyQL to run at startup, the Terminal app now sporadically display a blank window, like so:

I managed to get the command prompt back after following the instructions from the MacFixIt column at CNET : OS X Terminal displays a blank window instead of a command prompt

However, the Terminal will intermittently go blank and I have to repeat the process again and it's driving me nuts. The CNET article cures the symtoms but the cause of this problem is still unknown. Does anyone has any theories or experiences to share in order to fix this annoying problem permanently?

Solution

A common cause for this is a hung "sudo" process. If you run sudo and it prompts for your password, but you close the terminal, sudo will hang forever waiting for the password, and this blocks any other logins until you kill it.

The solution is to kill the "sudo" process with Activity Monitor.

I believe sudo has been fixed on Mac OS X Lion 10.7 to exit if you close the terminal.

Comments

[JasKerr]

Have you solved this problem?

[GeneQ]

It happened a few more times. Each time used the procedure suggested by CNET to fix it. Then it never happened again (so far). Wish I knew what caused it. Maybe Apple quietly push an update that fixed it.

[Chris Page]

A common source of this is if you run sudo and then close the terminal while it’s waiting for you to enter the password. This hangs sudo, which prevents any further logins. To resolve the issue, use Activity Monitor (or another terminal if you happen to have one open) to kill the sudo process. (Obviously, if there is no sudo process, this isn’t the issue.)

[Chris Page]

By the way, that C|Net article is incorrect about “…you can tell the terminal to specify the shell used and bypass the need to look up account information…” All shells and commands issued by Terminal are run via /usr/bin/login. All the UI is indicating is that the default shell is selected by /usr/bin/login (it looks at your user account info), but if you customize the shell, Terminal just tells /usr/bin/login to use that shell instead of the default. Login still must look up user account information to…login before running the shell or other command.

[GeneQ]

It hngs at the Unix login. (As the title bar of the Terminal shows). Some rights or authentication related stuff perhaps is causing the problem.

[Jacob Valdez]

Killing all java processes has also solved this, for me