package libpam0g:amd64 1.3.1-5ubuntu4.6 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe)

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

Bug Description

not sure why the problem

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libpam0g:amd64 1.3.1-5ubuntu4.6
ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Mar 25 07:27:49 2023
DpkgTerminalLog:
 Preparing to unpack .../libpam0g_1.3.1-5ubuntu4.6_amd64.deb ...
 Unpacking libpam0g:amd64 (1.3.1-5ubuntu4.6) over (1.3.1-5ubuntu4.3) ...
 Setting up libpam0g:amd64 (1.3.1-5ubuntu4.6) ...
 dpkg: error processing package libpam0g:amd64 (--configure):
  installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe)
DuplicateSignature:
 package:libpam0g:amd64:1.3.1-5ubuntu4.6
 Setting up libpam0g:amd64 (1.3.1-5ubuntu4.6) ...
 dpkg: error processing package libpam0g:amd64 (--configure):
  installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe)
ErrorMessage: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe)
InstallationDate: Installed on 2020-08-07 (964 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt 2.0.9
SourcePackage: pam
Title: package libpam0g:amd64 1.3.1-5ubuntu4.6 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Broken pipe)
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Ronald McCallister (ronaldmccallister) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Steve Langasek (vorlon) wrote :

"broken pipe" means the maintainer script died because the debconf frontend exited abnormally (this is the only pipe we wait for). This isn't a bug in pam, it can't proceed with configuration if it doesn't get sane answers for debconf. What was the context in which you were running the package upgrade?

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.