terminal app stuck with process completed message

Depending on how you have Terminal configured, pressing a control-d may show a process completed message, or close the Terminal window. A process completed doesn't mean the Terminal is hung, it means that you have quit the running shell, need to either quit Terminal, or select a Shell -> New Window (or Tab) to produce another window with an active shell running in it.

On my M1 Pro running macOS 12.2.1, when I press a control-d in the Terminal, its open window vanishes, though the Terminal application remains running in the menu bar.

premsagar_ wrote:

When I open any new shell or new window, it stucks with the above process completed message without doing anything.

This sounds like something has been added to your shell profile. You will likely need to replace the shell profile file with an older copy from a backup or perhaps you can create a new admin user account which you can use to edit the profile file for the main account (or you can do so while booted into Recovery Mode). I'll have to leave the precise details to another contributor since it may take time to explain the process depending on how familiar you are with the command line. Plus I have a limited knowledge of these profiles especially on a Mac.

Seriously suggest updating Big Sur to Current version 11.6.4

User wrote " On my macos 11.0.1, I am stuck at following screen in terminal "

You may have an app or script that utilizes the command line Terminal and leaves this Terminal window open after the app finishes. It shows poor programming with the developer as it is possible to have the Terminal window to automatically close after an app/script has run. No app or script should ever launch a Terminal window AND leave it open after the app/script has finished. What app or script have you installed or run which is opening the Terminal window when it is run? Check your Login items as one possible source if you are not manually running the app/script which is causing the Terminal window to open.

Do you have your Termina Preferences panel > Profiles tab > Shell tab configured as below:

If you are running any command or script on startup in the Terminal, its completion signal, or how it exits, may cause the current Terminal session to hang up (quit), just as if you had pressed cmd+D.