Text console login does not allow login - it behaves as if "entered" is continuously keyed after "login". N

Bug #1817034 reported by Michael Grivas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
shadow (Ubuntu)
New
Undecided
Unassigned

Bug Description

The following happens with any user, WITHOUT typing any password !! Only one "ENTER" keyed.
Login: myuser
Password:

Login incorrect
Login:

Login incorrect
...

To happens to all Alt+Ctrl+Fx , while no problem appears in graphical terminals or Gnome.
That appeared only after the last updates, with kernel 4.15.0-45 .
If I boot back to 4.15.0-43 the issue does not appear.

The /var/log/auth.log shows:
login[6180]: pam_unix(login:auth): conversation failed
login[6180]: pam_unix(login:auth): auth could not identify password for [myuser]
login[6180]: FAILED LOGIN (1) on '/dev/tty3' FOR 'myuser', Authentication failure
login[6180]: pam_securetty(login:auth): cannot determine username
login[6180]: FAILED LOGIN (2) on '/dev/tty3' FOR 'UNKNOWN', Error in service module
login[6180]: pam_securetty(login:auth): cannot determine username
login[6180]: FAILED LOGIN (3) on '/dev/tty3' FOR 'UNKNOWN', Error in service module
login[6180]: pam_securetty(login:auth): cannot determine username
login[6180]: FAILED LOGIN (4) on '/dev/tty3' FOR 'UNKNOWN', Error in service module

The /var/log/audit.log shows:
type=USER_LOGIN msg=audit(1550742677.578:221): pid=7230 uid=0 auid=4294967295 ses=4294967295 msg='op=login acct="UNKNOWN" exe="/bin/login" hostname=P50 addr=? terminal=/dev/tty3 res=failed'
type=USER_AUTH msg=audit(1550742680.902:222): pid=7230 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication acct="?" exe="/bin/login" hostname=P50 addr=? terminal=/dev/tty3 res=failed'
type=USER_LOGIN msg=audit(1550742680.902:223): pid=7230 uid=0 auid=4294967295 ses=4294967295 msg='op=login acct="UNKNOWN" exe="/bin/login" hostname=P50 addr=? terminal=/dev/tty3 res=failed'
type=SERVICE_STOP msg=audit(1550742730.226:224): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty3 comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
type=SERVICE_START msg=audit(1550742730.226:225): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty3 comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
type=SERVICE_STOP msg=audit(1550742730.226:226): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty3 comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
type=SERVICE_START msg=audit(1550742730.230:227): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty3 comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: login 1:4.5-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 21 10:17:48 2019
InstallationDate: Installed on 2018-11-05 (107 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: shadow
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Michael Grivas (mgrivas) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.