Trouble with Terminal on MacOS Monterey

Johnson44uuu wrote:

Also, i tried booting into safe mode, same issue happens as well

Testing in Safe Mode is always a good idea.

In this case, it is not surprising that the problem remains, because as far as we can tell this has something to do with the shell settings, like that PATH going through /opt/... first.

We need to determine how these go into your PATH.

There is another way to put directories in the PATH: via /etc/paths and /etc/paths.d

Let's see if that is where the homebrew thing gets there.

In Finder, press Command-Shift-G and paste

/etc

Locate the file named "paths" in this folder. Control-click and choose Open With->TextEdit.

Do not make any changes to this file. What does it contain?

In Finder, press Command-Shift-G and paste

/etc/paths.d

What files does this folder contain?

Trying to avoid a reinstall of the OS.

Does the following work in Terminal, and if so, what is the result?

echo $PATH

Also: while we are trying to figure out the issue with zsh, you may want to try and see if other shells do work, like bash.

You can go to Terminal->Preferences->Profiles, duplicate your favorite profile and in the copy change the shell to bash.

Open a new window with that profile. Does it work?

Try using the Finder to rename the .zshrc file: go to your home folder, press Command-Shift-period to toggle invisible files, then rename it .zshrc-old.

Start Terminal again. Any progress?

I saw something about this, sorry I can't find it right now; but it had to do with installing homebrew in an M1 mac.

Do you have homebrew? If so, see if it needs to be updated, or if you can uninstall it.

On another direction: try deactivating the .zshrc file and see if that helps:

mv ~/.zshrc ~/.zshrc-old

and quit and restart Terminal.

Johnson44uuu wrote:

The paths.d folder, only contains my `go` text file, with this content

/usr/local/go/bin

Use the Finder to delete that file or move it somewhere else.

Then, create a new administrator account on your computer. From that account, you can "sudo zsh" or "su -l <old account>" (that's a lowercase L) and correct the startup files.

I can't tell you what you need to correct because I have no idea what Homebrew has done.

What happens when the Terminal command man ls or man mkdir is run ?

To be honest - there appears to be some corruption of some type of file associated with Terminal.

That will require a More Learned Colleague to pickup this question and provide some insights or solutions.

Johnson44uuu wrote:

That didn't fix it either. I still get the same errors

That was a self-supporting recommendation. Once you correct the startup files, then it must, by definition, then be fixed. If you still get the same errors, then you haven't fixed the startup files.

Sorry about that. From your description, it sounded like a new account would be immune to the corruption. But I guess Homebrew is more thorough than that. In the future, I will just skip right to your solution.

The only time I have seen something list this was below link

Please help - Terminal.app keeps crashing upon reopening - macoS Monterey version 12.4