package libpam-systemd:amd64 208-8ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 in pam-auth-update

Bug #1372193 reported by Aram Paronikyan
64
This bug affects 14 people
Affects Status Importance Assigned to Milestone
pam (Ubuntu)
Confirmed
High
Unassigned

Bug Description

No further info available. This is the first occurrence of the error. The system updater was working that time.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: libpam-systemd:amd64 208-8ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
Uname: Linux 3.16.0-14-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
Date: Mon Sep 22 02:19:49 2014
DuplicateSignature: package:libpam-systemd:amd64:208-8ubuntu4:subprocess installed post-installation script returned error exit status 128
ErrorMessage: subprocess installed post-installation script returned error exit status 128
InstallationDate: Installed on 2013-09-15 (370 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: systemd
Title: package libpam-systemd:amd64 208-8ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Aram Paronikyan (paronikyan) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Martin Pitt (pitti) wrote :

This happens in the pam-auth-update call, reassigning to PAM.

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

The errors in the log are:

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.

This looks like a problem with debconf, not with pam. Please show the output of the commands 'debconf-show debconf' and 'debconf-show libpam-runtime'.

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
Revision history for this message
Sebastien Bacher (seb128) wrote :

I'm having the same issue on vivid,

$ debconf-show debconf
  debconf-apt-progress/preparing:
  debconf/priority: high
  debconf-apt-progress/info:
  debconf-apt-progress/media-change:
  debconf-apt-progress/title:
* debconf/frontend: Dialog

$ debconf-show libpam-runtime
  libpam-runtime/no_profiles_chosen:
  libpam-runtime/override: false
  libpam-runtime/profiles: unix, systemd, gnome-keyring, ecryptfs-utils, consolekit, capability
  libpam-runtime/title:
  libpam-runtime/you-had-no-auth:
  libpam-runtime/conflicts:

Revision history for this message
Sebastien Bacher (seb128) wrote :

note that I'm doing updates using update-manager (in case that makes a difference)

Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in pam (Ubuntu):
importance: Undecided → High
Revision history for this message
schollsky (schollsky) wrote :

Affects me with vivid. Bugs shows up after update. Last updates before have been made 5 days ago.

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.