3

Problem: After updating iTerm2 to version 3.3.6, I started getting the following message whenever opening iTerm2 or opening a new tab in iTerm2.

Login incorrect
login:

I could then login and use the iTerm as normal, but would get the same message and prompt whenever opening a new tab.

Workaround: If I go to Preferences > Profiles and change the Working Directory setting from "Home directory" to "Directory:", then enter the path to my home directory, this fixes the problem.

Question: I'm trying to understand and fix the underlying problem. Given the above workaround, it seems that iTerm2 thinks my home directory is somewhere else. Any ideas?

Extra details: I'm running MacOS 10.14.5. My username and home directory contains a space. Someone suggested that this might be part of the problem, but if the space is causing a problem, that doesn't explain why it only became an issue after updating iTerm.

Improve this question
5
  • 1
    I'm running High Sierra and iTerm 3.3.6 and I cannot reproduce your problem. It works fine on my machine. Do you have something strange in your .bash_profile file. – Natsfan Oct 11 '19 at 17:16
  • Thanks. I tried deleting my .bash_profile and .bashrc files from my home directory, and the problem persisted. Does your home directory contain a space? – srcerer Oct 11 '19 at 17:37
  • no, my home directory does not contain a space. – Natsfan Oct 11 '19 at 17:40
  • 1
    I'm seeing this issue now and my home directory does happen to contain an apostrophe - ' . (not recommended btw) – ryryguy Nov 7 '19 at 22:39
  • Does the workaround work for you? I'm trying to decide if I should post it as the answer. – srcerer Nov 8 '19 at 13:19
1

Go to Preferences > Profiles and change the Working Directory setting from "Home directory" to "Directory:", then enter the path to your home directory. If your home directory contains spaces or special characters, this might fix the problem.

However, this doesn't explain the underlying cause of the problem, and is not an ideal solution. I'm posting this as the answer since it has worked for at least two people.

Improve this answer
0

My fix: I had the same issue with iTerm2 v3.3.12. My fix was to quit and restart iterm2. I had tmux up and running so I did not lose any of my sessions. - E

Improve this answer

You must log in to answer this question.

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