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

[許年糕]

dpkg: error processing archive /var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2.4_amd64.deb (--unpack):
 new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2
Errors were encountered while processing:
 /var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2.4_amd64.deb
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/libpam-modules.0.crash'
Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libpam-modules 1.3.1-5ubuntu4.7
ProcVersionSignature: Ubuntu 5.15.0-1060.68~20.04.1-gcp 5.15.149
Uname: Linux 5.15.0-1060-gcp x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
CloudArchitecture: x86_64
CloudID: gce
CloudName: gce
CloudPlatform: gce
CloudRegion: asia-east1
CloudSubPlatform: metadata (http://metadata.google.internal/computeMetadata/v1/)
Date: Fri May 24 11:32:33 2024
ErrorMessage: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.3
 apt 2.0.10
SourcePackage: pam
Title: 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
UpgradeStatus: Upgraded to focal on 2024-05-24 (0 days ago)

[Steve Langasek (vorlon)]

Your dpkg log shows the following prompt:

        Configuring libpam-modules

    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.

This is not a bug. The pam package is saving you from making it impossible to log into your system after upgrade.

If you were using the supported `do-release-upgrade` tool for upgrading between releases, this would have notified you at the beginning of the upgrade and not resulted in a package upgrade failure.