I can't type a “b” when I'm in the command line

Update

I can't even paste a b. I am trying to upgrade to Ubuntu 15.04 but I need to delete some files in the /boot directory. When I cd /oot I can't type a b. So, I thought, I will list the files in the / directory and copy/paste, but to no avail. I can't even paste a b.

Update 2

I recently added some lines to the /etc/inputrc file in order to get better tab auto-completion:

set completion-ignore-case on

set show-all-if-ambiguous on

TAB: menu-complete

bind TAB:menu-complete

Original Question

When I ssh into my ubuntu server I can't type the letter "b". I can however type a capital "B" using either shift keys.

I'm using a MacBook Pro with Retina display from 2012, and I'm ssh-ing into a custom built ubuntu box. It is here that I can't type a lower case "b".

I have restarted the server and yet I still can't type a "b". Every other letter is fine.

It hasn't done that before, I've had the server up and running for about two years and haven't come across an issue like this before. I also haven't done anything notable to cause it to do that.

At first I thought the keyboard was a little sticky but when I closed the connection it works fine. I've restarted the server, ssh'd back in and the "b" key stops working again.

I've tried my bluetooth keyboard and still no luck.

Could this be something that is a rule in a .profile or .bashrc file or something similar? A setting to not allow certain characters.

When I try to type the letter "b" I get the terminal bell sound as if it is not allowed.

edited May 3 '15 at 12:00

muru

asked Apr 30 '15 at 19:14

Mike

103110

Does it work when not using ssh?

– s3lph
Apr 30 '15 at 20:36

1

Please add this to your question using the edit button under your post.

– s3lph
Apr 30 '15 at 20:38

2

I don't think it is that as it is fine everywhere else. It's a MacBook Pro so I doubt it is a fault like that. It is too consistent to only occur in this state that I am sure it is something else.

– Mike
May 1 '15 at 9:54

2

