package libpam0g 1.1.3-2ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

[bb]

I was doing a distribution upgrade and this hapened

ProblemType: Package
DistroRelease: Ubuntu 11.10
Package: libpam0g 1.1.3-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic i686
ApportVersion: 1.23-0ubuntu2
Architecture: i386
Date: Tue Oct 4 11:40:02 2011
ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
SourcePackage: pam
Title: package libpam0g 1.1.3-2ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to oneiric on 2011-10-04 (0 days ago)

[Steve Langasek (vorlon)]

Thank you for taking the time to report this issue and help to improve Ubuntu.

The error message in the logs is:

Setting up libpam0g (1.1.3-2ubuntu1) ...
Checking for services that may need to be restarted...Checking init scripts...
WARNING: init script for samba not found.
dpkg: error processing libpam0g (--configure):
 subprocess installed post-installation script returned error exit status 1

Were you shown a prompt during upgrade asking permission to restart pam services on your system?

If you resume the upgrade, does it now succeed?

Please attach the output of this command:
  debconf-show libpam0g

[bb (bbiran09)]

The upgrade went through and now it seems that this package is installed.

[Steve Langasek (vorlon)]

Ok. Can you still please attach the requested command output, so we can try to get this fixed for other users?

[bb (bbiran09)]

Yes sure, Here is the command output:

debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied
  libpam0g/restart-services:
  libpam0g/xdm-needs-restart:
  libpam0g/restart-failed:

[Steve Langasek (vorlon)]

Thanks for following up. Unfortunately, looking at that output I can see *no* reason why this would have failed. Since the issue has resolved itself for you, we aren't going to be able to diagnose it any further, so I have no choice but to close that bug and wait for someone else to encounter the problem.