update to login 4.13+dfsg1-4ubuntu3.3 solved problem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060676
Title:
[SRU] login: remove pam_lastlog.so from config
To manage notifications about this b
I performed a fresh noble install in a VM, first I verified that the
issue was still persistent. See screenshot attached
** Attachment added: "pre-new-login.png"
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2060676/+attachment/5841523/+files/pre-new-login.png
--
You received this bu
Then, (in GDM, not a tty) I downloaded:
http://launchpadlibrarian.net/761035045/login_4.13+dfsg1-4ubuntu3.3_amd64.deb
Ran:
```
sudo apt install ./login_4.13+dfsg1-4ubuntu3.3_amd64.deb
```
verified that the problematic entry was no longer present in /etc/pam.d/login:
```
$ cat /etc/pam.d/login | gr
Hello Alfonso, or anyone else affected,
Accepted shadow into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/shadow/1:4.13+dfsg1-4ubuntu3.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
Staging this bug with block-proposed-noble as the impact isn't high
enough to warrant an upload on it's own. This is a nice-to-have, fixing
a cosmetic issue, and should be bundled with another SRU.
** Description changed:
[ Impact ]
* The following line has been found in users logs when t
** Description changed:
[ Impact ]
* The following line has been found in users logs when trying to log in to
their systems:
login[2449]: PAM unable to dlopen(pam_lastlog.so):
/usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file
or directory
This is t
Looking for sponsorship for this!
** Description changed:
[ Impact ]
* The following line has been found in users logs when trying to log in to
their systems:
login[2449]: PAM unable to dlopen(pam_lastlog.so):
/usr/lib/security/pam_lastlog.so: cannot open shared object file: No suc
** Description changed:
[ Impact ]
* The following line has been found in users logs when trying to log in to
their systems:
login[2449]: PAM unable to dlopen(pam_lastlog.so):
/usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file
or directory
This is t
** Description changed:
[ Impact ]
* The following line has been found in users logs when trying to log in to
their systems:
login[2449]: PAM unable to dlopen(pam_lastlog.so):
/usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file
or directory
This is t
** Description changed:
[ Impact ]
* The following line has been found in users logs when trying to log in to
their systems:
login[2449]: PAM unable to dlopen(pam_lastlog.so):
/usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file
or directory
- This resu
MP attached to bug, ready for review, I think
** Description changed:
[ Impact ]
* The following line has been found in users logs when trying to log in to
their systems:
login[2449]: PAM unable to dlopen(pam_lastlog.so):
/usr/lib/security/pam_lastlog.so: cannot open shared object
** Merge proposal linked:
https://code.launchpad.net/~andersson123/ubuntu/+source/shadow/+git/shadow/+merge/476396
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060676
Title:
[SRU] login: remov
Hi Mikael,
The missing entry in /var/log/wtmp is a pre-existing issue. To fix that
in noble would involve a separate SRU, to my understanding. We would
need to SRU changes from util-linux/2.40* (which includes
pam_lastlog2.so) to noble, as well as SRU'ing changes to shadow which
would involve depe
I believe it is a problem, since it seems to be causing "last" not to
work correctly.
Removing the entry in /etc/pam.d/login will just clean up the
/var/log/auth.log file and not fix the missing entry in /var/log/wtmp -
right?
--
You received this bug notification because you are a member of Ubu
Hi all,
I spent some time reproducing this issue, thus far, it seems as though
this issue is entirely cosmetic - I've only been able to reproduce the
annoying log message, but have failed to reproduce any issues actually
logging in. Can anyone please confirm to me that this issue is purely
cosmeti
** Changed in: shadow (Ubuntu Plucky)
Milestone: noble-updates => None
** Changed in: shadow (Ubuntu Plucky)
Assignee: Tim Andersson (andersson123) => (unassigned)
** No longer affects: shadow (Ubuntu Plucky)
** Changed in: shadow (Ubuntu Noble)
Assignee: (unassigned) => Paride Leg
16 matches
Mail list logo
