package libpam-modules 1.3.1-5ubuntu4.7 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pam (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
failed during upgrade
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libpam-modules 1.3.1-5ubuntu4.7
ProcVersionSign
Uname: Linux 5.4.0-170-generic x86_64
ApportVersion: 2.20.11-
Architecture: amd64
CasperMD5CheckR
Date: Mon Jan 29 13:45:41 2024
ErrorMessage: new libpam-
InstallationDate: Installed on 2017-09-02 (2340 days ago)
InstallationMedia:
Python3Details: /usr/bin/
PythonDetails: N/A
RelatedPackageV
dpkg 1.21.1ubuntu2.2
apt 2.0.10
SourcePackage: pam
Title: package libpam-modules 1.3.1-5ubuntu4.7 failed to install/upgrade: new libpam-
UpgradeStatus: Upgraded to focal on 2024-01-29 (0 days ago)
modified.
mtime.conffile.
tags: | removed: need-duplicate-check |
The log output shows that you have pam_tally or pam_tally2 in your pam configuration. The preinst fails in order to save you from upgrading and breaking your system, leaving you with a configuration referencing an obsolete pam module.
The message says:
you are using pam_tally or pam_tally2 in your configuration
The pam_tally and pam_tally2 modules have been removed from PAM. You are using one of these
modules in your PAM configuration in /etc/pam.d. You must remove the uses of these modules
before PAM can be upgraded; including these modules in your PAM configuration after the
upgrade will stop users from being able to log into the system.
Consider the pam_faillock module as a replacement for pam_tally.
The fact that this message was shown to you via the pam preinst script also indicates that you were not using ubuntu- release- upgrader, the recommended way to upgrade between Ubuntu releases. On servers, please upgrading using 'sudo do-release- upgrade' . On desktops, please use 'update-manager'.