package libpam-modules 1.1.1-2ubuntu5.3 failed to install/upgrade: subprocess new pre-installation script killed by signal (Segmentation fault)

[Tzivaras Vasilis]

I had just set the system with a new format so that was the first update.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: libpam-modules 1.1.1-2ubuntu5.3
ProcVersionSignature: Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18
Uname: Linux 2.6.32-33-generic i686
Architecture: i386
Date: Mon Feb 13 13:44:13 2012
ErrorMessage: subprocess new pre-installation script killed by signal (Segmentation fault)
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1)
SourcePackage: pam
Title: package libpam-modules 1.1.1-2ubuntu5.3 failed to install/upgrade: subprocess new pre-installation script killed by signal (Segmentation fault)

[Steve Beattie (sbeattie)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Brian Murray (brian-murray)]

From DpkgTerminalLog.txt:

Preparing to replace libpam-modules 1.1.1-2ubuntu5.3 (using .../libpam-modules_1.1.1-2ubuntu5.4_i386.deb) ...
dpkg: error processing /var/cache/apt/archives/libpam-modules_1.1.1-2ubuntu5.4_i386.deb (--unpack):
 subprocess new pre-installation script killed by signal (Segmentation fault)

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your log files attached to this bug report it seems that a package failed to install due to a segmentation fault in an application being used by the package installation process. Unfortunately, this bug report isn't very useful in its current state and a crash report would be much more useful. Could you try recreating this issue by enabling apport to catch the crash report 'sudo service apport start force_start=1' and then trying to install the same package again? This process will create a new bug report so I am marking this one as Invalid. Thanks again for helping out!