New MacosVentura 13.1 installed killed zsh

Hello,


Yesterday i had to upgrade my OS. I was on Monterey 12.2 or 12.3 i think, and i needed to get a more recent version. After doing the upload of the last one macOs Ventura. I can't use my terminal and my command line such as cd, code ., npx create ..., ect even a rm -rf i can't.


Each time i try a line command, i get this : zsh: killed [TOOL]

And when i open my terminal i get this on iTerm2 :

zsh: killed     mkdir -p "$ZSH_CACHE_DIR/completions"
zsh: killed
zsh: killed
[6]    5837 killed     ls -G . &> /dev/null


And on my terminal from my mac i get this :

zsh: killed     mkdir -m 700 -p "$SHELL_SESSION_DIR"
zsh: killed     mkdir -p "$ZSH_CACHE_DIR/completions"
zsh: killed     
zsh: killed     
[6]    6021 killed     ls -G . &> /dev/null

So did anyone has an idea of what is happening please. I read a lot of topic here where some people get this issue but without solution.


Hope someone will help me. Thanks you by advance !

MacBook Pro 14″, macOS 13.1

Posted on Jan 16, 2023 06:37 AM

Reply
Question marked as Top-ranking reply

Posted on Jan 16, 2023 10:30 AM

I can't tell you any more than I already have. What you are describing is a typical Homebrew post here on the Apple Support Community. In theory, it is supposed to be a great way to install things like Node, React, etc. without having to learn all the details. Now you have to learn all those details. Homebrew is one of the freebie apps that doesn't provide any support.


If you can't fix it yourself, you'll have to erase the hard drive and reinstall the operating system. You won't be able to restore from backup as that would simply restore your broken Homebrew installation. There are easier ways to fix it, but they all require advanced Terminal, shell, and macOS knowledge that you took a shortcut to avoid learning by installing Homebrew.


I recommend following my advice above to run a new, generic shell. Create a new user account. Use your generic shell to copy the functional dot files from the new account back into your corrupted account. You will either have to change your path to avoid looking at /usr/local or wherever homebrew installs things, or completely uninstall homebrew.

5 replies
Question marked as Top-ranking reply

Jan 16, 2023 10:30 AM in response to JennaDF

I can't tell you any more than I already have. What you are describing is a typical Homebrew post here on the Apple Support Community. In theory, it is supposed to be a great way to install things like Node, React, etc. without having to learn all the details. Now you have to learn all those details. Homebrew is one of the freebie apps that doesn't provide any support.


If you can't fix it yourself, you'll have to erase the hard drive and reinstall the operating system. You won't be able to restore from backup as that would simply restore your broken Homebrew installation. There are easier ways to fix it, but they all require advanced Terminal, shell, and macOS knowledge that you took a shortcut to avoid learning by installing Homebrew.


I recommend following my advice above to run a new, generic shell. Create a new user account. Use your generic shell to copy the functional dot files from the new account back into your corrupted account. You will either have to change your path to avoid looking at /usr/local or wherever homebrew installs things, or completely uninstall homebrew.

Jan 16, 2023 08:04 AM in response to JennaDF

JennaDF wrote:

No i didn't

Anything similar "MacPorts" or "Fink"?


Also, are you sure you didn't install Homebrew? "npx create" is something from React.js. Which I check to see how people recommend installing that (or its various prerequisites like nvm), Homebrew comes right up.


You can always go to the "Shell" menu in Terminal and run "New Command". In the dialog box, you can manually type in the path to a shell like "/bin/zsh" or "/bin/bash". Hopefully that will get you up and running so you can correct whatever damage Homebrew, React, etc. have done to your environment.


In a worst-case scenario, you can even use this as the command in that dialog:

/bin/zsh --no-rcs


This will run zsh without loading any dot files. You can take that opportunity to fix the ones you have and/or rebuild your installation. I recommend keeping a couple of windows open so you always have one that is functional.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

New MacosVentura 13.1 installed killed zsh

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.