Enter key not working in terminalBackspace key not workingTerminal not workingTerminal “find” command not...
Hero deduces identity of a killer
Can I say "fingers" when referring to toes?
Invalid date error by date command
PTIJ: Haman's bad computer
Does IPv6 have similar concept of network mask?
On a tidally locked planet, would time be quantized?
What is Cash Advance APR?
What should you do when eye contact makes your subordinate uncomfortable?
Why is it that I can sometimes guess the next note?
Extract more than nine arguments that occur periodically in a sentence to use in macros in order to typset
Non-trope happy ending?
How should I respond when I lied about my education and the company finds out through background check?
When were female captains banned from Starfleet?
Biological Blimps: Propulsion
Using substitution ciphers to generate new alphabets in a novel
This is why we puzzle
Why Shazam when there is already Superman?
Unexpected behavior of the procedure `Area` on the object 'Polygon'
Why did the EU agree to delay the Brexit deadline?
Lowest total scrabble score
What are the advantages of simplicial model categories over non-simplicial ones?
What are the balance implications behind making invisible things auto-hide?
Yosemite Fire Rings - What to Expect?
Are Captain Marvel's powers affected by Thanos' actions in Infinity War
Enter key not working in terminal
Backspace key not workingTerminal not workingTerminal “find” command not workingRight shift key not workingGnome- terminal quits when pressing enterSuper key not workingGnome Terminal: Ctrl key “sticky”Gnome terminal not working (18.04)terminal not working after deleting pythonV key not working, down key stuck only in GRUB
Just now, the enter key has stopped working in a terminal only.
Works in all other apps, but only generates the default system sound when pressed in the terminal.
Tried both xTerm and gnome-terminal, tried restarting.
No joy.
I'm at a loss, because I can't use the terminal to resolve this. It doesn't even work when I use CTRL-ALT-F2 to toggle to a full terminal outside X.
Anyone have any ideas?
All I can think of to do is open bash related configs and clear them after backing them up, but I'd prefer any better ideas.
Being unable to grep or find anything is a large limitation.
This is in Ubuntu 15.10.
gnome-terminal keyboard-layout
asked Apr 5 '16 at 18:00
Ron RubleRon Ruble
1613
bumped to the homepage by Community♦ 13 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
Just now, the enter key has stopped working in a terminal only.
Works in all other apps, but only generates the default system sound when pressed in the terminal.
Tried both xTerm and gnome-terminal, tried restarting.
No joy.
I'm at a loss, because I can't use the terminal to resolve this. It doesn't even work when I use CTRL-ALT-F2 to toggle to a full terminal outside X.
Anyone have any ideas?
All I can think of to do is open bash related configs and clear them after backing them up, but I'd prefer any better ideas.
Being unable to grep or find anything is a large limitation.
This is in Ubuntu 15.10.
gnome-terminal keyboard-layout
asked Apr 5 '16 at 18:00
Ron RubleRon Ruble
1613
bumped to the homepage by Community♦ 13 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
press Ctrl-V and the the Enter Key. What shows up?
– tlund
Apr 5 '16 at 18:42
Pressing CTRL-V and Enter gives ^M
– Ron Ruble
Apr 6 '16 at 13:37
add a comment |
Just now, the enter key has stopped working in a terminal only.
Works in all other apps, but only generates the default system sound when pressed in the terminal.
Tried both xTerm and gnome-terminal, tried restarting.
No joy.
I'm at a loss, because I can't use the terminal to resolve this. It doesn't even work when I use CTRL-ALT-F2 to toggle to a full terminal outside X.
Anyone have any ideas?
All I can think of to do is open bash related configs and clear them after backing them up, but I'd prefer any better ideas.
Being unable to grep or find anything is a large limitation.
This is in Ubuntu 15.10.
gnome-terminal keyboard-layout
asked Apr 5 '16 at 18:00
Ron RubleRon Ruble
1613
Just now, the enter key has stopped working in a terminal only.
Works in all other apps, but only generates the default system sound when pressed in the terminal.
Tried both xTerm and gnome-terminal, tried restarting.
No joy.
I'm at a loss, because I can't use the terminal to resolve this. It doesn't even work when I use CTRL-ALT-F2 to toggle to a full terminal outside X.
Anyone have any ideas?
All I can think of to do is open bash related configs and clear them after backing them up, but I'd prefer any better ideas.
Being unable to grep or find anything is a large limitation.
This is in Ubuntu 15.10.
gnome-terminal keyboard-layout
gnome-terminal keyboard-layout
asked Apr 5 '16 at 18:00
Ron RubleRon Ruble
1613
asked Apr 5 '16 at 18:00
Ron RubleRon Ruble
1613
asked Apr 5 '16 at 18:00
Ron RubleRon Ruble
1613
asked Apr 5 '16 at 18:00
Ron RubleRon Ruble
1613
asked Apr 5 '16 at 18:00
Ron RubleRon Ruble
1613
1613
bumped to the homepage by Community♦ 13 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 13 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
press Ctrl-V and the the Enter Key. What shows up?
– tlund
Apr 5 '16 at 18:42
Pressing CTRL-V and Enter gives ^M
– Ron Ruble
Apr 6 '16 at 13:37
add a comment |
press Ctrl-V and the the Enter Key. What shows up?
– tlund
Apr 5 '16 at 18:42
Pressing CTRL-V and Enter gives ^M
– Ron Ruble
Apr 6 '16 at 13:37
press Ctrl-V and the the Enter Key. What shows up?
– tlund
Apr 5 '16 at 18:42
press Ctrl-V and the the Enter Key. What shows up?
– tlund
Apr 5 '16 at 18:42
Pressing CTRL-V and Enter gives ^M
– Ron Ruble
Apr 6 '16 at 13:37
Pressing CTRL-V and Enter gives ^M
– Ron Ruble
Apr 6 '16 at 13:37
add a comment |
2 Answers
2
active
oldest
votes
Okay, it was something in the generated .profile file. But I don't see what was wrong.
I'm posting this as "Answered", but in case anyone wants to see, here are the contents of .profile; I don't see anything wrong, myself:
# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.
# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022
# if running bash
if [ -n "$BASH_VERSION" ]; then
# include .bashrc if it exists
if [ -f "$HOME/.bashrc" ]; then
. "$HOME/.bashrc"
fi
fi
# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi
answered Apr 6 '16 at 16:20
Ron RubleRon Ruble
1613
add a comment |
I can't tell from that profile, but ensure that you do not leave a empty line at the end. I had this issue with my .bashrc that kept the enter key from working properly.
answered Dec 13 '16 at 21:40
AshleyVidettoAshleyVidetto
1
Makes no sense. Both~/.profileand~/.bashrcare shell script files, and empty lines at the bottom shouldn't make any difference.
– Gunnar Hjalmarsson
Dec 13 '16 at 22:26
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f754175%2fenter-key-not-working-in-terminal%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Okay, it was something in the generated .profile file. But I don't see what was wrong.
I'm posting this as "Answered", but in case anyone wants to see, here are the contents of .profile; I don't see anything wrong, myself:
# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.
# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022
# if running bash
if [ -n "$BASH_VERSION" ]; then
# include .bashrc if it exists
if [ -f "$HOME/.bashrc" ]; then
. "$HOME/.bashrc"
fi
fi
# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi
answered Apr 6 '16 at 16:20
Ron RubleRon Ruble
1613
add a comment |
Okay, it was something in the generated .profile file. But I don't see what was wrong.
I'm posting this as "Answered", but in case anyone wants to see, here are the contents of .profile; I don't see anything wrong, myself:
# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.
# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022
# if running bash
if [ -n "$BASH_VERSION" ]; then
# include .bashrc if it exists
if [ -f "$HOME/.bashrc" ]; then
. "$HOME/.bashrc"
fi
fi
# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi
answered Apr 6 '16 at 16:20
Ron RubleRon Ruble
1613
add a comment |
Okay, it was something in the generated .profile file. But I don't see what was wrong.
I'm posting this as "Answered", but in case anyone wants to see, here are the contents of .profile; I don't see anything wrong, myself:
# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.
# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022
# if running bash
if [ -n "$BASH_VERSION" ]; then
# include .bashrc if it exists
if [ -f "$HOME/.bashrc" ]; then
. "$HOME/.bashrc"
fi
fi
# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi
answered Apr 6 '16 at 16:20
Ron RubleRon Ruble
1613
Okay, it was something in the generated .profile file. But I don't see what was wrong.
I'm posting this as "Answered", but in case anyone wants to see, here are the contents of .profile; I don't see anything wrong, myself:
# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.
# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022
# if running bash
if [ -n "$BASH_VERSION" ]; then
# include .bashrc if it exists
if [ -f "$HOME/.bashrc" ]; then
. "$HOME/.bashrc"
fi
fi
# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi
answered Apr 6 '16 at 16:20
Ron RubleRon Ruble
1613
answered Apr 6 '16 at 16:20
Ron RubleRon Ruble
1613
answered Apr 6 '16 at 16:20
Ron RubleRon Ruble
1613
answered Apr 6 '16 at 16:20
Ron RubleRon Ruble
1613
1613
add a comment |
add a comment |
I can't tell from that profile, but ensure that you do not leave a empty line at the end. I had this issue with my .bashrc that kept the enter key from working properly.
answered Dec 13 '16 at 21:40
AshleyVidettoAshleyVidetto
1
Makes no sense. Both~/.profileand~/.bashrcare shell script files, and empty lines at the bottom shouldn't make any difference.
– Gunnar Hjalmarsson
Dec 13 '16 at 22:26
add a comment |
I can't tell from that profile, but ensure that you do not leave a empty line at the end. I had this issue with my .bashrc that kept the enter key from working properly.
answered Dec 13 '16 at 21:40
AshleyVidettoAshleyVidetto
1
Makes no sense. Both~/.profileand~/.bashrcare shell script files, and empty lines at the bottom shouldn't make any difference.
– Gunnar Hjalmarsson
Dec 13 '16 at 22:26
add a comment |
I can't tell from that profile, but ensure that you do not leave a empty line at the end. I had this issue with my .bashrc that kept the enter key from working properly.
answered Dec 13 '16 at 21:40
AshleyVidettoAshleyVidetto
1
I can't tell from that profile, but ensure that you do not leave a empty line at the end. I had this issue with my .bashrc that kept the enter key from working properly.
answered Dec 13 '16 at 21:40
AshleyVidettoAshleyVidetto
1
answered Dec 13 '16 at 21:40
AshleyVidettoAshleyVidetto
1
answered Dec 13 '16 at 21:40
AshleyVidettoAshleyVidetto
1
answered Dec 13 '16 at 21:40
AshleyVidettoAshleyVidetto
1
1
Makes no sense. Both~/.profileand~/.bashrcare shell script files, and empty lines at the bottom shouldn't make any difference.
– Gunnar Hjalmarsson
Dec 13 '16 at 22:26
add a comment |
Makes no sense. Both~/.profileand~/.bashrcare shell script files, and empty lines at the bottom shouldn't make any difference.
– Gunnar Hjalmarsson
Dec 13 '16 at 22:26
Makes no sense. Both
~/.profile and ~/.bashrc are shell script files, and empty lines at the bottom shouldn't make any difference.– Gunnar Hjalmarsson
Dec 13 '16 at 22:26
Makes no sense. Both
~/.profile and ~/.bashrc are shell script files, and empty lines at the bottom shouldn't make any difference.– Gunnar Hjalmarsson
Dec 13 '16 at 22:26
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f754175%2fenter-key-not-working-in-terminal%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
press Ctrl-V and the the Enter Key. What shows up?
– tlund
Apr 5 '16 at 18:42
Pressing CTRL-V and Enter gives ^M
– Ron Ruble
Apr 6 '16 at 13:37