Why won't the Terminal log in?

Discussion in 'Mac Apps and Mac App Store' started by Zach808, Mar 21, 2010.

  1. Zach808 macrumors newbie

    Joined:
    Mar 21, 2010
    #1
    It was working fine until yesterday, and now when I open it, all I get is a blank screen, and it's stuck at "Login", and I can't use it. What happened, and how can I fix it?
     
  2. Zach808 thread starter macrumors newbie

    Joined:
    Mar 21, 2010
    #3
    Tried it. Helped it work once, but then same problem.
     
  3. MacManiac76 macrumors 65816

    MacManiac76

    Joined:
    Apr 21, 2007
    Location:
    Arizona
    #4
    Can you post a screenshot of what your Terminal looks like? Will make it a little easier to grasp what is happening on your system.
     
  4. Zach808 thread starter macrumors newbie

    Joined:
    Mar 21, 2010
    #5
    Here's what happened:

    [​IMG]

    Edit: Whoops, sorry. I'd like to delete this accidental post.
     
  5. Zach808 thread starter macrumors newbie

    Joined:
    Mar 21, 2010
    #6
    Here's what it looks like:

    [​IMG]

    Normally it just logs me in and lets me type a command, but it's just stuck here.
     
  6. TuffLuffJimmy macrumors G3

    TuffLuffJimmy

    Joined:
    Apr 6, 2007
    Location:
    Portland, OR
    #7
    learn how to attach a picture, bro.

    Click this button, [​IMG], next to the smiley face and upload your picture.
     
  7. Zach808 thread starter macrumors newbie

    Joined:
    Mar 21, 2010
  8. MacManiac76 macrumors 65816

    MacManiac76

    Joined:
    Apr 21, 2007
    Location:
    Arizona
    #9
    Have you checked out your Terminal preferences? Check the Startup section and the Shell tab in the Settings section to see if anything is out of sorts there.
     
  9. angelwatt Moderator emeritus

    angelwatt

    Joined:
    Aug 16, 2005
    Location:
    USA
    #10
    This can happen sometimes when the .profile or .bash_profile file has commands that crash the login. Are you able to type anything in your Terminal window? The above files are hidden so you won't see them in Finder unless you've turned on hidden files. They are located in your home folder, though not everyone has them by default. You can use the Secrets preference panel to turn on hidden files. If you have the above mentioned files you can rename them and see if Terminal starts up normally. If so, then there's something wrong in the file.
     
  10. Zach808 thread starter macrumors newbie

    Joined:
    Mar 21, 2010
    #11
    I can type in the window, but it doesn't do anything. And I've tried renaming the .profile file, but it didn't do anything. I didn't see a .bash_profile file there.
     
  11. angelwatt Moderator emeritus

    angelwatt

    Joined:
    Aug 16, 2005
    Location:
    USA
    #12
    Go to Terminal preferences and on the Startup tab, switch the bottom radio to the second item and set it to /bin/bash and see if that makes a difference. Also, since it lets you type try doing /bin/ls and see if it lists the current directory.
     
  12. SDub90 macrumors 6502a

    Joined:
    Nov 9, 2009
    Location:
    Long Island
    #13
    Sorry to bring up this thread - but I've been having this problem for roughly a month and I FINALLY figured out the solution. Next time it happens, just open up Activity Monitor and check to see if there is a "sudo" command still running. If there is, just quit the process and restart terminal.

    My problem was occured when my system would be under heavy load and I'd have an apple script that would delete a set of files run. It wouldn't run the last command in the proper terminal window so the "rm" command would still have the password prompt open. Another applescript would close all terminal windows and the password prompt would leave the sudo process running.
     
  13. Makosuke macrumors 603

    Joined:
    Aug 15, 2001
    Location:
    The Cool Part of CA, USA
    #14
    Wanted to add a thanks for the final, highly useful tip in this thread.

    I had the same thing happen, in my case because I had some .command batch files that included sudo, and I'd accidentally closed one of the Terminal windows while this was still asking for a prompt. I'd expected it to kill the process, but instead the sudo was sitting there waiting, and locking up new Terminal windows.

    I could see all the login processes sitting there in Activity Monitor--one for each window I tried to open, all of which refused to Force Quit--but didn't realize there was also a sudo sitting somewhere that was the actual problem.

    Surprising that, of all the things that came up in a Google search for blank terminal windows or stuck login processes, none suggested this.
     
  14. markozga1, Apr 19, 2012
    Last edited: Apr 19, 2012

    markozga1 macrumors newbie

    Joined:
    Apr 19, 2012
    #15

    This is the solution that worked for me, thank you kindly.
     

Share This Page