Not in .profile or .bashrc, but probably in .inputrc or /etc/inputrc (readline's config file) it could be a lone b letter on its own row.

– egmont
May 3 '15 at 11:05

1

I'll update my question with those lines that I added, and if you update your answer to say to remove them then I can award you the 50 rep.

– Mike
May 3 '15 at 11:30

|
show 4 more comments

Update

Update 2

I recently added some lines to the /etc/inputrc file in order to get better tab auto-completion:

set completion-ignore-case on

set show-all-if-ambiguous on

TAB: menu-complete

bind TAB:menu-complete

Original Question

When I ssh into my ubuntu server I can't type the letter "b". I can however type a capital "B" using either shift keys.

I'm using a MacBook Pro with Retina display from 2012, and I'm ssh-ing into a custom built ubuntu box. It is here that I can't type a lower case "b".

I have restarted the server and yet I still can't type a "b". Every other letter is fine.

It hasn't done that before, I've had the server up and running for about two years and haven't come across an issue like this before. I also haven't done anything notable to cause it to do that.

At first I thought the keyboard was a little sticky but when I closed the connection it works fine. I've restarted the server, ssh'd back in and the "b" key stops working again.

I've tried my bluetooth keyboard and still no luck.

Could this be something that is a rule in a .profile or .bashrc file or something similar? A setting to not allow certain characters.

When I try to type the letter "b" I get the terminal bell sound as if it is not allowed.

edited May 3 '15 at 12:00

muru

asked Apr 30 '15 at 19:14

Mike

103110

Does it work when not using ssh?

– s3lph
Apr 30 '15 at 20:36

1

Please add this to your question using the edit button under your post.

– s3lph
Apr 30 '15 at 20:38

2

I don't think it is that as it is fine everywhere else. It's a MacBook Pro so I doubt it is a fault like that. It is too consistent to only occur in this state that I am sure it is something else.

– Mike
May 1 '15 at 9:54

2

Not in .profile or .bashrc, but probably in .inputrc or /etc/inputrc (readline's config file) it could be a lone b letter on its own row.

– egmont
May 3 '15 at 11:05

1

I'll update my question with those lines that I added, and if you update your answer to say to remove them then I can award you the 50 rep.

– Mike
May 3 '15 at 11:30

|
show 4 more comments

Update

Update 2

I recently added some lines to the /etc/inputrc file in order to get better tab auto-completion:

set completion-ignore-case on

set show-all-if-ambiguous on

TAB: menu-complete

bind TAB:menu-complete

Original Question

When I ssh into my ubuntu server I can't type the letter "b". I can however type a capital "B" using either shift keys.

I'm using a MacBook Pro with Retina display from 2012, and I'm ssh-ing into a custom built ubuntu box. It is here that I can't type a lower case "b".

I have restarted the server and yet I still can't type a "b". Every other letter is fine.

It hasn't done that before, I've had the server up and running for about two years and haven't come across an issue like this before. I also haven't done anything notable to cause it to do that.

At first I thought the keyboard was a little sticky but when I closed the connection it works fine. I've restarted the server, ssh'd back in and the "b" key stops working again.

I've tried my bluetooth keyboard and still no luck.

Could this be something that is a rule in a .profile or .bashrc file or something similar? A setting to not allow certain characters.

When I try to type the letter "b" I get the terminal bell sound as if it is not allowed.

edited May 3 '15 at 12:00

muru

asked Apr 30 '15 at 19:14

Mike

103110

Update

Update 2

I recently added some lines to the /etc/inputrc file in order to get better tab auto-completion:

set completion-ignore-case on

set show-all-if-ambiguous on

TAB: menu-complete

bind TAB:menu-complete

Original Question

When I ssh into my ubuntu server I can't type the letter "b". I can however type a capital "B" using either shift keys.

I'm using a MacBook Pro with Retina display from 2012, and I'm ssh-ing into a custom built ubuntu box. It is here that I can't type a lower case "b".

I have restarted the server and yet I still can't type a "b". Every other letter is fine.

It hasn't done that before, I've had the server up and running for about two years and haven't come across an issue like this before. I also haven't done anything notable to cause it to do that.

At first I thought the keyboard was a little sticky but when I closed the connection it works fine. I've restarted the server, ssh'd back in and the "b" key stops working again.

I've tried my bluetooth keyboard and still no luck.

Could this be something that is a rule in a .profile or .bashrc file or something similar? A setting to not allow certain characters.

When I try to type the letter "b" I get the terminal bell sound as if it is not allowed.

14.04 keyboard ssh

edited May 3 '15 at 12:00

muru

asked Apr 30 '15 at 19:14

Mike

103110

edited May 3 '15 at 12:00

muru

asked Apr 30 '15 at 19:14

Mike

103110

edited May 3 '15 at 12:00

muru

edited May 3 '15 at 12:00

muru

edited May 3 '15 at 12:00

muru

asked Apr 30 '15 at 19:14

Mike

103110

asked Apr 30 '15 at 19:14

Mike

103110

asked Apr 30 '15 at 19:14

Mike

103110

Does it work when not using ssh?

– s3lph
Apr 30 '15 at 20:36

1

Please add this to your question using the edit button under your post.

– s3lph
Apr 30 '15 at 20:38

2

I don't think it is that as it is fine everywhere else. It's a MacBook Pro so I doubt it is a fault like that. It is too consistent to only occur in this state that I am sure it is something else.

– Mike
May 1 '15 at 9:54

2

Not in .profile or .bashrc, but probably in .inputrc or /etc/inputrc (readline's config file) it could be a lone b letter on its own row.

– egmont
May 3 '15 at 11:05

1

I'll update my question with those lines that I added, and if you update your answer to say to remove them then I can award you the 50 rep.

– Mike
May 3 '15 at 11:30

|
show 4 more comments

Does it work when not using ssh?

– s3lph
Apr 30 '15 at 20:36

1

Please add this to your question using the edit button under your post.

– s3lph
Apr 30 '15 at 20:38

2

I don't think it is that as it is fine everywhere else. It's a MacBook Pro so I doubt it is a fault like that. It is too consistent to only occur in this state that I am sure it is something else.

– Mike
May 1 '15 at 9:54

2

Not in .profile or .bashrc, but probably in .inputrc or /etc/inputrc (readline's config file) it could be a lone b letter on its own row.

– egmont
May 3 '15 at 11:05

1

I'll update my question with those lines that I added, and if you update your answer to say to remove them then I can award you the 50 rep.

– Mike
May 3 '15 at 11:30

Does it work when not using ssh?

– s3lph
Apr 30 '15 at 20:36

Please add this to your question using the edit button under your post.

– s3lph
Apr 30 '15 at 20:38

I don't think it is that as it is fine everywhere else. It's a MacBook Pro so I doubt it is a fault like that. It is too consistent to only occur in this state that I am sure it is something else.

– Mike
May 1 '15 at 9:54

Not in .profile or .bashrc, but probably in .inputrc or /etc/inputrc (readline's config file) it could be a lone b letter on its own row.

– egmont
May 3 '15 at 11:05

I'll update my question with those lines that I added, and if you update your answer to say to remove them then I can award you the 50 rep.

– Mike
May 3 '15 at 11:30

|
show 4 more comments

1 Answer
1

active

oldest

votes

+50

Inside the ssh session, start a cat command and see whether you can type b there. I'm almost sure it'll work, which means that it's your shell that decides not to act on b.

Assuming the default bash, you should check readline's configuration files: ~/.inputrc, /etc/inputrc, or the one referred by $INPUTRC. Chances are you'll find an accidental lone b on its own line (or something similar), instructing readline not to do anything upon encountering this character.

Update

Looks to me that the first three lines of your .inputrc are correct, it's the fourth line (bind TAB:menu-complete) causing the trouble. Change its first letter to anything else (e.g. find instead of bind) and then that letter (e.g. f) will misbehave. Apparently bind is not a recognized keyword in this context.

edited May 3 '15 at 11:37

answered May 3 '15 at 11:20

egmont

3,88611024

I have to wait 24 hours to award the bounty. I will do it then. Thank you.

– Mike
May 3 '15 at 11:38

could OP just leave it as TAB:menu-complete ?

– Sergiy Kolodyazhnyy
May 4 '15 at 21:22

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
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f616525%2fi-cant-type-a-b-when-im-in-the-command-line%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

+50

Inside the ssh session, start a cat command and see whether you can type b there. I'm almost sure it'll work, which means that it's your shell that decides not to act on b.

Update

edited May 3 '15 at 11:37

answered May 3 '15 at 11:20

egmont

3,88611024

I have to wait 24 hours to award the bounty. I will do it then. Thank you.

– Mike
May 3 '15 at 11:38

could OP just leave it as TAB:menu-complete ?

– Sergiy Kolodyazhnyy
May 4 '15 at 21:22

add a comment |

+50

Inside the ssh session, start a cat command and see whether you can type b there. I'm almost sure it'll work, which means that it's your shell that decides not to act on b.

Update

edited May 3 '15 at 11:37

answered May 3 '15 at 11:20

egmont

3,88611024

I have to wait 24 hours to award the bounty. I will do it then. Thank you.

– Mike
May 3 '15 at 11:38

could OP just leave it as TAB:menu-complete ?

– Sergiy Kolodyazhnyy
May 4 '15 at 21:22

add a comment |

+50

Inside the ssh session, start a cat command and see whether you can type b there. I'm almost sure it'll work, which means that it's your shell that decides not to act on b.

Update

edited May 3 '15 at 11:37

answered May 3 '15 at 11:20

egmont

3,88611024

Inside the ssh session, start a cat command and see whether you can type b there. I'm almost sure it'll work, which means that it's your shell that decides not to act on b.

Update

edited May 3 '15 at 11:37

answered May 3 '15 at 11:20

egmont

3,88611024

edited May 3 '15 at 11:37

answered May 3 '15 at 11:20

egmont

3,88611024

answered May 3 '15 at 11:20

egmont

3,88611024

answered May 3 '15 at 11:20

egmont

3,88611024

I have to wait 24 hours to award the bounty. I will do it then. Thank you.

– Mike
May 3 '15 at 11:38

could OP just leave it as TAB:menu-complete ?

– Sergiy Kolodyazhnyy
May 4 '15 at 21:22

add a comment |

I have to wait 24 hours to award the bounty. I will do it then. Thank you.

– Mike
May 3 '15 at 11:38

could OP just leave it as TAB:menu-complete ?

– Sergiy Kolodyazhnyy
May 4 '15 at 21:22

I have to wait 24 hours to award the bounty. I will do it then. Thank you.

– Mike
May 3 '15 at 11:38

could OP just leave it as TAB:menu-complete ?

– Sergiy Kolodyazhnyy
May 4 '15 at 21:22

add a comment |

draft saved

draft discarded

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.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Cfxtrjtrk