package libpam-runtime 1.3.1-5ubuntu4.1 failed to install/upgrade: installed libpam-runtime package post-installation script subprocess returned error exit status 128

Bug #1895207 reported by Daisuke Aihara
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
pam (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Dear Sirs/Madams, I am simply reporting this as the "pam package" directs.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libpam-runtime 1.3.1-5ubuntu4.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Sep 10 22:56:49 2020
DuplicateSignature:
 package:libpam-runtime:1.3.1-5ubuntu4.1
 Setting up libpam-runtime (1.3.1-5ubuntu4.1) ...
 Use of uninitialized value $ret in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 134, <GEN0> line 1.
 dpkg: error processing package libpam-runtime (--configure):
  installed libpam-runtime package post-installation script subprocess returned error exit status 128
ErrorMessage: installed libpam-runtime package post-installation script subprocess returned error exit status 128
InstallationDate: Installed on 2020-09-10 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.2ubuntu0.1
SourcePackage: pam
Title: package libpam-runtime 1.3.1-5ubuntu4.1 failed to install/upgrade: installed libpam-runtime package post-installation script subprocess returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Daisuke Aihara (daisukeaihara) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in pam (Ubuntu):
status: New → Confirmed
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.