3

Since I upgraded my M1 MacBook Pro to MacOS Ventura 13.0, the Terminal app does not work correctly.

When I type, for example, rm -rf ..., it gets killed as shown in the screenshot below. I get this response for a lot of other commands in Terminal. In addition, I now get Unexpected Error when I try to build an application in Xcode. Same problems appear with either ZSH or Bash.

enter image description here

enter image description here

enter image description here

enter image description here

10
  • 5
    It is more readable and convenient for others if you paste the text form of commands and outputs from Terminal to your questions rather than the screenshots.
    – Alper
    Commented Oct 25, 2022 at 17:55
  • 3
    Are these the standard built-in command-line tools, or are you using something nonstandard like homebrew? Does this or this help? Commented Oct 25, 2022 at 18:21
  • MBP-von-Daniel:~ danielehrhardt$ ls Killed: 9 I try to use mkdir, ls, rm Commented Oct 25, 2022 at 18:22
  • 1
    Can you try bash and then the commands? Maybe this is some misconfiguration in your zshrc files?
    – vinibrsl
    Commented Oct 25, 2022 at 18:34
  • bash Killed: 9 also happening with bash Commented Oct 25, 2022 at 18:41

1 Answer 1

-1

At first i thought that chmod fixed the Issue but then i opned iTerm with ZSH and had the same killed Issue again. I ended up also deleting all content from /usr/local/bin and changed my Path Variable to use the /bin folder.

/bin/chmod 755 /usr/local/bin
6
  • How did that directory get corrupted?
    – mmmmmm
    Commented Oct 25, 2022 at 20:33
  • macOS Ventura update Commented Oct 25, 2022 at 20:33
  • 1
    Which permissions did the directory have before the chmod?
    – nohillside
    Commented Oct 25, 2022 at 21:30
  • Same problem but I would advise care, only delete files that are already present in /bin, not everything ! Commented Nov 22, 2022 at 12:36
  • I have the same issue. I even tried reinstalling ventura again. What do you suggest? Uninstall commandlineTools or delete usr/local/bin contents'; the latter seems little dangerous. @DanielEhrhardt Commented Dec 1, 2022 at 11:01

You must log in to answer this question.

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