3

so my Ubuntu 20.04 is behaving weirdly, i am unable to launch Terminal. Whenever i click on the icon it gives me the loading animation and then nothing happens. I didn't even installed anything special that will cause something like this. Help me with this. Thanks !!

vatsalay
  • 343

2 Answers2

0

if you can open the .bashrc with a text application like 'Text Editor' edit it as advised by Thiago Rider Augusto in I messed up my .bashrc

  1. Click in Ubuntu icon (the first bottom in side menu).
  2. Write gedit
  3. Open Text Editor clicking in its icon.
  4. Click in Open.
  5. In the list, write: ~/.bashrc
  6. Enter
  7. Clean your failing .bashrc file.
  8. Save and you can open terminal again.

second option is to default your .bashrc -

ADVISABLE YOU MAKE A COPY OF THIS FILE BEFORE REPLACING IT - (just make a copy, rename a backup when you go to that file in the file manager in /etc/skel/)

see if you can switch TTY with CTRL-ALT-F4, login and run this below

Finally, use the following command in your terminal to replace the >~/.bashrc with a fresh copy,

/bin/cp /etc/skel/.bashrc ~/

It will replace your corrupt ~/.bashrc with a fresh one. After that, you >need to source the ~/.bashrc so that the change takes place immediately, >write in the terminal,

. ~/.bashrc

or,

source ~/.bashrc

as mentioned by souravc default .bashrc

then CTRL-ALT-F1 to return -

-2

Posting because I had the same issue. Have you updated Python recently??

I tried a bunch of things everywhere. Here's what I eventually found that worked. It turned out when I updated python, it updated what gnome-terminal was set to. Here's what ya do:

Ctrl + Alt + F3, this will open a terminal

login

type sudo vim /usr/bin/gnome-terminal substitute vim for whatever editor you have if needed

check the comment at the top does it read #!/usr/bin/python3? If so, change it to the version you're using of python.

I was updating to 3.9 so I changed it to #!/usr/bin/python3.9. This fixed the issue and allowed me to open the terminal. Update it to whichever version you're using.

The issue was caused by when I updated python, for some reason it changed the gnome-terminal to just generically be python, instead of the python version I was actually using.