Hello, after upgrading to focal I found the following in my journalctl output:
Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory
Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory
Hello, after upgrading to focal I found the following in my journalctl output:
Jan 24 23:07:00 millbarge sudo[32120]: pam_unix( sudo:auth) : Couldn't open /etc/securetty: No such file or directory sudo:auth) : Couldn't open /etc/securetty: No such file or directory
Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(
The login package stopped packaging this file: /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 731656 /paste. ubuntu. com/p/myh9cGWrH D/
https:/
and now forcibly removes the file:
https:/
However, the pam package's pam_unix.so module has not yet been adapted to ignore this file: /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 674857# 25
https:/
Thanks
ProblemType: Bug ature: Ubuntu 5.4.0-9.12-generic 5.4.3 dules: zfs zunicode zavl icp zcommon znvpair unicode- 256color DIR=<set>
DistroRelease: Ubuntu 20.04
Package: libpam-modules 1.3.1-5ubuntu4
ProcVersionSign
Uname: Linux 5.4.0-9-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
Date: Fri Jan 24 23:35:33 2020
ProcEnviron:
TERM=rxvt-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: pam
UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago)