Ubuntu
pam package

package libpam-gnome-keyring 2.28.0-0ubuntu2 failed to install/upgrade: il sottoprocesso vecchio script di post-installation è stato terminato dal segnale (Interrupt)

Bug #444452 reported by Alessio Gaeta on 2009-10-06

This bug report is a duplicate of: Bug #444252: tmp cleaned during upgrades and breaking installations?. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	pam (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: gnome-keyring

Upgrade from update-manager fails. It seems that debconf does not returns settings (checkboxes for pam profiles to activate), so the configuration process goes in an infinite loop breakable with ctrl-c.
It is still possible to properly configure package later, from a terminal, with dpkg --configure -a (and the graphical debconf works), so it is likely an update-manager bug.

ProblemType: Package
Architecture: i386
Date: Tue Oct 6 02:59:58 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: il sottoprocesso vecchio script di post-installation è stato terminato dal segnale (Interrupt)
Package: libpam-gnome-keyring 2.28.0-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: gnome-keyring
Title: package libpam-gnome-keyring 2.28.0-0ubuntu2 failed to install/upgrade: il sottoprocesso vecchio script di post-installation è stato terminato dal segnale (Interrupt)
Uname: Linux 2.6.31-11-generic i686

Tags:

Revision history for this message

Alessio Gaeta (meden) wrote on 2009-10-06:

Dependencies.txt Edit (633 bytes, text/plain; charset="utf-8")
Dmesg.gz Edit (14.4 KiB, application/x-gzip)
DpkgTerminalLog.gz Edit (17.2 KiB, application/x-gzip)
XsessionErrors.txt Edit (4.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Sebastien Bacher (seb128) wrote on 2009-10-06:

bug #444216 is a similar issue

affects:

gnome-keyring (Ubuntu) → pam (Ubuntu)

Revision history for this message

Steve Langasek (vorlon) wrote on 2009-10-06:

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.