package libpam-runtime 1.1.8-3.1ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

Bug #1559780 reported by giovanni
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pam (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I don't know what happened

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: libpam-runtime 1.1.8-3.1ubuntu3.2
ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
Uname: Linux 4.2.0-34-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Sun Mar 20 18:31:34 2016
DuplicateSignature: package:libpam-runtime:1.1.8-3.1ubuntu3.2:subprocess installed post-installation script returned error exit status 128
ErrorMessage: subprocess installed post-installation script returned error exit status 128
InstallationDate: Installed on 2012-06-18 (1371 days ago)
InstallationMedia: Ubuntu "Precise" - Build amd64 LIVE Binary 20120426-22:45
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5.1
 apt 1.0.10.2ubuntu1
SourcePackage: pam
Title: package libpam-runtime 1.1.8-3.1ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
UpgradeStatus: Upgraded to wily on 2015-12-12 (99 days ago)

Revision history for this message
giovanni (giovanni-maderni) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Steve Langasek (vorlon) wrote :

Your dpkg log shows:

Setting up libpam-runtime (1.1.8-3.1ubuntu3.2) ...
Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66.
Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67.
Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68.
[...]
dpkg: error processing package libpam-runtime (--configure):
 subprocess installed post-installation script returned error exit status 128

This may be a transient problem with your debconf environment. You should be able to correct this problem by running 'sudo dpkg --configure -a' from the commandline.

Changed in pam (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for pam (Ubuntu) because there has been no activity for 60 days.]

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