package libpam-gnome-keyring 2.28.0-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 143
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pam (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-keyring
1)
eve[~]% lsb_release -rd
aptDescription: Ubuntu karmic (development branch)
Release: 9.10
2)
eve[~]% apt-cache policy gnome-keyring
gnome-keyring:
Installed: 2.28.0-0ubuntu2
Candidate: 2.28.0-0ubuntu2
Version table:
*** 2.28.0-0ubuntu2 0
500 http://
100 /var/lib/
eve[~]% apt-cache policy libpam-
libpam-
Installed: 2.28.0-0ubuntu2
Candidate: 2.28.0-0ubuntu2
Version table:
*** 2.28.0-0ubuntu2 0
500 http://
100 /var/lib/
3)
Installation to work
4)
During installation, a debconf dialog popped up and asked me to choose which PAM backend I wanted to enable (all were orginallyset to be disabled).
I selected them all, only to be informed that I need to select at least one. This time I de-selected them all, and tried to go 'forward'; same problem. In no combination of selections, could I go forward (there were 5).
I kill the debconf process (kill -15) and it caused my entire system to commence a shutdown sequence. And then the crash dialog came up when I logged back in.
ProblemType: Package
Architecture: i386
Date: Tue Oct 6 03:33:00 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned error exit status 143
Package: libpam-
ProcVersionSign
SourcePackage: gnome-keyring
Title: package libpam-
Uname: Linux 2.6.31-11-generic i686
affects: | gnome-keyring (Ubuntu) → pam (Ubuntu) |
Thank you for taking the time to report this bug and help to improve Ubuntu.
It has been suggested that, given the timing of its appearance, this strange (and largely inexplicable) debconf behavior is fallout from bug #444252. Marking as a duplicate; will revisit if we get further reports of this problem now that 444252 is resolved.