MacOS – Terminal prompt does’t show on macOS Sierra

bashmacosterminal

Since I upgraded to Sierra, Terminal no longer loads my bash prompt, making it unusable. When I start it, it doesn't hang, but it stays looking like this:

I can enter text, but it doesn't do anything. It seems like the bash or tail command is hanging. I have also tried using the terminal window in Android Studio and that just shows a blank screen.

Any idea how I could fix this?

Best Answer

After some debugging I found out that the bash-autocompletion package for brew did cause this. It is clear that if you run $(brew --prefix)/etc/bash_completion the command does not terminate

As a wordaround, you can uninstall it with brew uninstall bash-autocompletion. I'd recommend to first update brew by running brew update && brew upgrade though.

Digging deeper it turned out the main problem here was the rust compiler. Running rustc --version pointed me to a segfault. I uninstalled it using /usr/local/lib/rustlib/uninstall.sh, after which the bash autocompletion started to work again. Removing rust as described, and reinstalling it using brew (brew install rust) ensured everything worked again

Related Solutions

MacOS – ssh-under-cron stops working in OS X 10.7 Lion

For anyone who ends up on this page, I realized I should post the answer:

Using launchd instead of cron does indeed fix the authorization problem. Your user launchd jobs (which run only when you are logged in) correctly use the SSH agent information that was unlocked via your keychain as part of login (as part of standard OS X key management, no other software required).

To minimize my interactions with launchd, I created a single launchd job that calls a bash script. In this way I can simply edit the script without dealing with launchd.

Here's the launchd file:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>Label</key>
  <string>com.mycron.hourly</string>

  <key>ProgramArguments</key>
  <array>
    <string>/Users/john/bin/cron.hourly</string>
  </array>

  <key>Nice</key>
  <integer>1</integer>

  <key>StartInterval</key>
  <integer>3600</integer> <!-- start every X seconds -->

  <key>RunAtLoad</key>
  <true/>
</dict>
</plist>

I saved the file to ~/Library/LaunchAgents/com.mycron.hourly.plist, and then loaded it with:

launchctl load ~/Library/LaunchAgents/com.mycron.hourly.plist

Once loaded, it will run right away and then again every 60 minutes.

If you follow the same procedure, you'll want to change the `ProgramArguments' string with the right path to your script.

MacOS – El Capitan Mac: /usr/bin/login tries to run /bin/false

I had the same problem, with emacs giving me "Error (use-package): exec-path-from-shell :init: Searching for program: no such file or directory, /bin/false" on startup. However, I noticed that this only happens when running Emacs (installed from emacsformacosx) from the Dock or Spotlight. If I ran it from my Terminal, or by clicking on it in Applications in finder, it worked fine.

After a restart, the problem was resolved. I suspect that Dock and Spotlight held on to my original default shell, and after a restart, they used the new value (changed from /bin/false to /bin/zsh).

Best Answer

Related Solutions

MacOS – ssh-under-cron stops working in OS X 10.7 Lion

MacOS – El Capitan Mac: /usr/bin/login tries to run /bin/false

Related Question