Terminal is broken! [on hold]
So my terminal is broken. I can open the terminal window using any of the methods listed below, but there is no prompt, and it's like it's stuck just about to give me a prompt but nothing.
- Alt + Ctrl + T
- clicking on the shortcut in "favorites" bar
- opening to a tty with alt + ctrl + F3 (this method allows me to log into the system, but as soon as I log in it's the same as the other two methods.)
Unfortunately, all the methods I know of to try and fix this issue won't work because they all inolve a CLI!
I was using Fish as my shell, although occasionally dropping into Bash for various things, all with no problem. I did update my system per the weekly software updates notification (this was done on 19 January 2019.) I'm fairly sure their was a kernel update, but I don'w remember anything having to do with the command line.
This is 18.10 Ubuntu (oosmic cuttlefish) using a vanilla minimalist install from bare metal (GPT, EFI) on an Asus VivoBook S530U. Any questions gladly answered.
Thanks y'all!
Pam
command-line 18.10 tty
asked Jan 20 at 17:11
pamdemoniapamdemonia
72
put on hold as off-topic by pomsky, Zanna, Kulfy, Eric Carvalho, Charles Green 2 days ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – pomsky, Zanna, Kulfy, Eric Carvalho, Charles Green
If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
So my terminal is broken. I can open the terminal window using any of the methods listed below, but there is no prompt, and it's like it's stuck just about to give me a prompt but nothing.
- Alt + Ctrl + T
- clicking on the shortcut in "favorites" bar
- opening to a tty with alt + ctrl + F3 (this method allows me to log into the system, but as soon as I log in it's the same as the other two methods.)
Unfortunately, all the methods I know of to try and fix this issue won't work because they all inolve a CLI!
I was using Fish as my shell, although occasionally dropping into Bash for various things, all with no problem. I did update my system per the weekly software updates notification (this was done on 19 January 2019.) I'm fairly sure their was a kernel update, but I don'w remember anything having to do with the command line.
This is 18.10 Ubuntu (oosmic cuttlefish) using a vanilla minimalist install from bare metal (GPT, EFI) on an Asus VivoBook S530U. Any questions gladly answered.
Thanks y'all!
Pam
command-line 18.10 tty
asked Jan 20 at 17:11
pamdemoniapamdemonia
72
put on hold as off-topic by pomsky, Zanna, Kulfy, Eric Carvalho, Charles Green 2 days ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – pomsky, Zanna, Kulfy, Eric Carvalho, Charles Green
If this question can be reworded to fit the rules in the help center, please edit the question.
Do you just have no prompt or doesn't the terminal respond at all? Can you typelsin the terminal?
– PerlDuck
Jan 20 at 17:18
I have a cursor blinking but no prompt. Can't type a tbing. Tried to do the repair through grub, but nothing happened.
– pamdemonia
Jan 20 at 17:39
Does it work to boot from a USB pendrive - and in that case do the repair, that you want to do but cannot do in the installed operating system because of the problem with the terminal windows?
– sudodus
Jan 20 at 19:51
i tried that, but couldn't remember the commands. I did install Synaptic and installed xterm as an experiment, but it's doing the same thing. it feels like there is some config file that got erased or some other lower level thing, Aargh. very annoying! I really wish I knew more shell scripting, cuz maybe that would work.
– pamdemonia
Jan 20 at 21:09
1
okay, so for some reason I could open a terminal from the anaconda navigator app, and now it's working again! Strange. But fixed!
– pamdemonia
Jan 21 at 5:16
add a comment |
So my terminal is broken. I can open the terminal window using any of the methods listed below, but there is no prompt, and it's like it's stuck just about to give me a prompt but nothing.
- Alt + Ctrl + T
- clicking on the shortcut in "favorites" bar
- opening to a tty with alt + ctrl + F3 (this method allows me to log into the system, but as soon as I log in it's the same as the other two methods.)
Unfortunately, all the methods I know of to try and fix this issue won't work because they all inolve a CLI!
I was using Fish as my shell, although occasionally dropping into Bash for various things, all with no problem. I did update my system per the weekly software updates notification (this was done on 19 January 2019.) I'm fairly sure their was a kernel update, but I don'w remember anything having to do with the command line.
This is 18.10 Ubuntu (oosmic cuttlefish) using a vanilla minimalist install from bare metal (GPT, EFI) on an Asus VivoBook S530U. Any questions gladly answered.
Thanks y'all!
Pam
command-line 18.10 tty
asked Jan 20 at 17:11
pamdemoniapamdemonia
72
So my terminal is broken. I can open the terminal window using any of the methods listed below, but there is no prompt, and it's like it's stuck just about to give me a prompt but nothing.
- Alt + Ctrl + T
- clicking on the shortcut in "favorites" bar
- opening to a tty with alt + ctrl + F3 (this method allows me to log into the system, but as soon as I log in it's the same as the other two methods.)
Unfortunately, all the methods I know of to try and fix this issue won't work because they all inolve a CLI!
I was using Fish as my shell, although occasionally dropping into Bash for various things, all with no problem. I did update my system per the weekly software updates notification (this was done on 19 January 2019.) I'm fairly sure their was a kernel update, but I don'w remember anything having to do with the command line.
This is 18.10 Ubuntu (oosmic cuttlefish) using a vanilla minimalist install from bare metal (GPT, EFI) on an Asus VivoBook S530U. Any questions gladly answered.
Thanks y'all!
Pam
command-line 18.10 tty
command-line 18.10 tty
asked Jan 20 at 17:11
pamdemoniapamdemonia
72
asked Jan 20 at 17:11
pamdemoniapamdemonia
72
asked Jan 20 at 17:11
pamdemoniapamdemonia
72
asked Jan 20 at 17:11
pamdemoniapamdemonia
72
asked Jan 20 at 17:11
pamdemoniapamdemonia
72
72
put on hold as off-topic by pomsky, Zanna, Kulfy, Eric Carvalho, Charles Green 2 days ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – pomsky, Zanna, Kulfy, Eric Carvalho, Charles Green
If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as off-topic by pomsky, Zanna, Kulfy, Eric Carvalho, Charles Green 2 days ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – pomsky, Zanna, Kulfy, Eric Carvalho, Charles Green
If this question can be reworded to fit the rules in the help center, please edit the question.
Do you just have no prompt or doesn't the terminal respond at all? Can you typelsin the terminal?
– PerlDuck
Jan 20 at 17:18
I have a cursor blinking but no prompt. Can't type a tbing. Tried to do the repair through grub, but nothing happened.
– pamdemonia
Jan 20 at 17:39
Does it work to boot from a USB pendrive - and in that case do the repair, that you want to do but cannot do in the installed operating system because of the problem with the terminal windows?
– sudodus
Jan 20 at 19:51
i tried that, but couldn't remember the commands. I did install Synaptic and installed xterm as an experiment, but it's doing the same thing. it feels like there is some config file that got erased or some other lower level thing, Aargh. very annoying! I really wish I knew more shell scripting, cuz maybe that would work.
– pamdemonia
Jan 20 at 21:09
1
okay, so for some reason I could open a terminal from the anaconda navigator app, and now it's working again! Strange. But fixed!
– pamdemonia
Jan 21 at 5:16
add a comment |
Do you just have no prompt or doesn't the terminal respond at all? Can you typelsin the terminal?
– PerlDuck
Jan 20 at 17:18
I have a cursor blinking but no prompt. Can't type a tbing. Tried to do the repair through grub, but nothing happened.
– pamdemonia
Jan 20 at 17:39
Does it work to boot from a USB pendrive - and in that case do the repair, that you want to do but cannot do in the installed operating system because of the problem with the terminal windows?
– sudodus
Jan 20 at 19:51
i tried that, but couldn't remember the commands. I did install Synaptic and installed xterm as an experiment, but it's doing the same thing. it feels like there is some config file that got erased or some other lower level thing, Aargh. very annoying! I really wish I knew more shell scripting, cuz maybe that would work.
– pamdemonia
Jan 20 at 21:09
1
okay, so for some reason I could open a terminal from the anaconda navigator app, and now it's working again! Strange. But fixed!
– pamdemonia
Jan 21 at 5:16
Do you just have no prompt or doesn't the terminal respond at all? Can you type
ls in the terminal?– PerlDuck
Jan 20 at 17:18
Do you just have no prompt or doesn't the terminal respond at all? Can you type
ls in the terminal?– PerlDuck
Jan 20 at 17:18
I have a cursor blinking but no prompt. Can't type a tbing. Tried to do the repair through grub, but nothing happened.
– pamdemonia
Jan 20 at 17:39
I have a cursor blinking but no prompt. Can't type a tbing. Tried to do the repair through grub, but nothing happened.
– pamdemonia
Jan 20 at 17:39
Does it work to boot from a USB pendrive - and in that case do the repair, that you want to do but cannot do in the installed operating system because of the problem with the terminal windows?
– sudodus
Jan 20 at 19:51
Does it work to boot from a USB pendrive - and in that case do the repair, that you want to do but cannot do in the installed operating system because of the problem with the terminal windows?
– sudodus
Jan 20 at 19:51
i tried that, but couldn't remember the commands. I did install Synaptic and installed xterm as an experiment, but it's doing the same thing. it feels like there is some config file that got erased or some other lower level thing, Aargh. very annoying! I really wish I knew more shell scripting, cuz maybe that would work.
– pamdemonia
Jan 20 at 21:09
i tried that, but couldn't remember the commands. I did install Synaptic and installed xterm as an experiment, but it's doing the same thing. it feels like there is some config file that got erased or some other lower level thing, Aargh. very annoying! I really wish I knew more shell scripting, cuz maybe that would work.
– pamdemonia
Jan 20 at 21:09
1
1
okay, so for some reason I could open a terminal from the anaconda navigator app, and now it's working again! Strange. But fixed!
– pamdemonia
Jan 21 at 5:16
okay, so for some reason I could open a terminal from the anaconda navigator app, and now it's working again! Strange. But fixed!
– pamdemonia
Jan 21 at 5:16
add a comment |
1 Answer
1
active
oldest
votes
So I turned off my machine for awhile, right after reinstalling both gnome-terminal and the libvte package using synaptic. I was still having a problem, but then almost without thinking I opened a terminal in a specific conda environment using the Anaconda Navigator application and it gave me a working terminal window. So now it's all working again.
If nothing else, this whole experience has reminded me of how much I enjoy Linux, even when it's being a pain in the butt!
that is all
pam
answered Jan 21 at 5:23
pamdemoniapamdemonia
72
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
So I turned off my machine for awhile, right after reinstalling both gnome-terminal and the libvte package using synaptic. I was still having a problem, but then almost without thinking I opened a terminal in a specific conda environment using the Anaconda Navigator application and it gave me a working terminal window. So now it's all working again.
If nothing else, this whole experience has reminded me of how much I enjoy Linux, even when it's being a pain in the butt!
that is all
pam
answered Jan 21 at 5:23
pamdemoniapamdemonia
72
add a comment |
So I turned off my machine for awhile, right after reinstalling both gnome-terminal and the libvte package using synaptic. I was still having a problem, but then almost without thinking I opened a terminal in a specific conda environment using the Anaconda Navigator application and it gave me a working terminal window. So now it's all working again.
If nothing else, this whole experience has reminded me of how much I enjoy Linux, even when it's being a pain in the butt!
that is all
pam
answered Jan 21 at 5:23
pamdemoniapamdemonia
72
add a comment |
So I turned off my machine for awhile, right after reinstalling both gnome-terminal and the libvte package using synaptic. I was still having a problem, but then almost without thinking I opened a terminal in a specific conda environment using the Anaconda Navigator application and it gave me a working terminal window. So now it's all working again.
If nothing else, this whole experience has reminded me of how much I enjoy Linux, even when it's being a pain in the butt!
that is all
pam
answered Jan 21 at 5:23
pamdemoniapamdemonia
72
So I turned off my machine for awhile, right after reinstalling both gnome-terminal and the libvte package using synaptic. I was still having a problem, but then almost without thinking I opened a terminal in a specific conda environment using the Anaconda Navigator application and it gave me a working terminal window. So now it's all working again.
If nothing else, this whole experience has reminded me of how much I enjoy Linux, even when it's being a pain in the butt!
that is all
pam
answered Jan 21 at 5:23
pamdemoniapamdemonia
72
answered Jan 21 at 5:23
pamdemoniapamdemonia
72
answered Jan 21 at 5:23
pamdemoniapamdemonia
72
answered Jan 21 at 5:23
pamdemoniapamdemonia
72
72
add a comment |
add a comment |
Do you just have no prompt or doesn't the terminal respond at all? Can you type
lsin the terminal?– PerlDuck
Jan 20 at 17:18
I have a cursor blinking but no prompt. Can't type a tbing. Tried to do the repair through grub, but nothing happened.
– pamdemonia
Jan 20 at 17:39
Does it work to boot from a USB pendrive - and in that case do the repair, that you want to do but cannot do in the installed operating system because of the problem with the terminal windows?
– sudodus
Jan 20 at 19:51
i tried that, but couldn't remember the commands. I did install Synaptic and installed xterm as an experiment, but it's doing the same thing. it feels like there is some config file that got erased or some other lower level thing, Aargh. very annoying! I really wish I knew more shell scripting, cuz maybe that would work.
– pamdemonia
Jan 20 at 21:09
1
okay, so for some reason I could open a terminal from the anaconda navigator app, and now it's working again! Strange. But fixed!
– pamdemonia
Jan 21 at 5:16