pam-auth-update crashes

Bug #1475989 reported by SAMsan
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pam (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

First update after fresh install from Ubuntu Mate x64

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libpam-systemd:amd64 204-5ubuntu20.12
ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7
Uname: Linux 3.16.0-33-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Sun Jul 19 15:07:39 2015
DuplicateSignature: package:libpam-systemd:amd64:204-5ubuntu20.12:subprocess installed post-installation script returned error exit status 139
ErrorMessage: subprocess installed post-installation script returned error exit status 139
InstallationDate: Installed on 2015-07-19 (0 days ago)
InstallationMedia: Ubuntu MATE 14.04.2 "Trusty Tahr" - LTS amd64 (20150323)
SourcePackage: systemd
Title: package libpam-systemd:amd64 204-5ubuntu20.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
SAMsan (kurushii) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Martin Pitt (pitti) wrote :

This means that pam-auth-update crashed with signal 11 (i. e. SIGSEGV).

affects: systemd (Ubuntu) → pam (Ubuntu)
summary: - package libpam-systemd:amd64 204-5ubuntu20.12 failed to install/upgrade:
- subprocess installed post-installation script returned error exit status
- 139
+ pam-auth-update crashes
Revision history for this message
Martin Pitt (pitti) wrote :

Can you still reproduce this, e. g. with

  sudo apt-get install --reinstall libpam-systemd

If this crashes again, do you get a crash in /var/crash/ ? Can you please report that?

Changed in pam (Ubuntu):
status: New → Incomplete
Revision history for this message
Steve Langasek (vorlon) wrote :

And pam-auth-update is written in perl, so this probably points to a bug deeper in the system (interpreter, or hardware bug)

Revision history for this message
Martin Pitt (pitti) wrote :

@Steve: Right; I really think we need a proper apport .crash here. If you prefer, we can also close this report right away as in no case we can go ahead with just that. (Not sure how you prefer tracking such things)

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.