Only recently, when I launch Terminal in Mavericks, the system becomes unresponsive temporarily: the spinning wheel appears; I can still move the mouse pointer but nothing responds; if Activity Monitor is running, it doesn't update any activity; the seconds indicator of the digital clock on the menu bar stops ticking. Terminal displays 'login' on the title bar. After 5 minutes, Terminal displays 'Log in timed out after 300 seconds' and the system becomes responsive again.
I have tried the following to no avail:
- Deleted the plist file (~/Library/Preferences/com.apple.Terminal.plist) and restarted the system. This tells me it is not due to the corrupt plist file.
- Used another user to log-in to the system and launched Terminal. This tells me the problem is not user-specific.
I enabled Remote Login in System Preferences and logged in from another computer using SSH. I get the password prompt immediately. However, only after about five minutes, do I get a command prompt. Again, during this time, if I go back to the computer, the system is unresponsive. When I get the command prompt, I can browse and navigate the files without any delay (discarding the network latency). I am trying to use the terminal to run git commands. Perhaps, the the following is related: if I run ssh-add to add my github key, it says: Could not open a connection to your authentication agent. Before, I was able to run ssh-add without any problems.
Any idea what is going on and how to fix this?
You said you encounter this problem with multiple users. Did you also encounter it with the guest profile?
– Vincent Sep 24 '14 at 13:52.bashrcor.bash_profilesince user3104465 checked this problem isn't user-specific. – dan Sep 24 '14 at 14:29.bashrcandbash_profile. The former used to havessh-addcommand and the latter sourced arvmfile for Ruby. I have removed those but that didn't make a difference. I have also enabled the guest login. Launching Terminal under the guest account causes the same freeze. Another thing I have noticed is the same amount of delay occurs when logging in through the log-in screen after the reboot. My guess is there is something that is causing severe delays in the log-in process. While Terminal times out, but SSH and the log-in screen don't. – user3104465 Sep 24 '14 at 14:50