package libpam-systemd:amd64 208-8ubuntu5 failed to install/upgrade: pam-auth-update dies in debconf

Bug #1376612 reported by Remco Brenninkmeijer on 2014-10-02
32
This bug affects 11 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
High
Michael Vogt

Bug Description

Error during update, however update went ok the next day so can probably be closed.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: libpam-systemd:amd64 208-8ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
Uname: Linux 3.16.0-18-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
Date: Wed Oct 1 10:24:40 2014
DuplicateSignature: package:libpam-systemd:amd64:208-8ubuntu5:subprocess installed post-installation script returned error exit status 128
ErrorMessage: subprocess installed post-installation script returned error exit status 128
InstallationDate: Installed on 2014-02-08 (235 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140208)
SourcePackage: systemd
Title: package libpam-systemd:amd64 208-8ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
UpgradeStatus: Upgraded to utopic on 2014-08-28 (34 days ago)

Remco Brenninkmeijer (requist1) wrote :
tags: removed: need-duplicate-check
Launchpad Janitor (janitor) wrote :

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

Changed in systemd (Ubuntu):
status: New → Confirmed
Martin Pitt (pitti) wrote :

This is a debconf failure in pam-auth-update, reassigning.

affects: systemd (Ubuntu) → pam (Ubuntu)
summary: package libpam-systemd:amd64 208-8ubuntu5 failed to install/upgrade:
- subprocess installed post-installation script returned error exit status
- 128
+ pam-auth-update dies in debconf
Steve Langasek (vorlon) wrote :

> Setting up libpam-systemd:amd64 (208-8ubuntu5) ...
> Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66.

Not a pam bug, either; something's wrong with the debconf environment here. I suspect update-manager / aptdaemon. Michael, is this something you could take a look at?

affects: pam (Ubuntu) → update-manager (Ubuntu)
Changed in update-manager (Ubuntu):
assignee: nobody → Michael Vogt (mvo)
Changed in update-manager (Ubuntu):
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers