Unable to login in a Ubuntu server 16.04.5
Im running an ubuntu server 16.04.5. System was working properly up to until a few days ago. Then yesterday I found out that I cannot login from the local keyboard. System behaves strangely....it takes the username but not the password. It looks like the enter key is stuck (its not) sending an empty password. After a few loops it resets asking for username. Login works via ssh and the problem also disappears once booting with previous kernel (4.4.0-151-genric). Any help??
command-line login
asked Feb 6 at 0:13
sourfousourfou
82
add a comment |
Im running an ubuntu server 16.04.5. System was working properly up to until a few days ago. Then yesterday I found out that I cannot login from the local keyboard. System behaves strangely....it takes the username but not the password. It looks like the enter key is stuck (its not) sending an empty password. After a few loops it resets asking for username. Login works via ssh and the problem also disappears once booting with previous kernel (4.4.0-151-genric). Any help??
command-line login
asked Feb 6 at 0:13
sourfousourfou
82
1
Welcome to Ask Ubuntu. I'd firstly check the keyboard itself (plus connection). Unplug it, re-plug it in or try a different keyboard. Yes if it only occurs on a specific kernel it's likely a software issue, but if hardware related (esp. dying component or poor/dirty connectors) it can work sometimes, other times not & co-incidence can give wrong impressions...
– guiverc
Feb 6 at 0:31
the keyboard is ok. The problem was a known issue with some kernels. Setting as default an unaffected kernel solved the problem. Thx for feedback.
– sourfou
Feb 6 at 15:29
See also: askubuntu.com/questions/1113704/tty-doesnt-wait-for-password
– Nathaniel M. Beaver
Feb 20 at 16:37
add a comment |
Im running an ubuntu server 16.04.5. System was working properly up to until a few days ago. Then yesterday I found out that I cannot login from the local keyboard. System behaves strangely....it takes the username but not the password. It looks like the enter key is stuck (its not) sending an empty password. After a few loops it resets asking for username. Login works via ssh and the problem also disappears once booting with previous kernel (4.4.0-151-genric). Any help??
command-line login
asked Feb 6 at 0:13
sourfousourfou
82
Im running an ubuntu server 16.04.5. System was working properly up to until a few days ago. Then yesterday I found out that I cannot login from the local keyboard. System behaves strangely....it takes the username but not the password. It looks like the enter key is stuck (its not) sending an empty password. After a few loops it resets asking for username. Login works via ssh and the problem also disappears once booting with previous kernel (4.4.0-151-genric). Any help??
command-line login
command-line login
asked Feb 6 at 0:13
sourfousourfou
82
asked Feb 6 at 0:13
sourfousourfou
82
asked Feb 6 at 0:13
sourfousourfou
82
asked Feb 6 at 0:13
sourfousourfou
82
asked Feb 6 at 0:13
sourfousourfou
82
82
1
Welcome to Ask Ubuntu. I'd firstly check the keyboard itself (plus connection). Unplug it, re-plug it in or try a different keyboard. Yes if it only occurs on a specific kernel it's likely a software issue, but if hardware related (esp. dying component or poor/dirty connectors) it can work sometimes, other times not & co-incidence can give wrong impressions...
– guiverc
Feb 6 at 0:31
the keyboard is ok. The problem was a known issue with some kernels. Setting as default an unaffected kernel solved the problem. Thx for feedback.
– sourfou
Feb 6 at 15:29
See also: askubuntu.com/questions/1113704/tty-doesnt-wait-for-password
– Nathaniel M. Beaver
Feb 20 at 16:37
add a comment |
1
Welcome to Ask Ubuntu. I'd firstly check the keyboard itself (plus connection). Unplug it, re-plug it in or try a different keyboard. Yes if it only occurs on a specific kernel it's likely a software issue, but if hardware related (esp. dying component or poor/dirty connectors) it can work sometimes, other times not & co-incidence can give wrong impressions...
– guiverc
Feb 6 at 0:31
the keyboard is ok. The problem was a known issue with some kernels. Setting as default an unaffected kernel solved the problem. Thx for feedback.
– sourfou
Feb 6 at 15:29
See also: askubuntu.com/questions/1113704/tty-doesnt-wait-for-password
– Nathaniel M. Beaver
Feb 20 at 16:37
1
1
Welcome to Ask Ubuntu. I'd firstly check the keyboard itself (plus connection). Unplug it, re-plug it in or try a different keyboard. Yes if it only occurs on a specific kernel it's likely a software issue, but if hardware related (esp. dying component or poor/dirty connectors) it can work sometimes, other times not & co-incidence can give wrong impressions...
– guiverc
Feb 6 at 0:31
Welcome to Ask Ubuntu. I'd firstly check the keyboard itself (plus connection). Unplug it, re-plug it in or try a different keyboard. Yes if it only occurs on a specific kernel it's likely a software issue, but if hardware related (esp. dying component or poor/dirty connectors) it can work sometimes, other times not & co-incidence can give wrong impressions...
– guiverc
Feb 6 at 0:31
the keyboard is ok. The problem was a known issue with some kernels. Setting as default an unaffected kernel solved the problem. Thx for feedback.
– sourfou
Feb 6 at 15:29
the keyboard is ok. The problem was a known issue with some kernels. Setting as default an unaffected kernel solved the problem. Thx for feedback.
– sourfou
Feb 6 at 15:29
See also: askubuntu.com/questions/1113704/tty-doesnt-wait-for-password
– Nathaniel M. Beaver
Feb 20 at 16:37
See also: askubuntu.com/questions/1113704/tty-doesnt-wait-for-password
– Nathaniel M. Beaver
Feb 20 at 16:37
add a comment |
1 Answer
1
active
oldest
votes
It's a known bug:
console login loop after entering username followed by RETURN
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095
Userspace break as a result of missing patch backport
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873
Check your kernel version to see if you're affected. 4.15.0-43-generic is good, 4.15.0-44-generic and 4.15.0-45-generic are bad.
$ uname -r
4.15.0-45-generic
answered Feb 6 at 1:00
Nathaniel M. BeaverNathaniel M. Beaver
264111
yeah thx for the help. Its the kernel issue u mention. Also confirming kernel 4.4.0-141 is good but 4.4.0-142 is bad for ubuntu server 16.04.5. Setting the former as default in grub, solved the issue.
– sourfou
Feb 6 at 15:23
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%2f1115961%2funable-to-login-in-a-ubuntu-server-16-04-5%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It's a known bug:
console login loop after entering username followed by RETURN
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095
Userspace break as a result of missing patch backport
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873
Check your kernel version to see if you're affected. 4.15.0-43-generic is good, 4.15.0-44-generic and 4.15.0-45-generic are bad.
$ uname -r
4.15.0-45-generic
answered Feb 6 at 1:00
Nathaniel M. BeaverNathaniel M. Beaver
264111
yeah thx for the help. Its the kernel issue u mention. Also confirming kernel 4.4.0-141 is good but 4.4.0-142 is bad for ubuntu server 16.04.5. Setting the former as default in grub, solved the issue.
– sourfou
Feb 6 at 15:23
add a comment |
It's a known bug:
console login loop after entering username followed by RETURN
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095
Userspace break as a result of missing patch backport
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873
Check your kernel version to see if you're affected. 4.15.0-43-generic is good, 4.15.0-44-generic and 4.15.0-45-generic are bad.
$ uname -r
4.15.0-45-generic
answered Feb 6 at 1:00
Nathaniel M. BeaverNathaniel M. Beaver
264111
yeah thx for the help. Its the kernel issue u mention. Also confirming kernel 4.4.0-141 is good but 4.4.0-142 is bad for ubuntu server 16.04.5. Setting the former as default in grub, solved the issue.
– sourfou
Feb 6 at 15:23
add a comment |
It's a known bug:
console login loop after entering username followed by RETURN
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095
Userspace break as a result of missing patch backport
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873
Check your kernel version to see if you're affected. 4.15.0-43-generic is good, 4.15.0-44-generic and 4.15.0-45-generic are bad.
$ uname -r
4.15.0-45-generic
answered Feb 6 at 1:00
Nathaniel M. BeaverNathaniel M. Beaver
264111
It's a known bug:
console login loop after entering username followed by RETURN
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095
Userspace break as a result of missing patch backport
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873
Check your kernel version to see if you're affected. 4.15.0-43-generic is good, 4.15.0-44-generic and 4.15.0-45-generic are bad.
$ uname -r
4.15.0-45-generic
answered Feb 6 at 1:00
Nathaniel M. BeaverNathaniel M. Beaver
264111
answered Feb 6 at 1:00
Nathaniel M. BeaverNathaniel M. Beaver
264111
answered Feb 6 at 1:00
Nathaniel M. BeaverNathaniel M. Beaver
264111
answered Feb 6 at 1:00
Nathaniel M. BeaverNathaniel M. Beaver
264111
264111
yeah thx for the help. Its the kernel issue u mention. Also confirming kernel 4.4.0-141 is good but 4.4.0-142 is bad for ubuntu server 16.04.5. Setting the former as default in grub, solved the issue.
– sourfou
Feb 6 at 15:23
add a comment |
yeah thx for the help. Its the kernel issue u mention. Also confirming kernel 4.4.0-141 is good but 4.4.0-142 is bad for ubuntu server 16.04.5. Setting the former as default in grub, solved the issue.
– sourfou
Feb 6 at 15:23
yeah thx for the help. Its the kernel issue u mention. Also confirming kernel 4.4.0-141 is good but 4.4.0-142 is bad for ubuntu server 16.04.5. Setting the former as default in grub, solved the issue.
– sourfou
Feb 6 at 15:23
yeah thx for the help. Its the kernel issue u mention. Also confirming kernel 4.4.0-141 is good but 4.4.0-142 is bad for ubuntu server 16.04.5. Setting the former as default in grub, solved the issue.
– sourfou
Feb 6 at 15:23
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%2f1115961%2funable-to-login-in-a-ubuntu-server-16-04-5%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
1
Welcome to Ask Ubuntu. I'd firstly check the keyboard itself (plus connection). Unplug it, re-plug it in or try a different keyboard. Yes if it only occurs on a specific kernel it's likely a software issue, but if hardware related (esp. dying component or poor/dirty connectors) it can work sometimes, other times not & co-incidence can give wrong impressions...
– guiverc
Feb 6 at 0:31
the keyboard is ok. The problem was a known issue with some kernels. Setting as default an unaffected kernel solved the problem. Thx for feedback.
– sourfou
Feb 6 at 15:29
See also: askubuntu.com/questions/1113704/tty-doesnt-wait-for-password
– Nathaniel M. Beaver
Feb 20 at 16:37